Treasure Data Outage History

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

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.

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

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

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.

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.

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.

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.

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.

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

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

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