Looking for an update now? Check the current status, or follow Treasure Data for future changes.
63.6%of 33 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
57.1%
28
12
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and we have observed that jobs are succeeding.
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.
Web InterfaceWeb InterfaceWeb InterfaceWeb InterfaceWeb Interface
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.
Web InterfaceWeb InterfaceWeb InterfaceWeb InterfaceWeb Interface
monitoring
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.
monitoring
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.
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 24 hours.
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.
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.
Legacy Incident Archive
4 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
[Tokyo Region] - Treasure Work / tdx claude - Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
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.
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.
investigating
We are continuing to investigate this issue and will provide another update in 30 minutes.
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.
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.
identified
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.
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. 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.
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.
May 2026
Realtime 2.0 Bulk Storage Outage
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
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, ...
April 2026
Intermittent 5xx Errors for Ingest and Real-Time APIs (EU01)
minorSource not attested
Last archived state: resolved
View archived record details
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 fr...
