New Multi-region uptime checks and custom-domain status pages

Treasure Data Outage History

Daily provider-status observations and published incident history for Treasure Data.

Operational

Treasure Data is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Treasure Data for future changes.

68.4% of 79 verified observed days had no reported provider issue

90-Day Trend

Aug 18Nov 15

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
October 2026 58.1% 31 13
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)

Aug 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
[US Region][Tokyo Region][EU Region][AP03 Region] Data Connector Integrations - Date columns from S3 Parquet imports loaded as text
major Observed active window 6h 50m

View incident details and source

Started:

Data Connector Integrations Data Connector Integrations Data Connector Integrations Data Connector Integrations
monitoring
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.
identified
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.
identified
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.
identified
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.
[Tokyo Region] Treasure AI Voice - Recordings fail to transfer from the mobile app
major Observed active window 1h 4m

View incident details and source

Started:

Treasure AI Voice
monitoring
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.
identified
We are continuing to work on a fix for this issue.
identified
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.
September 2026
Batch Data Load failure for RT2.0
minor Observed active window 3h 57m

View incident details and source

Started:

Realtime 2.0
monitoring
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.
[All Regions] Live Chat Service Unavailable
major Observed active window 9h 38m

View incident details and source

Started:

Web Interface Web Interface Web Interface Web Interface Web 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.
[All Regions] Transactional email delivery delays
major Observed active window 692h 50m

View incident details and source

Started:

Web Interface Web Interface Web Interface Web Interface Web 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 14 days, or sooner if conditions change.
monitoring
We are continuing to monitor for any further issues.
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
minor Source 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.
June 2026
[US Region] - Hive - Query Performance Degradation
minor Source not attested
Last archived state: resolved
View archived record details
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.
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
minor Source 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)
minor Source 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...
Get alerts for Treasure Data Subscribe to the provider incident feed Browse all services