Treasure Data Outage History

Treasure Data is up right now

Treasure Data had 50 outages in the last 2 years totaling 10h 15m of downtime — averaging 2.1 incidents per month.

There were 50 Treasure Data outages since June 20, 2024 totaling 10h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.treasuredata.com

Minor February 18, 2026

US region: Treasure Insights unavailable

Detected by Pingoru
Feb 18, 2026, 10:00 PM UTC
Resolved
Feb 18, 2026, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Feb 18, 2026, 10:00 PM UTC

    Feb 18, 14:00 PST Resolved - This incident has been resolved. Feb 18, 13:32 PST Monitoring - The performance went back to normal, and no errors are observed now. We will monitor at least for 15 minutes. Feb 18, 13:27 PST Identified - We have partially resolved the incident. We are continuously working to resolve the incident. Feb 18, 12:45 PST Investigating - We are investigating a possible problem currently affecting Treasure Insights. We will provide an update as soon as we know more.

Read the full incident report →

Notice December 10, 2025

[All Regions] REST API sometimes returns only partial job result

Detected by Pingoru
Dec 10, 2025, 06:03 AM UTC
Resolved
Dec 10, 2025, 06:03 AM UTC
Duration
—
Affected: REST APIREST APIREST APIREST APIREST API
Timeline · 1 update
  1. resolved Dec 10, 2025, 06:03 AM UTC

    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.

Read the full incident report →

Minor December 5, 2025

[All Region] Service Disruption on Treasure Insights

Detected by Pingoru
Dec 05, 2025, 09:30 AM UTC
Resolved
Dec 05, 2025, 09:30 AM UTC
Duration
—
Timeline · 1 update
  1. monitoring Dec 05, 2025, 09:30 AM UTC

    Dec 5, 01:30 PST Resolved - We confirmed the third-party service is now operational. The incident has been resolved. Dec 5, 01:22 PST Monitoring - The third-party service provider has implemented a fix. We are monitoring the results. Dec 5, 01:18 PST Investigating - We are currently experiencing issues accessing Treasure Insights. Our investigation has identified that this is caused by an outage with a third-party service provider utilized by Treasure Insights. We are monitoring the situation and working with the provider to resolve the issue. We will provide updates as soon as more information becomes available.

Read the full incident report →

Major September 30, 2025

[All Regions] AI Agent Foundry May Provide Incomplete Responses

Detected by Pingoru
Sep 30, 2025, 03:37 AM UTC
Resolved
Sep 30, 2025, 07:22 AM UTC
Duration
3h 45m
Affected: Web InterfaceWeb InterfaceWeb InterfaceWeb InterfaceWeb Interface
Timeline · 4 updates
  1. investigating Sep 30, 2025, 03:37 AM UTC

    We are currently investigating an issue where AI agents in the AI Agent Foundry may prematurely stop their response without providing a final conclusion, especially during their thinking process. This behavior does not generate an error message. Our initial findings show it is more likely to occur in agents handling long or extensive conversations, though we have not yet identified a specific threshold. Our engineering team is actively investigating the root cause. We will provide another update as soon as more information is available. We apologize for any inconvenience this may cause.

  2. identified Sep 30, 2025, 06:08 AM UTC

    We have an update on the root cause of the issue causing AI agents to provide incomplete responses. Our investigation has found that when an agent uses its tools, the user's original prompt was being sent multiple times to the underlying AI model. This duplication caused the model to incorrectly process the tool results, leading it to return an empty response instead of a complete answer. The hotfix we are preparing will correct this behavior by ensuring the user's prompt is sent only once for each task. This will allow the AI to properly process all tool results and generate a complete, final response. We are working to deploy this fix as quickly as possible and will provide another update once it is ready. Thank you for your continued patience.

  3. monitoring Sep 30, 2025, 06:53 AM UTC

    The hotfix for the incomplete agent responses has been deployed. This should prevent the duplicate prompt issue during tool use. We are now monitoring the platform to ensure everything is working as expected. We will resolve this incident once we've confirmed stability.

  4. resolved Sep 30, 2025, 07:22 AM UTC

    After a successful 30-minute monitoring period, we can confirm that our fix is working and the issue is now resolved. All AI agents are functioning as expected. Thank you for your patience.

Read the full incident report →

Notice September 26, 2025

Profile API Data Delays - Tokyo Region

Detected by Pingoru
Sep 26, 2025, 07:12 PM UTC
Resolved
Sep 26, 2025, 11:24 PM UTC
Duration
4h 12m
Affected: CDP Personalization - Lookup API
Timeline · 3 updates
  1. identified Sep 26, 2025, 07:12 PM UTC

    We are currently experiencing delays in our Profile API replication pipeline in the Tokyo region. This issue began at approximately 13:00 UTC and is affecting all customers in this region. Impact: - Profile API responses may return stale data (up to several hours behind) - Lookup functionality remains available but data may be inconsistent Our engineering team is actively working on recovery. We estimate normal service will be restored within 8-10 hours. We will continue to provide updates as we make progress toward resolution.

  2. monitoring Sep 26, 2025, 11:02 PM UTC

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

  3. resolved Sep 26, 2025, 11:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 24, 2025

[US Region] Partial Issue with Table API in Hive and Trino

Detected by Pingoru
Sep 24, 2025, 06:53 AM UTC
Resolved
Sep 24, 2025, 06:53 AM UTC
Duration
—
Affected: Hadoop / Hive Query EnginePresto Query Engine
Timeline · 1 update
  1. resolved Sep 24, 2025, 06:53 AM UTC

    We experienced a partial issue on September 24th, between 01:55 and 02:40 UTC, where some users may have encountered incorrect permission errors when accessing their tables and databases in Hive and Trino. The issue was caused by a high load on our table API, which temporarily struggled to retrieve correct permission data. All underlying data remained secure and unaffected. The API load has returned to normal, and all services are operating as expected. If you had any jobs that failed with a permission error during this period, please try running them again. We apologize for any confusion this may have caused.

Read the full incident report →