Oct <var data-var='date'> 1</var>, <var data-var='time'>00:29</var> PDT Completed - The maintenance and validations are completed. Email campaigns, sending and delivery were not affected, and all other channels remain operation. Sep <var data-var='date'>17</var>, <var data-var='time'>00:58</var> PDT Scheduled - We will perform a planned migration of the delivery feedback processing pipeline used to record email delivery, bounce, and related event information in the Email Delivery Events Table. Email sending and delivery will remain operational during this maintenance. Emails will not be resent or duplicated. Customers may observe a short delay in Email Delivery Events Table updates, and a small number of duplicate entries may be recorded while events are retried. No other Engage channels will be affected. In an extreme retry scenario, up to approximately 1,200 duplicate entries could be created. This is a theoretical upper bound, and the expected duplication volume is much lower. No customer action is required. We will monitor the migration and provide updates throughout the maintenance window.

[All Regions] Engage Studio (Email): Planned maintenance for the Email Delivery Events Table

Sep <var data-var='date'>29</var>, <var data-var='time'>21:36</var> PDT Resolved - Between Sept 28th (5:30 PM UTC) and Sept 29th (6:30 PM UTC) customers with no batch segments who had scheduled attribute updates would have seen failed jobs preventing batch data from loading into Reactor. Customers would have seen errors while waiting for the config changes to update. The impact is any realtime applications, personalizations, or campaigns during that window may have relied on stale batch attribute data. The system has recovered and workflows are now sending updated data.

[EU01 Tokyo AP03 Regions] Batch Data Load failure for RT2.0

Sep <var data-var='date'>29</var>, <var data-var='time'>14:18</var> PDT Resolved - This incident has been resolved, and our support team will be following up with affected customers. Sep <var data-var='date'>29</var>, <var data-var='time'>11:20</var> PDT Monitoring - A fix has been implemented and we have observed that jobs are succeeding. Sep <var data-var='date'>29</var>, <var data-var='time'>10:22</var> PDT Investigating - We are currently investigating batch export jobs failing to load data into Reactor in the US (AWS) region. Data updates will be delayed up to 24 hours. We will update status in one hour.

[US Region] Batch Data Load failure for RT2.0

Sep <var data-var='date'>28</var>, <var data-var='time'>06:16</var> PDT Resolved - We have identified and resolved the issue affecting the Live Chat feature for Corporate and Enterprise support plans. The service has been fully restored and is operating normally. We sincerely apologize for any inconvenience this may have caused and thank you for your patience. Sep <var data-var='date'>27</var>, <var data-var='time'>20:41</var> PDT Investigating - We are currently experiencing an issue with our Live Chat feature for Corporate and Enterprise support plans. Our team is actively investigating. You can still reach our support team as usual by emailing support@treasure.ai. We appreciate your patience and apologize for any inconvenience.

[All Regions] Live Chat Service Unavailable

Oct <var data-var='date'> 4</var>, <var data-var='time'>19:20</var> PDT Update - Transactional email delivery continues to recover, but it may take some time to return to normal levels. Delivery remains stable, and we are continuing to monitor the service. Other email services remain unaffected. We will provide another update within 14 days, or sooner if conditions change. Oct <var data-var='date'> 4</var>, <var data-var='time'>19:19</var> PDT Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>24</var>, <var data-var='time'>21:44</var> PDT Update - Transactional email delivery continues to recover, but it may take some time to return to normal levels. Delivery remains stable, and we are continuing to monitor the service. Other email services remain unaffected. We will provide another update within seven days, or sooner if conditions change. Sep <var data-var='date'>17</var>, <var data-var='time'>23:51</var> PDT Update - Transactional email delivery is recovering, but it may take some time to return to normal levels. Delivery continues to improve steadily. We are continuing to monitor the service. Other email services remain unaffected. We will provide another update within 7 days. Sep <var data-var='date'>16</var>, <var data-var='time'>23:10</var> PDT Update - Transactional email delivery is recovering, but it may take some time to return to normal levels. We are continuing to monitor the service. Other email services remain unaffected. We will provide another update within 24 hours. Sep <var data-var='date'>16</var>, <var data-var='time'>20:44</var> PDT Monitoring - Transactional email delivery is recovering, but it may take some time to return to normal levels. We are continuing to monitor the service. Other email services remain unaffected. We will provide another update within 2 hours. Sep <var data-var='date'>16</var>, <var data-var='time'>20:14</var> PDT Identified - We have identified the cause of delays affecting transactional emails from our web interface and are working on a solution. Customers may receive some emails later than expected during this time. Affected emails include system notifications and password reset requests. Other email services are operating normally. We will provide another update within 30 minutes.

[All Regions] Transactional email delivery delays

Sep <var data-var='date'> 2</var>, <var data-var='time'>18:24</var> PDT Completed - The database maintenance has been completed. All systems are operating normally. Sep <var data-var='date'> 2</var>, <var data-var='time'>18:10</var> PDT Verifying - The database update operation has been completed, and the results are currently being verified. Sep <var data-var='date'> 2</var>, <var data-var='time'>18:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>30</var>, <var data-var='time'>22:26</var> PDT Scheduled - On Thursday, Sep 3rd from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI 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.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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@treasure.ai.

[AP03 Region] Database Maintenance

Sep <var data-var='date'> 1</var>, <var data-var='time'>18:31</var> PDT Completed - The database maintenance has been completed. All systems are operating normally. Sep <var data-var='date'> 1</var>, <var data-var='time'>18:15</var> PDT Verifying - The database update operation has been completed, and the results are currently being verified. Sep <var data-var='date'> 1</var>, <var data-var='time'>18:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>30</var>, <var data-var='time'>22:24</var> PDT Scheduled - On Wednesday, Sep 2nd from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI 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.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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@treasure.ai.

[EU Region] Database Maintenance

Aug <var data-var='date'>30</var>, <var data-var='time'>18:47</var> PDT Completed - The database maintenance has been completed. All systems are operating normally. Aug <var data-var='date'>30</var>, <var data-var='time'>18:21</var> PDT Verifying - The database update operation has been completed, and the results are currently being verified. Aug <var data-var='date'>30</var>, <var data-var='time'>18:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>30</var>, <var data-var='time'>22:23</var> PDT Scheduled - On Monday, Aug 31st from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI 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.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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@treasure.ai.

[Tokyo Region] Database Maintenance

Aug <var data-var='date'>26</var>, <var data-var='time'>19:32</var> PDT Completed - The database maintenance has been completed. All systems are operating normally. Aug <var data-var='date'>26</var>, <var data-var='time'>18:25</var> PDT Verifying - The database update operation has been completed, and the results are currently being verified. Aug <var data-var='date'>26</var>, <var data-var='time'>18:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>30</var>, <var data-var='time'>22:21</var> PDT Scheduled - On Thursday, Aug 27th from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI 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.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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@treasure.ai.

[US Region] Database Maintenance

Aug <var data-var='date'>24</var>, <var data-var='time'>19:10</var> PDT Completed - The database maintenance has been completed. All systems are operating normally. Aug <var data-var='date'>24</var>, <var data-var='time'>18:41</var> PDT Verifying - Verification is currently underway for the maintenance items. Aug <var data-var='date'>24</var>, <var data-var='time'>18:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>30</var>, <var data-var='time'>22:17</var> PDT Scheduled - On Tuesday, Aug 25th from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI 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.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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@treasure.ai.

[Korea Region] Database Maintenance

Jul <var data-var='date'>27</var>, <var data-var='time'>01:29</var> PDT Resolved - Between 7/25 and today, 7/27 at 11:30 AM JST, we experienced a performance degradation issue affecting BulkLoad (Data Connector Import), Result Export (Activation) and Bulk Import. Following reports received this morning, our engineering team investigated the issue and identified high system load under specific conditions (increasing delay in internal components communication) as the root cause. The issue has been resolved by full rotation of our server nodes, and full performance was restored as of 11:30 AM JST. We sincerely apologize for any inconvenience caused. We are currently reviewing our monitoring and alerting rules to prevent similar issues in the future.

