All Systems Operational
About This Site
This is Treasure AI's status page.
We believe that trust starts with full transparency.
US
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Realtime 2.0
Operational
Engage Studio - Campaign API
Operational
Engage Studio - Delivery API
Operational
Treasure Work / tdx
Operational
Tokyo
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Realtime 2.0
Operational
Engage Studio - Campaign API
Operational
Engage Studio - Delivery API
Operational
Treasure Work / tdx
Operational
Treasure AI Voice
Operational
EU
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Realtime 2.0
Operational
Engage Studio - Campaign API
Operational
Engage Studio - Delivery API
Operational
Treasure Work / tdx
Operational
Korea
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
Data Access API (beta)
Operational
Insights
Operational
ADL
Operational
Data Tank
Operational
Consent Configuration API
Operational
Engage Studio - Campaign API
Operational
Engage Studio - Delivery API
Operational
Treasure Work / tdx
Operational
AP03
Operational
Web Interface
Operational
REST API
Operational
Streaming Import REST API
Operational
Mobile/Javascript REST API
Operational
Data Connector Integrations
Operational
Hadoop / Hive Query Engine
Operational
Presto Query Engine
Operational
Presto JDBC/ODBC Gateway
Operational
Workflow
Operational
CDP API
Operational
CDP Personalization - Lookup API
Operational
CDP Personalization - Ingest API
Operational
ADL
Operational
Engage Studio - Campaign API
Operational
Engage Studio - Delivery API
Operational
Treasure Work / tdx
Operational
Data Tank
Operational
Realtime 2.0
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
[Korea Region] Database Maintenance Nov 15, 2026 17:00-19:00 PST
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 10:25 PDT
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 10:25 PDT
[US Region] Database Maintenance Nov 16, 2026 17:00-19:00 PST
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 12:43 PDT
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 12:43 PDT
[Tokyo Region] Database Maintenance Nov 17, 2026 17:00-19:00 PST
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 12:53 PDT
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 12:53 PDT
[AP03 Region] Database Maintenance Nov 18, 2026 17:00-19:00 PST
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 15:44 PDT
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 15:44 PDT
[EU Region] Database Maintenance Nov 19, 2026 17:00-19:00 PST
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 15:50 PDT
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 support@treasure.ai 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 support@treasure.ai 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 support@treasure.ai.
Posted on Oct 15, 2026 - 15:50 PDT