Treasure Data Outage History

Between 8:05 AM and 8:30 AM PDT, customers operating in the EU01 (Europe) region may have experienced intermittent errors (5xx) affecting two primary areas: Data Ingestion: Errors when attempting to send records via the Ingest API. Real-Time Personalization: Request failures for personalization and profile lookup services. The disruption was caused by an service interruption with an upstream provider in our data processing layer within the eu-central-1 region. This prevented our systems from successfully processing incoming data streams and executing real-time lookups during the affected window. The upstream provider has confirmed the issue is resolved. Our engineering team monitored the recovery, and we have confirmed that all services in the EU01 region have returned to normal operating parameters. Data Integrity: For data ingestion, records that were rejected with a retryable error code during this window should be resubmitted. Records that have already been successfully ingested following the recovery require no further action. Personalization: Real-time request success rates have returned to 100%. We are continuing to monitor the stability of the region. We apologize for any inconvenience this may have caused to your operations. For further questions, please contact our support team at [email protected].

Apr 14, 18:35 PDT Completed - The database maintenance has been completed. All systems are operating normally. Apr 14, 18:05 PDT Verifying - The database update operation has been completed, and the results are currently being verified. Apr 14, 18:00 PDT Update - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 14, 17:01 PDT Update - In about an hour, from 01:00 UTC, the maintenance window for the database maintenance will commence. 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. Beyond this notice, we will provide updates at the start and completion of the operation and once the verification of the new system is completed: at that time, all systems will have returned to full functionality and this Scheduled Maintenance will be closed. Mar 11, 19:53 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 [email protected].

Mar 3, 17:54 PST Completed - The database maintenance has been completed. All systems are operating normally. Mar 3, 17:19 PST Verifying - The database update operation has been completed, and the results are currently being verified. Mar 3, 17:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 18:40 PST Update - We will be undergoing scheduled maintenance during this time. Jan 29, 00:30 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 [email protected] 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 [email protected].

Mar 2, 18:50 PST Completed - The database maintenance has been completed. All systems are operating normally. Mar 2, 18:26 PST Verifying - The database update operation has been completed, and the results are currently being verified. Mar 2, 17:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 18:40 PST Update - We will be undergoing scheduled maintenance during this time. Jan 29, 00:23 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 [email protected] 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 [email protected].

Feb 25, 18:52 PST Completed - The database maintenance has been completed. All systems are operating normally. Feb 25, 17:36 PST Verifying - The database update operation has been completed, and the results are currently being verified. Feb 25, 17:01 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 18:39 PST Update - We will be undergoing scheduled maintenance during this time. Jan 29, 00:20 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 [email protected] 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 [email protected].

Feb 24, 18:55 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 24, 17:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 18:39 PST Update - We will be undergoing scheduled maintenance during this time. Jan 27, 22:34 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 [email protected] 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 [email protected].

Feb 23, 18:19 PST Completed - The database maintenance has been completed. All systems are operating normally. Feb 23, 18:06 PST Verifying - The database update operation has been completed, and the results are currently being verified. Feb 23, 18:04 PST Update - The database update operation has been completed, and the results are currently being verified. Feb 23, 17:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 18:38 PST Update - We will be undergoing scheduled maintenance during this time. Jan 26, 22:45 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 [email protected] 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 [email protected].

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