Treasure Data Status

Resolved: 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.

Resolved: 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.

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.

Resolved: 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.

Resolved: 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.

Resolved: 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.