Last checked
Leading Enterprise Customer Data Platform.
Experiencing an issue?
Is Treasure Data down?
Maintenance
Share your experience to help others stay informed.
Official status checked
Treasure Data has active maintenance
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 6h 51m | Yes | Major | ||
| 1h 4m | Yes | Major | ||
| 0m | Yes | Minor | ||
| 3h 57m | Yes | Minor | ||
| 9h 35m | Yes | Major | ||
| 692h 49m | Yes | Major | ||
| 0m | Yes | Unknown | ||
| 3h 55m | Yes | Minor |
Uptimus monitors Treasure Data through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 107 monitored components, 61 indexed incidents, 61 maintenance windows and 15 days of known history.
Uptimus is an independent monitoring service and is not affiliated with Treasure Data. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when Treasure Data or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 61 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “[US Region][Tokyo Region][EU Region][AP03 Region] Data Connector Integrations - Date columns from S3 Parquet imports loaded as text”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 107 Treasure Data components: Web Interface, Web Interface, Web Interface, Web Interface. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Planned work published by the official provider.
On Friday, November 20 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability while we restart services, typically a few minutes. See below for information about the impact of this change to Treasure AI services. We will communicate with you via our status page (https://status.treasure.ai/ ) on the maintenance activities. If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support ). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Customers make experience the following: - Jobs execution delay All jobs (Presto Query Engine, Hadoop / Hive Query Engine, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at [email protected] to recover the jobs. To avoid data duplication in your systems from Treasure AI exports, Integration Export jobs won’t be automatically retried. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to recover gradually over 30 minutes. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - REST API The REST API endpoints to create tables, job submission, and job cancellation will be unavailable and will respond with a 500 error code. Components that use the REST API may also see performance degradation such as delays, authorisation failures, partial functionality, unavailability, and errors during the maintenance window. These components include “Web Interface”, “Mobile/Javascript REST API”, “Workflow”, “Workflow REST API”, “CDP API”, “Data Access API (beta)”, “ADL”, “Engage Studio REST APIs”, “Engage Studio Message Delivery”, “AI Agent Foundry, Foundry Workspace”, “Streaming Ingress / Egress connectors” Requests, workflows, and deliveries will be retried where safe to do so, and scheduled jobs will be processed after the maintenance period. - Data Connector Integrations connection settings During the maintenance, creating or updating Data Connector Integrations connections may fail. Please retry after the maintenance is complete. - AI Signals During the maintenance window, requests to the ML Batch API used by AI Signals may temporarily fail, and machine learning training or prediction runs may not be created or executed. Treasure Workflow tasks that invoke the ML Batch API will retry automatically, so no customer action is expected for workflow-based runs. Customers that call the ML Batch API directly may receive failed requests during the maintenance window and should follow their normal retry handling after maintenance is complete. - AI Studio During the maintenance window, Treasure AI Studio users may experience errors when accessing chats, managing projects, or updating settings. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact [email protected] to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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].
Started Nov 20, 2026, 01:00 AM UTC · Ongoing
On Thursday, November 19 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability while we restart services, typically a few minutes. See below for information about the impact of this change to Treasure AI services. We will communicate with you via our status page (https://status.treasure.ai/ ) on the maintenance activities. If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Customers make experience the following: - Jobs execution delay All jobs (Presto Query Engine, Hadoop / Hive Query Engine, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at [email protected] to recover the jobs. To avoid data duplication in your systems from Treasure AI exports, Integration Export jobs won’t be automatically retried. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to recover gradually over 30 minutes. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - REST API The REST API endpoints to create tables, job submission, and job cancellation will be unavailable and will respond with a 500 error code. Components that use the REST API may also see performance degradation such as delays, authorisation failures, partial functionality, unavailability, and errors during the maintenance window. These components include “Web Interface”, “Mobile/Javascript REST API”, “Workflow”, “Workflow REST API”, “CDP API”, “Data Access API (beta)”, “ADL”, “Engage Studio REST APIs”, “Engage Studio Message Delivery”, “AI Agent Foundry, Foundry Workspace”, “Streaming Ingress / Egress connectors” Requests, workflows, and deliveries will be retried where safe to do so, and scheduled jobs will be processed after the maintenance period. - Data Connector Integrations connection settings During the maintenance, creating or updating Data Connector Integrations connections may fail. Please retry after the maintenance is complete. - AI Signals During the maintenance window, requests to the ML Batch API used by AI Signals may temporarily fail, and machine learning training or prediction runs may not be created or executed. Treasure Workflow tasks that invoke the ML Batch API will retry automatically, so no customer action is expected for workflow-based runs. Customers that call the ML Batch API directly may receive failed requests during the maintenance window and should follow their normal retry handling after maintenance is complete. - AI Studio During the maintenance window, Treasure AI Studio users may experience errors when accessing chats, managing projects, or updating settings. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact [email protected] to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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].
On Wednesday, November 18 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability while we restart services, typically a few minutes. See below for information about the impact of this change to Treasure AI services. We will communicate with you via our status page (https://status.treasure.ai/ ) on the maintenance activities. If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support ). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Customers make experience the following: - Jobs execution delay All jobs (Presto Query Engine, Hadoop / Hive Query Engine, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at [email protected] to recover the jobs. To avoid data duplication in your systems from Treasure AI exports, Integration Export jobs won’t be automatically retried. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to recover gradually over 30 minutes. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - REST API The REST API endpoints to create tables, job submission, and job cancellation will be unavailable and will respond with a 500 error code. Components that use the REST API may also see performance degradation such as delays, authorisation failures, partial functionality, unavailability, and errors during the maintenance window. These components include “Web Interface”, “Mobile/Javascript REST API”, “Workflow”, “Workflow REST API”, “CDP API”, “Data Access API (beta)”, “ADL”, “Engage Studio REST APIs”, “Engage Studio Message Delivery”, “AI Agent Foundry, Foundry Workspace”, “Streaming Ingress / Egress connectors” Requests, workflows, and deliveries will be retried where safe to do so, and scheduled jobs will be processed after the maintenance period. Data Connector Integrations connection settings During the maintenance, creating or updating Data Connector Integrations connections may fail. Please retry after the maintenance is complete. - AI Signals During the maintenance window, requests to the ML Batch API used by AI Signals may temporarily fail, and machine learning training or prediction runs may not be created or executed. Treasure Workflow tasks that invoke the ML Batch API will retry automatically, so no customer action is expected for workflow-based runs. Customers that call the ML Batch API directly may receive failed requests during the maintenance window and should follow their normal retry handling after maintenance is complete. - AI Studio During the maintenance window, Treasure AI Studio users may experience errors when accessing chats, managing projects, or updating settings. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact [email protected] to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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].
On Tuesday, November 17 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability while we restart services, typically a few minutes. See below for information about the impact of this change to Treasure AI services. We will communicate with you via our status page (https://status.treasure.ai/ ) on the maintenance activities. If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Customers make experience the following: - Jobs execution delay All jobs (Presto Query Engine, Hadoop / Hive Query Engine, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at [email protected] to recover the jobs. To avoid data duplication in your systems from Treasure AI exports, Integration Export jobs won’t be automatically retried. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to recover gradually over 30 minutes. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - REST API The REST API endpoints to create tables, job submission, and job cancellation will be unavailable and will respond with a 500 error code. Components that use the REST API may also see performance degradation such as delays, authorisation failures, partial functionality, unavailability, and errors during the maintenance window. These components include “Web Interface”, “Mobile/Javascript REST API”, “Workflow”, “Workflow REST API”, “CDP API”, “Data Access API (beta)”, “ADL”, “Engage Studio REST APIs”, “Engage Studio Message Delivery”, “AI Agent Foundry, Foundry Workspace”, “Streaming Ingress / Egress connectors”. Requests, workflows, and deliveries will be retried where safe to do so, and scheduled jobs will be processed after the maintenance period. - Data Connector Integrations connection settings During the maintenance, creating or updating Data Connector Integrations connections may fail. Please retry after the maintenance is complete. - AI Signals During the maintenance window, requests to the ML Batch API used by AI Signals may temporarily fail, and machine learning training or prediction runs may not be created or executed. Treasure Workflow tasks that invoke the ML Batch API will retry automatically, so no customer action is expected for workflow-based runs. Customers that call the ML Batch API directly may receive failed requests during the maintenance window and should follow their normal retry handling after maintenance is complete. - AI Studio During the maintenance window, Treasure AI Studio users may experience errors when accessing chats, managing projects, or updating settings. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact [email protected] to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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].
On Monday, November 16 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability while we restart services, typically a few minutes. See below for information about the impact of this change to Treasure AI services. We will communicate with you on an ongoing basis via our status page (https://status.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Customers make experience the following: - Jobs execution delay All jobs (Presto Query Engine, Hadoop / Hive Query Engine, Data Connector Integrations, Bulk Import, Bulk Export, Result Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will be delayed and automatically retried until they succeed after the downtime period. We expect job processing to ramp up over 30 minutes after the maintenance is complete before returning to full throughput. If customers experience errors running Data Connector Integration Export jobs, please contact our Support team at [email protected] to recover the jobs. To avoid data duplication in your systems from Treasure AI exports, Integration Export jobs won’t be automatically retried. - Console execution delay Data Workbench and Audience Studio will show that jobs are running longer due to job execution delays. The Table preview (sample data and records counter) in Data Workbench may show old information while maintenance is underway. After maintenance is complete, we expect the processing of Data Workbench and Audience Studio jobs to recover gradually over 30 minutes. SQL or Workflow requests to create tables will be delayed and automatically retried after the maintenance period. - REST API The REST API endpoints to create tables, job submission, and job cancellation will be unavailable and will respond with a 500 error code. Components that use the REST API may also see performance degradation such as delays, authorisation failures, partial functionality, unavailability, and errors during the maintenance window. These components include “Web Interface”, “Mobile/Javascript REST API”, “Workflow”, “Workflow REST API”, “CDP API”, “Data Access API (beta)”, “ADL”, “Engage Studio REST APIs”, “Engage Studio Message Delivery”, “AI Agent Foundry, Foundry Workspace”, “Streaming Ingress / Egress connectors” Requests, workflows, and deliveries will be retried where safe to do so, and scheduled jobs will be processed after the maintenance period. - Data Connector Integrations connection settings During the maintenance, creating or updating Data Connector Integrations connections may fail. Please retry after the maintenance is complete. - AI Signals During the maintenance window, requests to the ML Batch API used by AI Signals may temporarily fail, and machine learning training or prediction runs may not be created or executed. Treasure Workflow tasks that invoke the ML Batch API will retry automatically, so no customer action is expected for workflow-based runs. Customers that call the ML Batch API directly may receive failed requests during the maintenance window and should follow their normal retry handling after maintenance is complete. - AI Studio During the maintenance window, Treasure AI Studio users may experience errors when accessing chats, managing projects, or updating settings. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact [email protected] to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) 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].
The maintenance and validations are completed. Email campaigns, sending and delivery were not affected, and all other channels remain operation.
Started Oct 1, 2026, 04:00 AM UTC · Resolved Oct 1, 2026, 07:29 AM UTC
The database maintenance has been completed. All systems are operating normally.
Started Sep 3, 2026, 01:00 AM UTC · Resolved Sep 3, 2026, 01:24 AM UTC
The database maintenance has been completed. All systems are operating normally.
Started Sep 2, 2026, 01:00 AM UTC · Resolved Sep 2, 2026, 01:31 AM UTC
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for Treasure Data | Included | Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
| 24-hour report activity and regional outage view | Included | Included |
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
| Email, push and webhook alerts from the same workspace | Included | Separate product |
| Official incident updates and status timeline for Treasure Data | Included | User-report led |
| Component health and maintenance windows kept separate | Included | Limited on public pages |
The official status page for Treasure Data reports normal operation. 0 reports were recorded for Treasure Data in the last 24 hours. Last official check: .
Started Nov 19, 2026, 01:00 AM UTC · Ongoing
Started Nov 18, 2026, 01:00 AM UTC · Ongoing
Started Nov 17, 2026, 01:00 AM UTC · Ongoing
Started Nov 16, 2026, 01:00 AM UTC · Ongoing
Discover other popular services and their current status
Rate this service
No reviews yet
Share your thoughts about Treasure Data
Be the first to comment!
