Is Treasure Data down?
Last checked 1m agoNo incidents right now.
Treasure Data is operational right now. Last checked 1m ago; the most recent incident resolved 39d ago.
Real-time Treasure Data status, recent outages, and incident history — pulled directly from Treasure Data's official status page at https://status.treasuredata.com every 5 minutes. Pingoru tracks 99 Treasure Data services and has captured 3 incidents in the last 90 days (99.93% uptime). Get email, Slack, Discord, or webhook alerts the moment Treasure Data reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Realtime 2.0Realtime 2.0Realtime 2.0
Timeline · 3 updates
- identified · May 05, 2026, 04:20 PM UTC
Incident: Real-time Profile Deletion Workflow Failures Status: Identified Impacted Regions: EU01 (Ireland), US01 (USA) Update (May 5, 2026 - 11:19 AM CDT) We have identified the root cause of the failures affecting Real-time (RT) profile deletion workflows in the EU01 and US01 regions. Summary of the Issue: A backend configuration issue resulted in a loss of necessary permissions for the service responsible for processing Real-time profile deletions. As a result, impacted workflows are failing with an "Authorization" or "400" error when attempting to invoke internal functions. Current Status: Our engineering team has developed a fix and is currently in the process of deploying it to all affected regions. We expect service to be restored shortly after the deployment is completed. Customer Impact: EU01: Extensive impact; workflows involving bulk-delete endpoints are currently failing. US01: Some accounts are experiencing failures; others may remain unaffected. JP01: This region is not affected. We will provide a further update once the fix has been fully deployed and we have confirmed that workflow processing has returned to normal.
- identified · May 05, 2026, 04:23 PM UTC
We are continuing to work on a fix for this issue.
- resolved · May 05, 2026, 05:43 PM UTC
We have applied the fix, and are observing that traffic is flowing correctly now.
Latest: We have applied the fix, and are observing that traffic is flowing correctly now.
-
- CDP Personalization - Ingest APIRealtime 2.0
Timeline · 2 updates
- monitoring · Apr 27, 2026, 05:31 PM UTC
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 from successfully processing incoming data streams and executing real-time lookups during the affected window. The upstream provider has confirmed the issue is resolved. Our engineering team monitored the recovery, and we have confirmed that all services in the EU01 region have returned to normal operating parameters. Data Integrity: For data ingestion, records that were rejected with a retryable error code during this window should be resubmitted. Records that have already been successfully ingested following the recovery require no further action. Personalization: Real-time request success rates have returned to 100%. We are continuing to monitor the stability of the region. We apologize for any inconvenience this may have caused to your operations. For further questions, please contact our support team at [email protected].
- resolved · Apr 27, 2026, 06:25 PM UTC
The upstream provider has restored service.
Latest: The upstream provider has restored service.
-
-
Timeline · 1 update
- monitoring · Apr 15, 2026, 01:35 AM UTC
Apr 14, 18:35 PDT Completed - The database maintenance has been completed. All systems are operating normally. Apr 14, 18:05 PDT Verifying - The database update operation has been completed, and the results are currently being verified. Apr 14, 18:00 PDT Update - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 14, 17:01 PDT Update - In about an hour, from 01:00 UTC, the maintenance window for the database maintenance will commence. During this maintenance, we will apply patches and updates to databases used by the CDP API. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. # Impact During the database downtime and recovery period, customers may experience the following: - The CDP API (api-cdp.eu01.treasuredata.com) will be unavailable The CDP API endpoints, that are mainly used for TD Console, will be unavailable during the maintenance and will respond with a 500 error code. And also CDP related features on TD Console will be unavailable. (NOTE: Profiles API and TD API won’t be affected by this maintenance.) - CDP related Workflow execution delay CDP-related Workflow will be delayed and will be automatically retried until they succeed after the downtime period. Beyond this notice, we will provide updates at the start and completion of the operation and once the verification of the new system is completed: at that time, all systems will have returned to full functionality and this Scheduled Maintenance will be closed. Mar 11, 19:53 PDT Scheduled - On Wednesday, Apr 15th, 2026 from 01:00 to 02:00 UTC, we will be performing maintenance on the CDP database. During this maintenance, we will apply patches and updates to databases used by the CDP API. These updates are necessary to ensure we have the latest security and performance improvements available. We expect downtime to be brief, lasting only a few minutes. The remaining time will be dedicated to verifying that the maintenance was completed successfully and that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. # Impact During the database downtime and recovery period, customers may experience the following: - The CDP API (api-cdp.eu01.treasuredata.com) will be unavailable The CDP API endpoints, that are mainly used for TD Console, will be unavailable during the maintenance and will respond with a 500 error code. And also CDP related features on TD Console will be unavailable. (NOTE: Profiles API and TD API won’t be affected by this maintenance.) - CDP related Workflow execution delay CDP-related Workflow will be delayed and will be automatically retried until they succeed after the downtime period. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasuredata.com/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at [email protected].
Latest: Apr 14, 18:35 PDT Completed - The database maintenance has been completed. All systems are operating normally. Apr 14, 18:05 PDT Verifying - The database update operation has been …
-
- Realtime 2.0 Bulk Storage Outage ResolvedStarted May 05, 2026, 04:20 PM UTC · Resolved May 05, 2026, 05:43 PM UTC · 1h 23m
- Started Apr 27, 2026, 05:31 PM UTC · Resolved Apr 27, 2026, 06:25 PM UTC · 53m
- Started Apr 15, 2026, 01:35 AM UTC · Resolved Apr 15, 2026, 01:35 AM UTC · —