All Systems Operational
About This Site
This is Treasure Data's status page.
We believe that trust starts with full transparency.
US
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Data Tank 2.0
Operational
Realtime 2.0
Operational
Tokyo
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Data Tank 2.0
Operational
Realtime 2.0
Operational
EU
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Data Tank 2.0
Operational
Realtime 2.0
Operational
Korea
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Data Tank 2.0
Operational
AP03
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
ADL
Operational
Data Tank 2.0 / ACID DWH
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
[US/Tokyo/EU] Realtime 2.0 Database Maintenance Jan 5, 2026 06:00-07:00 PST
Realtime Database Maintenance
Upcoming scheduled maintenance notice on January 5th, 2026 from 14:00 to 15:00 UTC - the backend databases supporting Realtime 2.0 on Treasure Data system will undergo a short maintenance window. Expected downtime is less than 10 minutes.
During the maintenance window, the databases supporting Realtime 2.0 service on Treasure Data Platform will undergo a PostgreSQL version upgrade. During this time customers attempting to launch journeys or personalizations will experience errors or lost Realtime journey or personalization updates.
Beyond this notice, we will provide updates approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is completed. At that time, all systems will have returned to full functionality and the Scheduled Maintenance will be closed.
If you have any question or concern about this maintenance, please feel free to reach out to our Support team at support@treasure-data.com.
Posted on Nov 26, 2025 - 13:41 PST
Upcoming scheduled maintenance notice on January 5th, 2026 from 14:00 to 15:00 UTC - the backend databases supporting Realtime 2.0 on Treasure Data system will undergo a short maintenance window. Expected downtime is less than 10 minutes.
During the maintenance window, the databases supporting Realtime 2.0 service on Treasure Data Platform will undergo a PostgreSQL version upgrade. During this time customers attempting to launch journeys or personalizations will experience errors or lost Realtime journey or personalization updates.
Beyond this notice, we will provide updates approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is completed. At that time, all systems will have returned to full functionality and the Scheduled Maintenance will be closed.
If you have any question or concern about this maintenance, please feel free to reach out to our Support team at support@treasure-data.com.
Posted on Nov 26, 2025 - 13:41 PST
[Korea Region] Database Maintenance Jan 18, 2026 17:00-17:40 PST
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.
Posted on Nov 25, 2025 - 20:36 PST
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.
Posted on Nov 25, 2025 - 20:36 PST
[US Region] Database Maintenance Jan 19, 2026 17:00-17:40 PST
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.
Posted on Nov 25, 2025 - 20:46 PST
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.
Posted on Nov 25, 2025 - 20:46 PST
[Tokyo Region] Database Maintenance Jan 19, 2026 18:00-18:40 PST
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.
Posted on Nov 25, 2025 - 20:50 PST
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.
Posted on Nov 25, 2025 - 20:50 PST
[EU Region] Database Maintenance Jan 20, 2026 17:00-17:40 PST
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.
Posted on Nov 25, 2025 - 20:56 PST
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.
Posted on Nov 25, 2025 - 20:56 PST
[AP03 Region] Database Maintenance Jan 20, 2026 18:00-18:40 PST
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.
Posted on Nov 25, 2025 - 20:59 PST
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.
Posted on Nov 25, 2025 - 20:59 PST