Treasure Data Status

Apr 3, 2025

No incidents reported today.

Apr 2, 2025

Completed - The scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected.

If you encounter any issues, please reach out to our support team.
Apr 2, 19:06 PDT

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Apr 2, 18:55 PDT

In progress - The scheduled database maintenance window is now starting. We are working to minimize downtime and will provide updates as the maintenance progresses.

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.
Apr 2, 18:00 PDT

Update - In about an hour, from 1:00 UTC, the maintenance window for Treasure Data databases will commence.

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

Beyond this notice, we will update our status page (https://status.treasuredata.com/) at the start and completion of the operation and once the new system has been verified. At that time, all systems will have returned to normal operations, and this Scheduled Maintenance will be closed.
Apr 2, 17:00 PDT

Scheduled - On Thursday, April 3 from 01:00 to 02:30 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

# Communication

Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed.

If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.
Feb 21, 11:15 PST

Apr 1, 2025

[EU Region] Database Maintenance

Completed - The scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected.

If you encounter any issues, please reach out to our support team.
Apr 1, 19:29 PDT

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Apr 1, 19:21 PDT

In progress - The scheduled database maintenance window is now starting. We are working to minimize downtime and will provide updates as the maintenance progresses.

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.
Apr 1, 18:00 PDT

Update - In about an hour, from 1:00 UTC, the maintenance window for Treasure Data databases will commence.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

Beyond this notice, we will update our status page (https://status.treasuredata.com/) at the start and completion of the operation and once the new system has been verified. At that time, all systems will have returned to normal operations, and this Scheduled Maintenance will be closed.
Apr 1, 17:00 PDT

Scheduled - On Wednesday, April 2 from 01:00 to 02:30 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

# Communication

Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed.

If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.
Feb 21, 11:14 PST

Mar 31, 2025

No incidents reported.

Mar 30, 2025

No incidents reported.

Mar 29, 2025

No incidents reported.

Mar 28, 2025

No incidents reported.

Mar 27, 2025

No incidents reported.

Mar 26, 2025

[Tokyo Region] Database Maintenance

Completed - The scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected.

If you encounter any issues, please reach out to our support team.
Mar 26, 19:04 PDT

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Mar 26, 18:53 PDT

In progress - The scheduled database maintenance window is now starting. We are working to minimize downtime and will provide updates as the maintenance progresses.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.
Mar 26, 18:00 PDT

Update - In about an hour, from 1:00 UTC, the maintenance window for Treasure Data databases will commence.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

Beyond this notice, we will update our status page (https://status.treasuredata.com/) at the start and completion of the operation and once the new system has been verified. At that time, all systems will have returned to normal operations, and this Scheduled Maintenance will be closed.
Mar 26, 17:00 PDT

Scheduled - On Thursday, March 27 from 01:00 to 02:30 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

# Communication

Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed.

If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.
Feb 21, 11:13 PST

Mar 25, 2025

[US Region] Database Maintenance

Completed - The scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected.

If you encounter any issues, please reach out to our support team.
Mar 25, 19:10 PDT

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Mar 25, 19:00 PDT

In progress - The scheduled database maintenance window is now starting. We are working to minimize downtime and will provide updates as the maintenance progresses.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.
Mar 25, 18:00 PDT

Update - In about an hour, from 1:00 UTC, the maintenance window for Treasure Data databases will commence.

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

Beyond this notice, we will update our status page (https://status.treasuredata.com/) at the start and completion of the operation and once the new system has been verified. At that time, all systems will have returned to normal operations, and this Scheduled Maintenance will be closed.
Mar 25, 17:00 PDT

Scheduled - On Wednesday, March 26 from 01:00 to 02:30 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

# Communication

Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed.

If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.
Feb 21, 11:10 PST

Mar 24, 2025

[Korea Region] Database Maintenance

Completed - The scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected.
Mar 24, 19:30 PDT

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Mar 24, 19:18 PDT

In progress - The scheduled database maintenance window is now starting. We are working to minimize downtime and will provide updates as the maintenance progresses.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.
Mar 24, 18:00 PDT

Update - In about an hour, from 1:00 UTC, the maintenance window for Treasure Data databases will commence.

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

Beyond this notice, we will update our status page (https://status.treasuredata.com/) at the start and completion of the operation and once the new system has been verified. At that time, all systems will have returned to normal operations, and this Scheduled Maintenance will be closed.
Mar 24, 17:00 PDT

Update - We will be undergoing scheduled maintenance during this time.
Mar 24, 16:46 PDT

Scheduled - On Tuesday, March 25 from 01:00 to 02:30 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service.

We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support).

# Impact

During the database downtime and recovery period, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs.

- Jobs execution delay

All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput.

- Table creation errors while maintenance is underway

Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period.

- Console execution delay

Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).

- Data Access API (beta) returns errors during downtime

Data Access API (Plazma Public API) for Spark will return errors during maintenance.

- Treasure Workflow delay and failure

We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary.

- Workflow REST API will be unavailable

During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete.

- Workflow operations in Console and CLI will be unavailable

Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations.

- Presto JDBC/ODBC queries and CDP segmentation queries failure

JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed.

- Console Table preview update delay

The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal.

- The REST API to submit and cancel jobs will be unavailable

During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code.

- Streaming Ingress / Egress connectors will be unavailable

The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete.

- ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable

The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal.

- ADL (Active Data Layer) service will be unavailable

The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal.

If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried.

# Communication

Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed.

If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.
Feb 21, 11:09 PST

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

No incidents reported.

Mar 20, 2025

No incidents reported.

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents