Treasure Data Outage History

Started Oct 22, 2026, 03:24 AM UTC· resolved Oct 22, 2026, 10:15 AM UTC

1. identified Oct 22, 2026, 03:24 AM UTC

   Since October 13, 2026 02:00 UTC, some import jobs that read Parquet files from Amazon S3 complete successfully but load date and time columns as text (string) instead of numbers (long). If the destination table already defines these columns as long, the imported values are empty (NULL). Only columns stored with a date or time type in the Parquet file are affected. Other columns and other data connectors are not affected. We have identified the cause, a change introduced in the October 13 release, and are preparing a fix. We are assessing the full scope of impact. We will provide an update in 30 minutes.

2. identified Oct 22, 2026, 04:06 AM UTC

   We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are implementing a fix. Until the fix is deployed, affected import jobs continue to complete successfully with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period. We will provide an update in 1 hour.

3. identified Oct 22, 2026, 06:22 AM UTC

   We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are deploying a fix. Until the fix is deployed, affected import jobs continue to complete with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period. We will provide an update in 30 minutes.

4. monitoring Oct 22, 2026, 07:44 AM UTC

   We have deployed a fix for Amazon S3 Parquet imports loading date and time columns as text. New import jobs load these columns as numbers (long), as before October 13, 2026. We are monitoring to ensure stability. We will provide an update in 30 minutes.

5. resolved Oct 22, 2026, 10:15 AM UTC

   The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026. Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Oct 07, 2026, 04:21 AM UTC· resolved Oct 07, 2026, 05:24 AM UTC

1. identified Oct 07, 2026, 04:21 AM UTC

   Since approximately 22:55 UTC on October 6, users of the Treasure AI Voice mobile app may be unable to transfer new recordings from their device. The transfer fails with an "Unauthorized" error. This affects both Wi-Fi and Bluetooth transfers. We have identified the cause and are deploying a fix. Recordings that were already transferred, and their transcripts and summaries, are not affected. We will provide an update in 30 minutes.

2. identified Oct 07, 2026, 04:27 AM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Oct 07, 2026, 04:54 AM UTC

   We have deployed a server-side fix for the recording transfer failures in Treasure AI Voice. New transfers from the mobile app are succeeding again. No app update is required. Recordings that failed to transfer during the incident can be transferred again from the device. We are monitoring to ensure stability.

4. resolved Oct 07, 2026, 05:24 AM UTC

   The recording transfer failures in Treasure AI Voice have been resolved. All systems are operating normally. Between approximately 22:55 UTC on October 6 and [fix time] UTC on October 7, new recordings could not be transferred from the mobile app. We deployed a server-side fix, and no app update is required. Recordings that failed to transfer during this period can be transferred again from the device. Thank you for your patience.

Read the full incident report →

Started Sep 30, 2026, 04:36 AM UTC· resolved Sep 30, 2026, 06:30 PM UTC

1. resolved Sep 30, 2026, 04:36 AM UTC

   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.

Read the full incident report →

Started Sep 29, 2026, 05:22 PM UTC· resolved Sep 29, 2026, 09:18 PM UTC

1. investigating Sep 29, 2026, 05:22 PM UTC

   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.

2. monitoring Sep 29, 2026, 06:20 PM UTC

   A fix has been implemented and we have observed that jobs are succeeding.

3. resolved Sep 29, 2026, 09:18 PM UTC

   This incident has been resolved, and our support team will be following up with affected customers.

Read the full incident report →

Started Sep 28, 2026, 03:41 AM UTC· resolved Sep 28, 2026, 01:16 PM UTC

1. investigating Sep 28, 2026, 03:41 AM UTC

   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 [email protected]. We appreciate your patience and apologize for any inconvenience.

2. resolved Sep 28, 2026, 01:16 PM UTC

   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.

Read the full incident report →

Started Sep 17, 2026, 03:14 AM UTC· resolved Oct 16, 2026, 12:04 AM UTC

1. identified Sep 17, 2026, 03:14 AM UTC

   We have identified the cause of delays affecting transactional emails from our web interface and are working on a solution. Customers may 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.

2. monitoring Sep 17, 2026, 03:44 AM UTC

   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.

3. monitoring Sep 17, 2026, 06:10 AM UTC

   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.

4. monitoring Sep 18, 2026, 06:51 AM UTC

   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.

5. monitoring Sep 25, 2026, 04:44 AM UTC

   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.

6. monitoring Oct 05, 2026, 02:19 AM UTC

   We are continuing to monitor for any further issues.

7. monitoring Oct 05, 2026, 02:20 AM UTC

   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.

8. resolved Oct 16, 2026, 12:04 AM UTC

   We are no longer observing any delivery delays. We have enhanced our monitoring and will continue to watch for disruptions. If you notice any sluggish delivery, please contact our support team for assistance.

Read the full incident report →

Started Jul 27, 2026, 08:29 AM UTC· resolved Jul 27, 2026, 08:29 AM UTC

1. resolved Jul 27, 2026, 08:29 AM UTC

   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.

Read the full incident report →

Started Jul 07, 2026, 05:04 PM UTC· resolved Jul 07, 2026, 08:59 PM UTC

1. investigating Jul 07, 2026, 05:04 PM UTC

   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.

2. investigating Jul 07, 2026, 05:40 PM UTC

   We are continuing to investigate this issue and will provide another update in 30 minutes.

3. identified Jul 07, 2026, 06:07 PM UTC

   We are continuing to explore this issue and are currently evaluating a potential fix. We will update as soon as our testing is complete.

4. identified Jul 07, 2026, 07:42 PM UTC

   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.

5. monitoring Jul 07, 2026, 08:27 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Jul 07, 2026, 08:59 PM UTC

   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.

Read the full incident report →

Started Jun 26, 2026, 09:48 PM UTC· resolved Jun 27, 2026, 01:13 AM UTC

1. identified Jun 26, 2026, 09:48 PM UTC

   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.

2. identified Jun 26, 2026, 10:22 PM UTC

   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.

3. identified Jun 26, 2026, 10:57 PM UTC

   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.

4. monitoring Jun 26, 2026, 11:57 PM UTC

   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.

5. resolved Jun 27, 2026, 01:13 AM UTC

   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.

Read the full incident report →

Started Jun 25, 2026, 11:46 AM UTC· resolved Jun 26, 2026, 05:26 AM UTC

1. resolved Jun 25, 2026, 11:46 AM UTC

   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.

Read the full incident report →

Started Jun 24, 2026, 03:45 AM UTC· resolved Jun 24, 2026, 07:30 AM UTC

1. resolved Jun 24, 2026, 11:11 AM UTC

   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.

Read the full incident report →

Started May 05, 2026, 04:20 PM UTC· resolved May 05, 2026, 05:43 PM UTC

1. identified May 05, 2026, 04:20 PM UTC

   Incident: Real-time Profile Deletion Workflow Failures Status: Identified Impacted Regions: EU01 (Ireland), US01 (USA) Update (May 5, 2026 - 11:19 AM CDT) We have identified the root cause of the failures affecting Real-time (RT) profile deletion workflows in the EU01 and US01 regions. Summary of the Issue: A backend configuration issue resulted in a loss of necessary permissions for the service responsible for processing Real-time profile deletions. 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. Customer Impact: EU01: Extensive impact; workflows involving bulk-delete endpoints are currently failing. US01: Some accounts are experiencing failures; others may remain unaffected. JP01: This region is not affected. We will provide a further update once the fix has been fully deployed and we have confirmed that workflow processing has returned to normal.

2. identified May 05, 2026, 04:23 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved May 05, 2026, 05:43 PM UTC

   We have applied the fix, and are observing that traffic is flowing correctly now.

Read the full incident report →

Started Apr 27, 2026, 05:31 PM UTC· resolved Apr 27, 2026, 06:25 PM UTC

1. monitoring Apr 27, 2026, 05:31 PM UTC

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

2. resolved Apr 27, 2026, 06:25 PM UTC

   The upstream provider has restored service.

Read the full incident report →

Started Apr 15, 2026, 01:35 AM UTC· resolved Apr 15, 2026, 01:35 AM UTC

1. monitoring Apr 15, 2026, 01:35 AM UTC

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

Read the full incident report →

Started Mar 04, 2026, 01:54 AM UTC· resolved Mar 04, 2026, 01:54 AM UTC

1. monitoring Mar 04, 2026, 01:54 AM UTC

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

Read the full incident report →

Started Mar 03, 2026, 02:50 AM UTC· resolved Mar 03, 2026, 02:50 AM UTC

1. monitoring Mar 03, 2026, 02:50 AM UTC

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