[Tokyo, Ap03 and US Regions] Performance degradation with Bulk Load, Bulk Import and Result Export jobs

Jul <var data-var='date'> 7</var>, <var data-var='time'>13:59</var> PDT Resolved - This issue has been resolved. Treasure Work and tdx are operating normally, and the Claude Haiku 4.5 model in the Tokyo region is no longer experiencing errors or timeouts. Thank you for your patience. Jul <var data-var='date'> 7</var>, <var data-var='time'>13:27</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 7</var>, <var data-var='time'>12:42</var> PDT Update - We are continuing to work through a potential fix and working to identify any potential contributing factors. Again, as the issue is localized to Haiku 4.5 models in the Tokyo region, we recommend users temporarily use a different model if they are experiencing any elevated error rates. We apologize for the inconvenience and will have another update soon. Jul <var data-var='date'> 7</var>, <var data-var='time'>11:07</var> PDT Identified - We are continuing to explore this issue and are currently evaluating a potential fix. We will update as soon as our testing is complete. Jul <var data-var='date'> 7</var>, <var data-var='time'>10:40</var> PDT Update - We are continuing to investigate this issue and will provide another update in 30 minutes. Jul <var data-var='date'> 7</var>, <var data-var='time'>10:04</var> PDT Investigating - We are observing degraded performance in Treasure Work and tdx in the Tokyo region. This issue is limited to the Claude Haiku 4.5 model in the Tokyo region only. Users may notice that requests using Claude Haiku 4.5 return errors or time out. At this time, we do not see any issues with other models. As a workaround, users can select a different model. We are actively investigating this issue and will aim to provide an update in 30 minutes.

[Tokyo Region] - Treasure Work / tdx claude - Degraded Performance

Jun <var data-var='date'>26</var>, <var data-var='time'>18:13</var> PDT Resolved - Hive query performance degradation in the US region has been resolved. We have successfully provisioned a new cluster and routed all traffic to it. Systems are now operating normally. Thank you for your patience. Jun <var data-var='date'>26</var>, <var data-var='time'>16:57</var> PDT Monitoring - We have provisioned a new cluster with sufficient capacity and are now routing jobs to it. Query performance is expected to recover gradually as the cluster stabilizes. We are monitoring the situation closely. We will provide an update in 1 hour. Jun <var data-var='date'>26</var>, <var data-var='time'>15:57</var> PDT Update - We are continuing to work on a fix. Our team is validating a cluster configuration change prior to applying it to the production environment. We will provide an update in 30 minutes. Jun <var data-var='date'>26</var>, <var data-var='time'>15:22</var> PDT Update - We are experiencing Hive query performance degradation in the US region. This issue began on June 25, 2026. Users may observe longer than expected query execution times, particularly for long-running jobs with large data volumes. We have identified the cause. To address this, we are validating a cluster configuration change prior to applying it to the production environment. We will provide an update in 30 minutes. Jun <var data-var='date'>26</var>, <var data-var='time'>14:48</var> PDT Identified - We are experiencing Hive query performance degradation in the US region. This issue began on June 25, 2026. Users may observe longer than expected query execution times, particularly for long-running jobs with large data volumes. We have identified the cause and are working on a fix. We will provide an update in 30 minutes.

[US Region] - Hive - Query Performance Degradation

Jun <var data-var='date'>25</var>, <var data-var='time'>04:46</var> PDT Resolved - Resolved — Some result export (data export) jobs in the US, Tokyo, and EU regions may have failed or been delayed between June 24, 2026 21:00 UTC and June 25, 2026 05:26 UTC. During this period, underlying compute nodes were intermittently unstable, which could cause export jobs to terminate before completing. In some cases an affected job may have ended without a clear error message.The issue has been resolved and all systems are operating normally. Data integrity is not impacted — source data in Treasure Data was unaffected; only the delivery of export jobs to external destinations during this window could have been disrupted.If you ran a result/data export during this window, we recommend confirming it completed and re-running it if the output looks incomplete. We will also contact affected customers directly. Thank you for your patience.

