Treasure Data Status

Jan 21, 2026

No incidents reported today.

Jan 20, 2026

Resolved - Incident Impact Summary (Plazma / Table Resources)

We have confirmed that the system in the Tokyo region is operating normally with no remaining issues.

What happened
- All operations accessing Plazma table resources experienced increased latency.

When
- US region: 17:00 PST – 18:40 PST
- Tokyo region: 09:00 JST – 12:50 JST

Temporary impact during recovery
- Updates to table row counts and preview data were temporarily paused.

Recovery status
- US region: Table metadata updates resumed at 20:00 PST.
- Tokyo region: Table metadata updates resumed at 13:40 JST.
Both regions are now fully recovered.

Data integrity
- No data loss or data corruption occurred.

We will prepare and publish a post-mortem document to explain the circumstances under which this incident occurred one day after the recent system maintenance.

With this confirmation, the incident is now closed.
Jan 20, 21:07 PST

Monitoring - The system in the US region is operating normally with no observed issues.

In the Tokyo region, table metadata updates have also been resumed. At this point, the Tokyo region is expected to be fully recovered, and we will continue to monitor system performance.

Once stability is fully confirmed, we plan to close this status page.
Jan 20, 20:41 PST

Update - In the US region, table metadata updates have been resumed. At this point, the system in the US region is expected to be fully recovered, and we are continuing to monitor it closely.

For the Tokyo region, metadata updates will be resumed after we complete confirmation of system performance. We will provide another update when this step begins.
Jan 20, 20:12 PST

Update - Performance in the Tokyo region improved at approximately 12:50 JST. The Tokyo region had been experiencing gradually increasing performance degradation since around 09:00 JST.
We are currently proceeding with the steps to resume updates of table metadata in Data Workbench.

Due to the temporary pause of metadata updates, application metrics that rely on this information, such as Parent Segment size, have also been temporarily not updated.

We will continue monitoring the system and share further updates as needed.
Jan 20, 20:06 PST

Update - We are continuing to work on a fix for this issue.
Jan 20, 19:40 PST

Identified - We identified the same issue in the Tokyo region and applied database parameter tuning. We are currently assessing the impact of this change on system performance.
As a result of this temporary mitigation applied in both the US and Tokyo regions, the following impact is observed:
In Data Workbench, updates to table metadata for row counts and preview data are temporarily paused.
We will continue monitoring and provide further updates as we make progress.
Jan 20, 19:37 PST

Investigating - Starting at approximately 17:00 PST, we observed increased latency affecting all operations accessing table resources in Plazma.
At around 19:00 PST, we applied temporary tuning to the database managing table resources and confirmed recovery based on internal performance metrics.

We are currently continuing to monitor the system to ensure overall performance remains stable.

Visible impacts are:

- Streaming, Mobile, and JavaScript/Browser imports may delay

- Jobs execution may delay

- Table creation may error

- Console execution may delay

- Plazma Public API may return errors

- Treasure Workflow may delay and fail

- Workflow REST API may be unavailable

- Workflow operations in Console and CLI may become unavailable

- Presto JDBC/ODBC queries and CDP segmentation queries may fail

- Console Table preview update may delay

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

- Data Connector Integrations may become unavailable

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

- ADL (Active Data Layer) service may be unavailable

We will send an additional update in 30 minutes
Jan 20, 18:55 PST

[AP03 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.
Jan 20, 18:17 PST

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Jan 20, 18:11 PST

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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 20, 18:01 PST

Update - In about an hour, from 2: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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 20, 16:59 PST

Scheduled - On Jan 21, 2026, from 02:00 to 02:40 UTC (Jan 21, 2026, 11:00 to 11:40 JST), we will be performing routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to a database used by the Treasure Data Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Nov 25, 20:59 PST

[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.
Jan 20, 17:22 PST

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Jan 20, 17:15 PST

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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 20, 17:00 PST

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

# 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 20, 16:00 PST

Scheduled - On Jan 21, 2026, from 01:00 to 01:40 UTC, we will be performing routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to a database used by the Treasure Data Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Nov 25, 20:56 PST

Jan 19, 2026

[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.
Jan 19, 18:13 PST

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

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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 19, 18:01 PST

Update - In about an hour, from 2: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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 19, 17:01 PST

Scheduled - On Jan 20, 2026, from 02:00 to 02:40 UTC (Jan 20, 2026, 11:00 to 11:40 JST), we will be performing routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to a database used by the Treasure Data Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Nov 25, 20:50 PST

[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.
Jan 19, 17:23 PST

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Jan 19, 17:16 PST

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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 19, 17:00 PST

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

# 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 19, 16:00 PST

Scheduled - On Jan 20, 2026, from 01:00 to 01:40 UTC (Jan 19, 2026, 17:00 to 17:40 PST), we will be performing routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to a database used by the Treasure Data Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Nov 25, 20:46 PST

Jan 18, 2026

[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.

If you encounter any issues, please reach out to our support team.
Jan 18, 17:16 PST

Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.
Jan 18, 17:10 PST

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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 18, 17:01 PST

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

# 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Jan 18, 16:01 PST

Scheduled - On January 19, 2026 from 01:00 to 01:40 UTC (January 19, 2026 from 10:00 to 10:40 KST), we will be performing routine maintenance on the databases that power the Treasure Data Platform.

During this maintenance, we will apply patches and updates to a database used by the Treasure Data Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying 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).

- Plazma Public API returns errors during downtime

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.

- Data Connector Integrations will be unavailable

The Data Connector Integrations 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.
Nov 25, 20:36 PST

Jan 17, 2026

No incidents reported.

Jan 16, 2026

No incidents reported.

Jan 15, 2026

No incidents reported.

Jan 14, 2026

No incidents reported.

Jan 13, 2026

No incidents reported.

Jan 12, 2026

No incidents reported.

Jan 11, 2026

No incidents reported.

Jan 10, 2026

No incidents reported.

Jan 9, 2026

No incidents reported.

Jan 8, 2026

No incidents reported.

Jan 7, 2026

No incidents reported.

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents