THIS IS A SCHEDULED EVENT Apr <var data-var='date'>14</var>, <var data-var='time'>18:00</var> - <var data-var='time'>19:00</var> PDTMar <var data-var='date'>11</var>, <var data-var='time'>19:53</var> PDT Scheduled - On Wednesday, Apr 15th, 2026 from 01:00 to 02:00 UTC, we will be performing maintenance on the CDP database. During this maintenance, we will apply patches and updates to databases used by the CDP API. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. # Impact During the database downtime and recovery period, customers may experience the following: - The CDP API (api-cdp.eu01.treasuredata.com) will be unavailable The CDP API endpoints, that are mainly used for TD Console, will be unavailable during the maintenance and will respond with a 500 error code. And also CDP related features on TD Console will be unavailable. (NOTE: Profiles API and TD API won’t be affected by this maintenance.) - CDP related Workflow execution delay CDP-related Workflow will be delayed and will be automatically retried until they succeed after the downtime period. # 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.

[EU Region] Scheduled CDP Database Maintenance

Mar <var data-var='date'> 3</var>, <var data-var='time'>17:54</var> PST Completed - The database maintenance has been completed. All systems are operating normally.Mar <var data-var='date'> 3</var>, <var data-var='time'>17:19</var> PST Verifying - The database update operation has been completed, and the results are currently being verified.Mar <var data-var='date'> 3</var>, <var data-var='time'>17:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 2</var>, <var data-var='time'>18:40</var> PST Update - We will be undergoing scheduled maintenance during this time.Jan <var data-var='date'>29</var>, <var data-var='time'>00:30</var> PST Scheduled - On Wednesday, March 4 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support). # Impact During the database downtime and recovery period, customers may experience the following: - Engage Studio REST APIs During the maintenance window, operating resources in Engage Studio (Email Domains, Sender Profiles, Campaigns, etc) will be unavailable. If you encounter errors during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Engage Studio Message Deliveries Message deliveries across all channels (such as Email, Mobile Push) will be delayed and automatically retried. We encourage you to check any campaigns running during the maintenance window and re-run them if failed. - AI Agent Foundry, Foundry Workspace During the maintenance window, chat and conversation requests with LLM models will fail. Any REST API requests to the AI Agent Foundry or Foundry Workspace will result in 5xx errors. Please try again after the maintenance is done. - Streaming, Mobile, and JavaScript/Browser imports delay During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs. - Jobs execution delay All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. - Table creation errors while maintenance is underway Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above). - Data Access API (beta) returns errors during downtime Data Access API (Plazma Public API) for Spark will return errors during maintenance. - Treasure Workflow delay and failure We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary. - Workflow REST API will be unavailable During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Treasure Workflow operations in Console and CLI will be unavailable Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations. - Presto JDBC/ODBC queries and CDP segmentation queries failure JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed. - Console Table preview update delay The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal. - The REST API to submit and cancel jobs will be unavailable During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code. - Streaming Ingress / Egress connectors will be unavailable The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete. - ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal. - ADL (Active Data Layer) service will be unavailable The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.

[AP03 Region] Database Maintenance

Mar <var data-var='date'> 2</var>, <var data-var='time'>18:50</var> PST Completed - The database maintenance has been completed. All systems are operating normally.Mar <var data-var='date'> 2</var>, <var data-var='time'>18:26</var> PST Verifying - The database update operation has been completed, and the results are currently being verified.Mar <var data-var='date'> 2</var>, <var data-var='time'>17:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 2</var>, <var data-var='time'>18:40</var> PST Update - We will be undergoing scheduled maintenance during this time.Jan <var data-var='date'>29</var>, <var data-var='time'>00:23</var> PST Scheduled - On Tuesday, March 3 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support). # Impact During the database downtime and recovery period, customers may experience the following: - Engage Studio REST APIs During the maintenance window, operating resources in Engage Studio (Email Domains, Sender Profiles, Campaigns, etc) will be unavailable. If you encounter errors during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Engage Studio Message Deliveries Message deliveries across all channels (such as Email, Mobile Push) will be delayed and automatically retried. We encourage you to check any campaigns running during the maintenance window and re-run them if failed. - AI Agent Foundry, Foundry Workspace During the maintenance window, chat and conversation requests with LLM models will fail. Any REST API requests to the AI Agent Foundry or Foundry Workspace will result in 5xx errors. Please try again after the maintenance is done. - Streaming, Mobile, and JavaScript/Browser imports delay During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs. - Jobs execution delay All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. - Table creation errors while maintenance is underway Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above). - Data Access API (beta) returns errors during downtime Data Access API (Plazma Public API) for Spark will return errors during maintenance. - Treasure Workflow delay and failure We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary. - Workflow REST API will be unavailable During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Treasure Workflow operations in Console and CLI will be unavailable Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations. - Presto JDBC/ODBC queries and CDP segmentation queries failure JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed. - Console Table preview update delay The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal. - The REST API to submit and cancel jobs will be unavailable During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code. - Streaming Ingress / Egress connectors will be unavailable The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete. - ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal. - ADL (Active Data Layer) service will be unavailable The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.

[EU Region] Database Maintenance

Feb <var data-var='date'>25</var>, <var data-var='time'>18:52</var> PST Completed - The database maintenance has been completed. All systems are operating normally.Feb <var data-var='date'>25</var>, <var data-var='time'>17:36</var> PST Verifying - The database update operation has been completed, and the results are currently being verified.Feb <var data-var='date'>25</var>, <var data-var='time'>17:01</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 2</var>, <var data-var='time'>18:39</var> PST Update - We will be undergoing scheduled maintenance during this time.Jan <var data-var='date'>29</var>, <var data-var='time'>00:20</var> PST Scheduled - On Thursday, February 26 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support). # Impact During the database downtime and recovery period, customers may experience the following: - Engage Studio REST APIs During the maintenance window, operating resources in Engage Studio (Email Domains, Sender Profiles, Campaigns, etc) will be unavailable. If you encounter errors during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Engage Studio Message Deliveries Message deliveries across all channels (such as Email, Mobile Push) will be delayed and automatically retried. We encourage you to check any campaigns running during the maintenance window and re-run them if failed. - AI Agent Foundry, Foundry Workspace During the maintenance window, chat and conversation requests with LLM models will fail. Any REST API requests to the AI Agent Foundry or Foundry Workspace will result in 5xx errors. Please try again after the maintenance is done. - Streaming, Mobile, and JavaScript/Browser imports delay During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs. - Jobs execution delay All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. - Table creation errors while maintenance is underway Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above). - Data Access API (beta) returns errors during downtime Data Access API (Plazma Public API) for Spark will return errors during maintenance. - Treasure Workflow delay and failure We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary. - Workflow REST API will be unavailable During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Treasure Workflow operations in Console and CLI will be unavailable Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations. - Presto JDBC/ODBC queries and CDP segmentation queries failure JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed. - Console Table preview update delay The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal. - The REST API to submit and cancel jobs will be unavailable During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code. - Streaming Ingress / Egress connectors will be unavailable The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete. - ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal. - ADL (Active Data Layer) service will be unavailable The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.

[Tokyo Region] Database Maintenance

Feb <var data-var='date'>24</var>, <var data-var='time'>18:55</var> PST 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.Feb <var data-var='date'>24</var>, <var data-var='time'>17:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 2</var>, <var data-var='time'>18:39</var> PST Update - We will be undergoing scheduled maintenance during this time.Jan <var data-var='date'>27</var>, <var data-var='time'>22:34</var> PST Scheduled - On Wednesday, February 25 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support). # Impact During the database downtime and recovery period, customers may experience the following: - Engage Studio REST APIs During the maintenance window, operating resources in Engage Studio (Email Domains, Sender Profiles, Campaigns, etc) will be unavailable. If you encounter errors during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Engage Studio Message Deliveries Message deliveries across all channels (such as Email, Mobile Push) will be delayed and automatically retried. We encourage you to check any campaigns running during the maintenance window and re-run them if failed. - AI Agent Foundry, Foundry Workspace During the maintenance window, chat and conversation requests with LLM models will fail. Any REST API requests to the AI Agent Foundry or Foundry Workspace will result in 5xx errors. Please try again after the maintenance is done. - Streaming, Mobile, and JavaScript/Browser imports delay During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs. - Jobs execution delay All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. - Table creation errors while maintenance is underway Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above). - Data Access API (beta) returns errors during downtime Data Access API (Plazma Public API) for Spark will return errors during maintenance. - Treasure Workflow delay and failure We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary. - Workflow REST API will be unavailable During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Treasure Workflow operations in Console and CLI will be unavailable Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations. - Presto JDBC/ODBC queries and CDP segmentation queries failure JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed. - Console Table preview update delay The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal. - The REST API to submit and cancel jobs will be unavailable During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code. - Streaming Ingress / Egress connectors will be unavailable The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete. - ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal. - ADL (Active Data Layer) service will be unavailable The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.

[US Region] Database Maintenance

Feb <var data-var='date'>23</var>, <var data-var='time'>18:19</var> PST Completed - The database maintenance has been completed. All systems are operating normally.Feb <var data-var='date'>23</var>, <var data-var='time'>18:06</var> PST Verifying - The database update operation has been completed, and the results are currently being verified.Feb <var data-var='date'>23</var>, <var data-var='time'>18:04</var> PST Update - The database update operation has been completed, and the results are currently being verified.Feb <var data-var='date'>23</var>, <var data-var='time'>17:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 2</var>, <var data-var='time'>18:38</var> PST Update - We will be undergoing scheduled maintenance during this time.Jan <var data-var='date'>26</var>, <var data-var='time'>22:45</var> PST Scheduled - On Tuesday, February 24 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure Data Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure Data Platform. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasuredata.com/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasuredata.com/display/public/PD/Contacting+Technical+Support). # Impact During the database downtime and recovery period, customers may experience the following: - Engage Studio REST APIs During the maintenance window, operating resources in Engage Studio (Email Domains, Sender Profiles, Campaigns, etc) will be unavailable. If you encounter errors during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Engage Studio Message Deliveries Message deliveries across all channels (such as Email, Mobile Push) will be delayed and automatically retried. We encourage you to check any campaigns running during the maintenance window and re-run them if failed. - AI Agent Foundry and Foundry Workspace will be unavailable During the maintenance window, chat and conversation requests with LLM models will fail. Any REST API requests to the AI Agent Foundry or Foundry Workspace will result in 5xx errors. Please try again after the maintenance is done. - Streaming, Mobile, and JavaScript/Browser imports delay During most of the maintenance period, Streaming Import requests will continue to be accepted as usual. However, these requests may be queued until after the database maintenance is complete. The service may be temporarily unavailable for approximately 180 seconds during maintenance, returning a 500 error response. During this brief period, clients may encounter temporary errors or timeouts. Once maintenance is complete, retrying the request should allow it to proceed successfully. We expect stream import processing to experience some delays during recovery. The same impact will apply to Mobiles (Android, iOS, and Unity SDKs), Data Ingestion APIs, and Postback APIs. - Jobs execution delay All jobs (Presto, Hive, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. - Table creation errors while maintenance is underway Any REST API requests to create tables during the maintenance period will result in an error. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. These delays will show because the Parent Segments, Segments, and Workflows jobs will be temporarily unavailable. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above). - Data Access API (beta) returns errors during downtime Data Access API (Plazma Public API) for Spark will return errors during maintenance. - Treasure Workflow delay and failure We will attempt to retry any failed workflows, but some long-running workflows may be terminated if they run for more than a few minutes. We encourage you to check any failed workflows and re-run them if necessary. - Workflow REST API will be unavailable During the maintenance window, it will be impossible to create or update Workflow Projects, Settings related to Audience Studio (including Parent Segment, Segment, Customer Journey Orchestration, etc.), and Predictive Scoring. If you encounter errors using the Workflow REST API during maintenance, please wait for an update on our status page and re-execute your tasks when we indicate that maintenance is complete. - Treasure Workflow operations in Console and CLI will be unavailable Workflow-related operations in the Console and CLI may fail during the maintenance. Once we indicate on our status page that service has returned to normal, you can resume regular Workflow-related operations. - Presto JDBC/ODBC queries and CDP segmentation queries failure JDBC/ODBC queries which access “api-presto.treasuredata.com” will result in an error. Additionally, queries from the CDP Segmentation UI in the Treasure Data Console will be unavailable. We suggest retrying queries after the database maintenance is complete. Scheduled Presto queries in Workflow or Console won't be affected and will automatically run once the maintenance has been completed. - Console Table preview update delay The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. Once maintenance is complete, it will return to normal. - The REST API to submit and cancel jobs will be unavailable During the maintenance, the REST API endpoints for job submission and cancellation will be unavailable and will respond with a 500 error code. - Streaming Ingress / Egress connectors will be unavailable The Streaming Ingress / Egress connectors will be unavailable during the maintenance. This will return to normal once maintenance is complete. - ADH (Ads Data Hub) and DCR (Data Clean Room) service will be unavailable The ADH and DCR services will be temporarily unavailable during the scheduled maintenance. Once the maintenance is complete, services will resume as normal. - ADL (Active Data Layer) service will be unavailable The ADL service will be temporarily unavailable during the scheduled maintenance due to its dependencies on other services undergoing maintenance. Once the maintenance is complete, services will resume as normal. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at support@treasuredata.com to recover the jobs. To avoid data duplication in your systems from Treasure Data exports, Integration Export jobs won’t be automatically retried. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasuredata.com.

[Korea Region] Database Maintenance

Feb <var data-var='date'>18</var>, <var data-var='time'>14:00</var> PST Resolved - This incident has been resolved.Feb <var data-var='date'>18</var>, <var data-var='time'>13:32</var> PST Monitoring - The performance went back to normal, and no errors are observed now. We will monitor at least for 15 minutes.Feb <var data-var='date'>18</var>, <var data-var='time'>13:27</var> PST Identified - We have partially resolved the incident. We are continuously working to resolve the incident.Feb <var data-var='date'>18</var>, <var data-var='time'>12:45</var> PST Investigating - We are investigating a possible problem currently affecting Treasure Insights. We will provide an update as soon as we know more.

US region: Treasure Insights unavailable

Jan <var data-var='date'>20</var>, <var data-var='time'>21:07</var> PST 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 <var data-var='date'>20</var>, <var data-var='time'>20:41</var> 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 <var data-var='date'>20</var>, <var data-var='time'>20:12</var> 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 <var data-var='date'>20</var>, <var data-var='time'>20:06</var> 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 <var data-var='date'>20</var>, <var data-var='time'>19:40</var> PST Update - We are continuing to work on a fix for this issue.Jan <var data-var='date'>20</var>, <var data-var='time'>19:37</var> 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 <var data-var='date'>20</var>, <var data-var='time'>18:55</var> 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

[US/Tokyo Region] Performance issues

Jan <var data-var='date'>20</var>, <var data-var='time'>18:17</var> PST 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 <var data-var='date'>20</var>, <var data-var='time'>18:11</var> PST Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.Jan <var data-var='date'>20</var>, <var data-var='time'>18:01</var> 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 <var data-var='date'>20</var>, <var data-var='time'>16:59</var> 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.Nov <var data-var='date'>25</var>, <var data-var='time'>20:59</var> 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.

Jan <var data-var='date'>20</var>, <var data-var='time'>17:22</var> PST 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 <var data-var='date'>20</var>, <var data-var='time'>17:15</var> PST Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.Jan <var data-var='date'>20</var>, <var data-var='time'>17:00</var> 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 <var data-var='date'>20</var>, <var data-var='time'>16:00</var> 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.Nov <var data-var='date'>25</var>, <var data-var='time'>20:56</var> 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.

Jan <var data-var='date'>19</var>, <var data-var='time'>18:13</var> PST 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 <var data-var='date'>19</var>, <var data-var='time'>18:08</var> PST Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.Jan <var data-var='date'>19</var>, <var data-var='time'>18:01</var> 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 <var data-var='date'>19</var>, <var data-var='time'>17:01</var> 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.Nov <var data-var='date'>25</var>, <var data-var='time'>20:50</var> 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.

Jan <var data-var='date'>19</var>, <var data-var='time'>17:23</var> PST 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 <var data-var='date'>19</var>, <var data-var='time'>17:16</var> PST Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.Jan <var data-var='date'>19</var>, <var data-var='time'>17:00</var> 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 <var data-var='date'>19</var>, <var data-var='time'>16:00</var> 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.Nov <var data-var='date'>25</var>, <var data-var='time'>20:46</var> 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.

Jan <var data-var='date'>18</var>, <var data-var='time'>17:16</var> PST 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 <var data-var='date'>18</var>, <var data-var='time'>17:10</var> PST Verifying - We've applied patches and performance improvements to our systems. We are validating that all systems are working correctly.Jan <var data-var='date'>18</var>, <var data-var='time'>17:01</var> 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 <var data-var='date'>18</var>, <var data-var='time'>16:01</var> 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.Nov <var data-var='date'>25</var>, <var data-var='time'>20:36</var> 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.

Jan <var data-var='date'> 5</var>, <var data-var='time'>06:11</var> PST Completed - The scheduled maintenance has been completed.Jan <var data-var='date'> 5</var>, <var data-var='time'>06:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Nov <var data-var='date'>26</var>, <var data-var='time'>13:41</var> PST Scheduled - 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.

[US/Tokyo/EU] Realtime 2.0 Database Maintenance

Dec <var data-var='date'> 9</var>, <var data-var='time'>22:03</var> PST Resolved - An unexpected behavior occurred in the REST API "GET /v3/job/result/{job_id}" which caused it to return only a partial set of results. This issue stemmed from an update to the job result download mechanism implemented around 2025/12/09 01:00 (UTC). The issue was resolved after a fix was applied around 2025/12/10 04:36(UTC). The affected API is used through the following methods: - Directly calling the REST API - Using functions in libraries (e.g., pytd) that reference job results - Toolbelt commands that refers to job results - Setting store_last_results:true in the td>:/td_run> operator in Treasure Workflows - Using the td_for_each>, td_wait> and td_wait_table>: operators in Treasure Workflows Unfortunately, we are unable to identify which API requests were affected. Please compare the number of results retrieved by your job with the download results to see if you were affected. We sincerely apologize for the inconvenience this has caused.

[All Regions] REST API sometimes returns only partial job result

Dec <var data-var='date'> 5</var>, <var data-var='time'>01:30</var> PST Resolved - We confirmed the third-party service is now operational. The incident has been resolved.Dec <var data-var='date'> 5</var>, <var data-var='time'>01:22</var> PST Monitoring - The third-party service provider has implemented a fix. We are monitoring the results.Dec <var data-var='date'> 5</var>, <var data-var='time'>01:18</var> PST Investigating - We are currently experiencing issues accessing Treasure Insights. Our investigation has identified that this is caused by an outage with a third-party service provider utilized by Treasure Insights. We are monitoring the situation and working with the provider to resolve the issue. We will provide updates as soon as more information becomes available.

[All Region] Service Disruption on Treasure Insights

Dec <var data-var='date'> 3</var>, <var data-var='time'>00:10</var> PST Completed - The scheduled maintenance has been completed.Oct <var data-var='date'>30</var>, <var data-var='time'>17:30</var> PDT Scheduled - On December 3rd, 2025 from 06:00-09:00 UTC, the databases supporting our AI Agent Foundry will undergo a short maintenance. This maintenance is required to apply upgrades, security patches, and performance improvements to our databases. We'll be updating regions by the following schedule: 06:00-07:00 UTC (02:00-03:00 EST) - US Region 07:00-08:00 UTC (07:00-08:00 GMT) - EU Region 08:00-09:00 UTC (17:00-18:00 JST) - Japan Region During the maintenance window, the backend databases supporting the AI Agent Foundry and Foundry Workspace on Treasure Data Platform will undergo a version upgrade. Customers will experience failures: * Requests to the APIs for AI will receive HTTP 5XX errors. * Chat and conversation requests with LLM models will fail. Please retry any failed requests after the maintenance period is complete. Beyond this notice, we will provide updates approximately one hour before the maintenance window begins, at the start and completion of the operation, and once verification is complete. At that time, all systems will have returned to full functionality, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this maintenance, please feel free to reach out to our Support team at support@treasure-data.com.

[All Regions] Database maintenance for AI Agent Foundry

Nov <var data-var='date'>25</var>, <var data-var='time'>07:07</var> PST Completed - The scheduled maintenance has been finished, with upgrades to all sites finished.Nov <var data-var='date'>25</var>, <var data-var='time'>06:47</var> PST Verifying - All sites have been upgraded. We're currently verifying the upgrade and monitoring for regressions.Nov <var data-var='date'>25</var>, <var data-var='time'>06:32</var> PST Update - All sites except for the environment in Korea have been upgraded, and we're verifying the status and monitoring for regressions.Nov <var data-var='date'>25</var>, <var data-var='time'>06:06</var> PST Update - Maintenance is still in progress, pending the resource creation by the infrastructure provider, which is taking longer than expected, but is near completion.Nov <var data-var='date'>25</var>, <var data-var='time'>05:39</var> PST Update - Maintenance is still in progress, pending the resource creation by the infrastructure provider, which is taking longer than expected. We will keep updating this page every 30 minutes.Nov <var data-var='date'>25</var>, <var data-var='time'>05:01</var> PST Update - Maintenance is still in progress, but the completion is delayed as we await resource creation on our infrastructure provider, which is taking longer than expected.Nov <var data-var='date'>25</var>, <var data-var='time'>04:35</var> PST Update - Maintenance is still in progress.Nov <var data-var='date'>25</var>, <var data-var='time'>04:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates every 30 minutes, or as necessary.Nov <var data-var='date'>25</var>, <var data-var='time'>02:57</var> PST Update - The scheduled maintenance window for the databases supporting PrecisionML will begin in 1h, from 12:00-13:00 UTC, today (November 25th, 2025).Oct <var data-var='date'>28</var>, <var data-var='time'>10:00</var> PDT Scheduled - On November 25th, 2025, from 12:00-13:00 UTC, the databases supporting PrecisionML will undergo a short maintenance period. We'll be upgrading the databases supporting the PrecisionML feature of the Treasure Data Platform. This upgrade is necessary to apply the latest available performance and security patches. During the maintenance window, customers may experience momentary failures or have PrecisionML runs not created or executed. Any failures will be automatically retried from Treasure Workflow, and no customer action is required to ensure all runs complete. # Communication 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 verification is complete. At that time, all systems will have returned to full functionality, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this maintenance, please feel free to reach out to our Support team at support@treasure-data.com.

[All Regions] PrecisionML Database Maintenance

Nov <var data-var='date'>17</var>, <var data-var='time'>22:00</var> PST Completed - The scheduled maintenance has been completed.Nov <var data-var='date'>17</var>, <var data-var='time'>19:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Nov <var data-var='date'> 5</var>, <var data-var='time'>01:54</var> PST Update - We will be undergoing scheduled maintenance during this time.Oct <var data-var='date'>12</var>, <var data-var='time'>23:53</var> PDT Scheduled - We are pleased to inform you that we will upgrade our DataTank 2.0 PostgreSQL database engine to version 14.18. This upgrade is part of our commitment to maintaining the highest levels of performance, security, and reliability for your data. *Key benefits of upgrading to version 14.18: - Enhanced performance: Improvements that boost query efficiency and overall system responsiveness. - Increased security: Security patches and updates to protect your data - New features: access to new features and functionalities of PostgreSQL *Upgrade details: - Expected Downtime: 10 minutes per instance. We aim to make this transition as smooth as possible. Our team will be monitoring the process closely to ensure minimal disruption. If you have any questions or concerns, please don’t hesitate to contact our support team. During the maintenance window, the databases will experience a short failover within 120 seconds, after which the respective systems are expected to recover in approximately 10 minutes. During the failover period, customers will observe that the DataTank 2.0 database system might not function properly

[Tokyo/AP03 Regions] DataTank 2.0 maintenance

Nov <var data-var='date'>11</var>, <var data-var='time'>23:00</var> PST Completed - The scheduled maintenance has been completed.Nov <var data-var='date'>11</var>, <var data-var='time'>19:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Nov <var data-var='date'> 5</var>, <var data-var='time'>01:49</var> PST Update - We will be undergoing scheduled maintenance during this time.Oct <var data-var='date'>12</var>, <var data-var='time'>23:46</var> PDT Update - We will be undergoing scheduled maintenance during this time.Oct <var data-var='date'>12</var>, <var data-var='time'>23:46</var> PDT Scheduled - We are pleased to inform you that we will upgrade our DataTank 2.0 PostgreSQL database engine to version 14.18. This upgrade is part of our commitment to maintaining the highest levels of performance, security, and reliability for your data. *Key benefits of upgrading to version 14.18: - Enhanced performance: Improvements that boost query efficiency and overall system responsiveness. - Increased security: Security patches and updates to protect your data - New features: access to new features and functionalities of PostgreSQL *Upgrade details: - Expected Downtime: 10 minutes for your instance We aim to make this transition as smooth as possible. Our team will be monitoring the process closely to ensure minimal disruption. If you have any questions or concerns, please don’t hesitate to contact our support team. During the maintenance window, the databases will experience a short failover within 120 seconds, after which the respective systems are expected to recover in approximately 10 minutes. During the failover period, customers will observe that the DataTank 2.0 database system might not function properly

[US/Korea/EU Regions] DataTank 2.0 maintenance