[US Region][Tokyo Region][EU Region] - Result/Data Export Job Failures

Jun <var data-var='date'>24</var>, <var data-var='time'>04:11</var> PDT Resolved - We identified a delay in recording email event data (such as open, click, bounce, delivery events, and error events) to customer event tables. Affected period (approximate): - June 22, 03:45 UTC – June 23, 04:15 UTC - June 23, 07:00 UTC – June 24, 07:30 UTC During these periods, email event data recording was delayed. Email delivery itself was not affected — emails were sent and received normally. The issue has been resolved and all systems are operating normally. Delayed events have been fully processed. If you ran queries on event or error_event tables during the affected periods, we suggest rerunning those queries to get accurate results. We apologize for any inconvenience.

[US Region] - Delay in Email Event Data Recording

May <var data-var='date'> 5</var>, <var data-var='time'>10:43</var> PDT Resolved - We have applied the fix, and are observing that traffic is flowing correctly now. May <var data-var='date'> 5</var>, <var data-var='time'>09:23</var> PDT Update - We are continuing to work on a fix for this issue. May <var data-var='date'> 5</var>, <var data-var='time'>09:20</var> PDT Identified - Incident: Real-time Profile Deletion Workflow Failures Status: Identified Impacted Regions: EU01, US01, Tokyo, AP03 (USA) Update (May 5, 2026 - 11:19 AM CDT) We have identified the root cause of the failures affecting Real-time (RT) bulk profile deletion, load, and stitch workflows in the affected regions. Summary of the Issue: A backend configuration issue resulted in a loss of necessary permissions for the service responsible for processing Real-time bulk profile operations. As a result, impacted workflows are failing with an "Authorization" or "400" error when attempting to invoke internal functions. Current Status: Our engineering team has developed a fix and is currently in the process of deploying it to all affected regions. We expect service to be restored shortly after the deployment is completed. We will provide a further update once the fix has been fully deployed and we have confirmed that workflow processing has returned to normal.

Realtime 2.0 Bulk Storage Outage

Apr <var data-var='date'>27</var>, <var data-var='time'>11:25</var> PDT Resolved - The upstream provider has restored service. Apr <var data-var='date'>27</var>, <var data-var='time'>10:31</var> PDT Monitoring - 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 persisting incoming data to our streaming infrastructure 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 support@treasure-data.com.

Intermittent 5xx Errors for Ingest and Real-Time APIs (EU01)

Apr <var data-var='date'>14</var>, <var data-var='time'>18:35</var> PDT Completed - The database maintenance has been completed. All systems are operating normally. Apr <var data-var='date'>14</var>, <var data-var='time'>18:05</var> PDT Verifying - The database update operation has been completed, and the results are currently being verified. Apr <var data-var='date'>14</var>, <var data-var='time'>18:00</var> PDT Update - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>14</var>, <var data-var='time'>17:01</var> 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 <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.

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.

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.

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.

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.

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

Is Treasure Data down?

Treasure Data status is DEGRADED

Components with issues

Lastest published events

[All Regions] Engage Studio (Email): Planned maintenance for the Email Delivery Events Table

[EU01 Tokyo AP03 Regions] Batch Data Load failure for RT2.0

[US Region] Batch Data Load failure for RT2.0

Treasure Data Services, Components and Regions

Recent Treasure Data events

[All Regions] Engage Studio (Email): Planned maintenance for the Email Delivery Events Table

[EU01 Tokyo AP03 Regions] Batch Data Load failure for RT2.0

[US Region] Batch Data Load failure for RT2.0

[All Regions] Live Chat Service Unavailable

[All Regions] Transactional email delivery delays

[AP03 Region] Database Maintenance