Last checked
Leading Enterprise Customer Data Platform.
Experiencing an issue?
Treasure Data est-il en panne?
Status unavailable
The current official status of Treasure Data cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Treasure Data in the last 24 hours. Last official check: .
Share your experience to help others stay informed.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
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 surveille Treasure Data via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.
Cette page comprend actuellement 107 composants surveillés, 61 incidents, 61 maintenances et 15 jours d'historique connu.
Uptimus est un service indépendant sans affiliation avec Treasure Data. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.
Recevez une alerte lorsque Treasure Data ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 61 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « [US Region][Tokyo Region][EU Region][AP03 Region] Data Connector Integrations - Date columns from S3 Parquet imports loaded as text ».
Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 107 composants Treasure Data: Web Interface, Web Interface, Web Interface, Web Interface. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
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 20 nov. 2026, 01:00 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 1 oct. 2026, 04:00 UTC · Resolved 1 oct. 2026, 07:29 UTC
The database maintenance has been completed. All systems are operating normally.
Started 3 sept. 2026, 01:00 UTC · Resolved 3 sept. 2026, 01:24 UTC
The database maintenance has been completed. All systems are operating normally.
Started 2 sept. 2026, 01:00 UTC · Resolved 2 sept. 2026, 01:31 UTC
Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.
| Critères de comparaison | Uptimus | Downdetector |
|---|---|---|
| Signalements communautaires concernant Treasure Data | Inclus | Inclus |
| Référence adaptative distinguant les cas isolés d’une panne étendue | Inclus | Inclus |
| Activité des signalements sur 24 heures et vue régionale | Inclus | Inclus |
| Un espace pour les sites, pages de statut, jeux Steam et apps et jeux Android | Inclus | Produit séparé |
| Alertes e-mail, push et webhook depuis le même espace | Inclus | Produit séparé |
| Mises à jour officielles et chronologie du statut de Treasure Data | Inclus | Piloté par les signalements |
| État des composants et maintenances affichés séparément | Inclus | Limité sur les pages publiques |
Partagez vos réflexions sur Treasure Data
Soyez le premier à commenter!
Started 19 nov. 2026, 01:00 UTC · Ongoing
Started 18 nov. 2026, 01:00 UTC · Ongoing
Started 17 nov. 2026, 01:00 UTC · Ongoing
Started 16 nov. 2026, 01:00 UTC · Ongoing
Évaluez ce service
Aucun avis pour le moment
Découvrez d'autres services populaires et leur état actuel