Nov <var data-var='date'> 4</var>, <var data-var='time'>23:58</var> PST Resolved - Services have been restored to normal operations, and all of our systems are reporting healthy once again. If you observe any lingering issues, please connect with our support team, and we would be happy to help: https://docs.treasuredata.com/articles/#!pd/contacting-treasure-data-supportNov <var data-var='date'> 4</var>, <var data-var='time'>19:55</var> PST Monitoring - A fix has been implemented and we are monitoring the results.Nov <var data-var='date'> 4</var>, <var data-var='time'>19:49</var> PST Investigating - We have encountered a temporary issue with the availability of Premium Audit Logs for Artificial Intelligence services (AI Agent Foundry and Audience Agent) during the period of November 4th 23:19:26 UTC to November 5th 00:57:55 UTC. While some data during this period may not have been captured, our engineering team is actively investigating the situation. We are taking all necessary steps to restore full service and ensure that all future logs are recorded without issue. We apologize for any inconvenience this may have caused and will keep you updated on our progress.

[All Regions] Temporary Interruption in Premium AI Audit Logs

Oct <var data-var='date'>20</var>, <var data-var='time'>16:15</var> PDT Resolved - Services have been restored to normal operations, and all of our systems are reporting healthy once again. If you observe any lingering issues, please connect with our support team, and we would be happy to help: https://docs.treasuredata.com/articles/#!pd/contacting-treasure-data-supportOct <var data-var='date'>20</var>, <var data-var='time'>14:42</var> PDT Update - Service levels continue to improve as upstream services become more stable. Users may still see processing delays, though those should be decreasing as we process the backlog of messages from this event. We are continuing to monitor our systems and deploy capacity as needed. We will update you with additional information as it develops.Oct <var data-var='date'>20</var>, <var data-var='time'>12:35</var> PDT Monitoring - We are seeing continued recovery across our systems, and are currently working to process any buffered or delayed messages. Customers may continue to observe delays in data processing and may notice slower-than-usual processing of configuration changes. We expect these delays to decrease as our systems catch up. Our team is continuing to track recovery closely, and we'll inform you of any new developments.Oct <var data-var='date'>20</var>, <var data-var='time'>11:49</var> PDT Update - We are continuing to monitor ongoing recovery efforts, and most of our systems remain operating. As the situation with our upstream provider develops we will react if we discover any new issues. At this time, we are observing delays in our systems, including Profile API 1.0 and Realtime 2.0. Requests are being processed as they have been received, but users may see a slowdown in results, and may notice delays when updating configurations or journeys. You may notice continued slower performance or unexpected errors. We are working with our service provider to address these issues and will provide an update with new information soon.Oct <var data-var='date'>20</var>, <var data-var='time'>08:05</var> PDT Update - Our upstream service provider is gradually recovering its services, and our services are gradually recovering too. Most of our Treasure Data services are back to normal except for Custom Script, autoML and realtime services such as profile API 1.0, and realtime 2.0. As the upstream service provider incident is still ongoing, you might still encounter unexpected errors or issues. We will closely monitoring our services and work with our upstream service provider.Oct <var data-var='date'>20</var>, <var data-var='time'>01:27</var> PDT Investigating - We are currently investigating an issue originating from an upstream service provider used by our infrastructure. This may be affecting the normal operation of some Treasure Data services. We are working to determine the scope of the impact. Observed symptoms may include, but are not limited to, the failure of various jobs (such as Trino, Hive, Result Export, Import, and Custom Script execution) to start. Our team is actively monitoring the situation and working with the provider. We will provide further updates as more information becomes available.

[US Region] Issue Affecting Treasure Data Services

