Treasure Data Outage History

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

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.

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.

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.

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.

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.

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.

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.