Read the full incident report →

Started Feb 26, 2026, 02:52 AM UTC· resolved Feb 26, 2026, 02:52 AM UTC

1. monitoring Feb 26, 2026, 02:52 AM UTC

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

Read the full incident report →

Started Feb 25, 2026, 02:55 AM UTC· resolved Feb 25, 2026, 02:55 AM UTC

1. monitoring Feb 25, 2026, 02:55 AM UTC

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

Read the full incident report →

Started Feb 24, 2026, 02:19 AM UTC· resolved Feb 24, 2026, 02:19 AM UTC

1. monitoring Feb 24, 2026, 02:19 AM UTC

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

Read the full incident report →

Started Feb 18, 2026, 10:00 PM UTC· resolved Feb 18, 2026, 10:00 PM UTC

1. monitoring Feb 18, 2026, 10:00 PM UTC

   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.

Read the full incident report →

Started Jan 21, 2026, 05:07 AM UTC· resolved Jan 21, 2026, 05:07 AM UTC

1. monitoring Jan 21, 2026, 05:07 AM UTC

   Jan 20, 21:07 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 20, 20:41 PST Monitoring - The system in the US region is operating normally with no observed issues. In the Tokyo region, table metadata updates have also been resumed. At this point, the Tokyo region is expected to be fully recovered, and we will continue to monitor system performance. Once stability is fully confirmed, we plan to close this status page. Jan 20, 20:12 PST Update - In the US region, table metadata updates have been resumed. At this point, the system in the US region is expected to be fully recovered, and we are continuing to monitor it closely. For the Tokyo region, metadata updates will be resumed after we complete confirmation of system performance. We will provide another update when this step begins. Jan 20, 20:06 PST Update - Performance in the Tokyo region improved at approximately 12:50 JST. The Tokyo region had been experiencing gradually increasing performance degradation since around 09:00 JST. We are currently proceeding with the steps to resume updates of table metadata in Data Workbench. Due to the temporary pause of metadata updates, application metrics that rely on this information, such as Parent Segment size, have also been temporarily not updated. We will continue monitoring the system and share further updates as needed. Jan 20, 19:40 PST Update - We are continuing to work on a fix for this issue. Jan 20, 19:37 PST Identified - We identified the same issue in the Tokyo region and applied database parameter tuning. We are currently assessing the impact of this change on system performance. As a result of this temporary mitigation applied in both the US and Tokyo regions, the following impact is observed: In Data Workbench, updates to table metadata for row counts and preview data are temporarily paused. We will continue monitoring and provide further updates as we make progress. Jan 20, 18:55 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

Read the full incident report →

Started Jan 05, 2026, 02:11 PM UTC· resolved Jan 05, 2026, 02:11 PM UTC

1. monitoring Jan 05, 2026, 02:11 PM UTC

   Jan 5, 06:11 PST Completed - The scheduled maintenance has been completed. Jan 5, 06:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 26, 13:41 PST Scheduled - Realtime Database Maintenance Upcoming scheduled maintenance notice on January 5th, 2026 from 14:00 to 15:00 UTC - the backend databases supporting Realtime 2.0 on Treasure Data system will undergo a short maintenance window. Expected downtime is less than 10 minutes. During the maintenance window, the databases supporting Realtime 2.0 service on Treasure Data Platform will undergo a PostgreSQL version upgrade. During this time customers attempting to launch journeys or personalizations will experience errors or lost Realtime journey or personalization updates. Beyond this notice, we will provide updates approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is completed. At that time, all systems will have returned to full functionality and the Scheduled Maintenance will be closed. If you have any question or concern about this maintenance, please feel free to reach out to our Support team at [email protected].

Read the full incident report →

Started Dec 10, 2025, 06:03 AM UTC· resolved Dec 10, 2025, 06:03 AM UTC

1. resolved Dec 10, 2025, 06:03 AM UTC

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

Read the full incident report →

Started Dec 05, 2025, 09:30 AM UTC· resolved Dec 05, 2025, 09:30 AM UTC

1. monitoring Dec 05, 2025, 09:30 AM UTC

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

Read the full incident report →

Started Dec 03, 2025, 08:10 AM UTC· resolved Dec 03, 2025, 08:10 AM UTC

1. monitoring Dec 03, 2025, 08:10 AM UTC

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

Read the full incident report →