Oct <var data-var='date'>20</var>, <var data-var='time'>14:32</var> PDT Resolved - Delays should be improving for all customers, and services should be returning to normal. Given the similarity of the two issues, we'll continue tracking any concerns related to this interruption as part of the "[US Region] Issue Affecting Treasure Data Services" issue. For further updates, please track here: https://status.treasuredata.com/incidents/w7v5wtmkdllj If you experience continued issues specifically relating to our Profiles API or SSO Logins, please contact our support team: https://docs.treasuredata.com/articles/#!pd/contacting-treasure-data-supportOct <var data-var='date'>20</var>, <var data-var='time'>11:53</var> PDT Identified - We are continuing to work with our service provider to track this issue. Customers may continue to observe higher latency than normal and may notice delays in processing. We are monitoring the situation closely and are adding additional capacity in anticipation of a recovery. As this situation develops, we will keep you updated on any changes in expected behavior.Oct <var data-var='date'>20</var>, <var data-var='time'>08:09</var> PDT Update - Our upstream service provider is gradually recovering its services, and our services are gradually recovering too. SSO login is working fine, however profile API 1.0 is still recovering its service with latency. As the upstream service provider incident is still ongoing, you might still encounter unexpected errors or issues. We will closely monitoring our services and work with our upstream service provider.Oct <var data-var='date'>20</var>, <var data-var='time'>03:15</var> PDT Update - We are also investigating reports indicating that this incident might be causing login errors for customers using SSO (Single Sign-On) to log into our service. Customers attempting a new login via SSO may be unable to access the service. We believe users who are already logged in (have an active session) and users logging in with methods other than SSO (e.g., username/password) are not affected by this login issue. We are working to confirm this.Oct <var data-var='date'>20</var>, <var data-var='time'>01:53</var> PDT Investigating - We are aware of an issue affecting log writing and reading for the Profile API in all regions. This is due to an incident with an upstream service. Our team is monitoring the provider's status. We will provide an update shortly.

[All Regions] Profile API Errors and SSO Logins

Oct <var data-var='date'>16</var>, <var data-var='time'>18:55</var> PDT Resolved - After a successful monitoring period, we can confirm that our fix is working and the issue is now resolved. Thank you for your patience.Oct <var data-var='date'>15</var>, <var data-var='time'>22:05</var> PDT Monitoring - We've identified that an internal component between our query engine which extracts the number of records that match Segment rules and Audience Studio ran into a capacity issue during a specific time. We have increased the capacity and will continue to monitor the situation. If the issue does not reoccur by approximately 2025/10/17 01:00 (+00:00), we will consider this incident resolved and close this.Oct <var data-var='date'>15</var>, <var data-var='time'>11:16</var> PDT Investigating - We are currently investigating an issue where some customers are experiencing intermittent “query expired” errors when retrieving segment counts in Audience Studio. In many cases, queries may succeed after a retry, but this behavior can impact the ability to view or use segment results reliably. Our engineering teams are actively investigating the root cause and working to mitigate the issue. We will provide updates here as soon as more information becomes available. In the meantime, affected users may be able to work around the issue by retrying the query after a short interval.

[ US region ]  Audience Studio – Intermittent Query Expired Errors When Retrieving Segment Counts

Oct <var data-var='date'>14</var>, <var data-var='time'>22:06</var> PDT Resolved - The issue has been fully resolved. Thank you for your patience.Oct <var data-var='date'>14</var>, <var data-var='time'>21:38</var> PDT Monitoring - The issue has been addressed with an applied fix. We are currently monitoring the system to ensure the services are fully restored and stable. Thank you for your patience while we addressed this.Oct <var data-var='date'>14</var>, <var data-var='time'>19:52</var> PDT Identified - The issue has been identified and a fix is being implemented.Oct <var data-var='date'>14</var>, <var data-var='time'>19:05</var> PDT Investigating - We are currently experiencing an issue with email delivery for Treasure Data system emails, such as password resets. The affected email deliveries are: * Default email notification of Treasure Workflow * Password reset * New user invitation * Password change * Email address change * User lock notifications The following emails are NOT affected: * Email delivery with the mail>: operator of Treasure Workflow * Email delivery with Engage Studio Our team is actively working to resolve this issue. We sincerely apologize for any inconvenience or disruption this may cause.

Is Treasure Data down?

Treasure Data status is UP

Lastest published events

[EU Region] Scheduled CDP Database Maintenance

[AP03 Region] Database Maintenance

[EU Region] Database Maintenance

Treasure Data Services, Components and Regions

Recent Treasure Data events

[EU Region] Scheduled CDP Database Maintenance

[AP03 Region] Database Maintenance

[EU Region] Database Maintenance

[Tokyo Region] Database Maintenance

[US Region] Database Maintenance

[Korea Region] Database Maintenance

Get your FREE account now,
5 monitors included!

Is Treasure Data down?

Treasure Data status is UP

Lastest published events

[EU Region] Scheduled CDP Database Maintenance

[AP03 Region] Database Maintenance

[EU Region] Database Maintenance

Treasure Data Services, Components and Regions

Recent Treasure Data events

[EU Region] Scheduled CDP Database Maintenance

[AP03 Region] Database Maintenance

[EU Region] Database Maintenance

[Tokyo Region] Database Maintenance

[US Region] Database Maintenance

[Korea Region] Database Maintenance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!