All Systems Operational

About This Site

This is Arm Treasure Data's status page.
We believe that trust starts with full transparency.

US Operational
90 days ago
99.99 % uptime
Today
Web Interface   Operational
90 days ago
100.0 % uptime
Today
REST API   Operational
90 days ago
100.0 % uptime
Today
Streaming Import REST API   Operational
90 days ago
100.0 % uptime
Today
Mobile/Javascript REST API   Operational
90 days ago
100.0 % uptime
Today
Data Connector Integrations   Operational
90 days ago
100.0 % uptime
Today
Hadoop / Hive Query Engine   Operational
90 days ago
99.99 % uptime
Today
Presto Query Engine   Operational
90 days ago
100.0 % uptime
Today
Presto JDBC/ODBC Gateway   Operational
90 days ago
100.0 % uptime
Today
Workflow   ? Operational
90 days ago
100.0 % uptime
Today
Tokyo Operational
90 days ago
100.0 % uptime
Today
Web Interface   Operational
90 days ago
100.0 % uptime
Today
REST API   Operational
90 days ago
100.0 % uptime
Today
Streaming Import REST API   Operational
90 days ago
100.0 % uptime
Today
Mobile/Javascript REST API   Operational
90 days ago
100.0 % uptime
Today
Data Connector Integrations   Operational
90 days ago
100.0 % uptime
Today
Hadoop / Hive Query Engine   Operational
90 days ago
100.0 % uptime
Today
Presto Engine Query Engine   Operational
90 days ago
100.0 % uptime
Today
Presto JDBC/ODBC Gateway   Operational
90 days ago
100.0 % uptime
Today
Workflow   ? Operational
90 days ago
100.0 % uptime
Today
Global Operational
90 days ago
100.0 % uptime
Today
Reporting   ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
SCHEDULE UPDATE
This maintenance has been postponed by a week from Monday, Dec 10th to Monday, Dec 17th PST (Tuesday, December 18th at 10:00 AM JST).

NOTE
This maintenance notice interests customers of both the Arm Treasure Data US and Tokyo regions sending events through the Javascript and Mobile (Android, iOS, and Unity) SDKs.

After the December 3rd upgrade of the Mobile/Javascript Event Collection Backend, the previous Event Collection Backend was kept operational although not actively servicing traffic.

On Monday, December 17th at 5:00 PM PST (Tuesday, December 18th at 10:00 AM JST) the old Event Collection Backend will be brought offline: at that time, Mobile devices and Browsers still caching the old in.treasuredata.com and tokyo.in.treasuredata.com domains definitions pointing to the old Event Collection Backend could experience request failure and drop in events. Following this isolated failure, the Mobile devices and Browsers will be expected to automatically re-acquire the DNS definitions for in.treasuredata.com or tokyo.in.treasuredata.com and begin sending events to the new Event Collection Backend.
Posted on Dec 10, 21:57 PST
US - REST API - Response Time ?
Fetching
US - REST API - Error Rates ?
Fetching
US - Streaming Import REST API - Response Time ?
Fetching
US - Queued Streaming Import requests ?
Fetching
US - Mobile/Javascript REST API - Response Time ?
Fetching
US - Web Interface - Response Time ?
Fetching
Tokyo - REST API - Response Time ?
Fetching
Tokyo - Streaming Import REST API - Response Time ?
Fetching
Tokyo - Queued Streaming Import requests ?
Fetching
Tokyo - Web Interface - Response Time ?
Fetching
Past Incidents
Dec 13, 2018

No incidents reported today.

Dec 12, 2018
Resolved - Between 00:54 UTC and 01:03 UTC we experienced degraded console and API performance in the US Region site. Both services have recovered automatically.
Dec 12, 18:53 PST
Identified - Between 00:54 UTC and 01:03 UTC we experienced degraded console and API performance in the US Region site. Both services have recovered automatically and we are continuing to investigate and monitor.
Dec 12, 17:23 PST
Investigating - We are currently investigating console and API performance issues.
Dec 12, 17:10 PST
Resolved - The REST API is operating normally after 10:40 am PT. The incident was resolved.
Dec 12, 12:28 PST
Monitoring - From 10:30 am to 10:40 am PT, our REST API endpoint experienced degraded API performance. We already provisioned additional processing resource and now the API is working normally. We will continue to monitor the status of API.
Dec 12, 11:18 PST
Dec 11, 2018

No incidents reported.

Dec 10, 2018

No incidents reported.

Dec 9, 2018

No incidents reported.

Dec 8, 2018

No incidents reported.

Dec 7, 2018
Resolved - Workflows are correctly run. Audiences are fixed to work.
Dec 7, 21:39 PST
Monitoring - At 2006 UTC failing queries in audience workflows works fine. Workflows run after that will successfully update the audience.
Dec 7, 14:44 PST
Identified - At 0958 UTC Customer Data Platform Audience Workflows began returning errors for some customer workflows after a regular release. At approximately 0030 UTC the reversion of the release began and is in progress. For customers requiring urgent update to audience workflows, please contact support for an immediate recovery option.
Dec 6, 18:46 PST
Dec 6, 2018
Resolved - Cluster migration has been completed and performance has returned to normal
Dec 6, 00:04 PST
Identified - At approximately 0125 UTC / 1025 JST we began experiencing presto query performance degradation. Cluster scaling in response to the increased workload began at 1049 JST. We are migrating cluster workloads to standby clusters and expect to resume normal query performance shortly
Dec 5, 22:00 PST
Resolved - Cluster migration has been completed and performance has returned to normal
Dec 6, 00:04 PST
Identified - At approximately 0125 UTC / 1025 JST we began experiencing presto query performance degradation. Cluster scaling in response to the increased workload began at 1125 JST. We are migrating cluster workloads to standby clusters and expect to resume normal query performance shortly
Dec 5, 21:59 PST
Dec 5, 2018
Resolved - From approximately 1100 JST / 0200 UTC until 1159 JST / 0259 UTC the CDP console was degraded and mostly unavailable.

The CDP console relies upon our Presto query engine, which experienced above normal workloads during this period. At 0218 UTC the presto team identified the source of the increased presto workload, and began scaling out and shedding load. At 0236 UTC the CDP team began scaling out the API backend to mitigate longer response times.

During the incident response we neglected to update our status page, and are doing so now in arrears.
Dec 5, 21:54 PST
Dec 4, 2018

No incidents reported.

Dec 3, 2018
Completed - The scheduled maintenance for December 3rd starting at 5:00 PM PST (December 4th starting at 10:00 AM JST) has been completed.

The new Event Collection Backends will be operational and will be serving traffic in parallel with the old ones.

This setup will be maintained until Monday, December 10th at 5:00 PM PST (Tuesday, December 11th at 10:00 AM JST) when the old systems will be brought offline. At that time, Mobile devices and Browsers sending events that wrongly cache the in.treasuredata.com and tokyo.in.treasuredata.com domains, or have cached it for a longer period of time than expected, may experience request failure and drop in events. Following this isolated failure, the Mobile devices and Browsers will be expected to automatically resolve to the correct in.treasuredata.com domain and resume sending events.
Dec 3, 23:00 PST
Verifying - As of December 3rd 10:00 PM PST (December 4th 3:00 PM JST), the upgrade process to renew the Mobile (Android, iOS, and Unity) and Javascript Event Collection Backends for the US and Tokyo regions is finished successfully. We're currently monitoring the system.
Dec 3, 21:58 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 3, 17:00 PST
Update - NOTE
This maintenance notice interests customers of both the Arm Treasure Data US and Tokyo regions sending events through the Javascript and Mobile (Android, iOS, and Unity) SDKs.

On Monday, December 3rd starting at 5:00 PM PST (December 4th starting at 10:00 AM JST) we will begin the upgrade process to renew the Mobile (Android, iOS, and Unity) and Javascript Event Collection Backends for the US and Tokyo regions. The renewal is necessary to enable automatic scale-out of the Backend in case of sudden traffic spikes and will greatly contribute to increase the reliability of the system.

The maintenance window will last 6 hours (and until December 3rd at 11:00 PM PST or December 4th at 4:00 PM JST), throughout which we will upgrade two systems for the US region and 1 for the Tokyo region one by one. At the end of the maintenance window, the new Event Collection Backends will be operational and will be serving traffic in parallel with the old ones.

This setup will be maintained until Monday, December 10th at 5:00 PM PST (Tuesday, December 11th at 10:00 AM JST) when the old systems will be brought offline. At that time, Mobile devices and Browsers sending events that wrongly cache the in.treasuredata.com and tokyo.in.treasuredata.com domains, or have cached it for a longer period of time than expected, may experience request failure and drop in events. Following this isolated failure, the Mobile devices and Browsers will be expected to automatically resolve to the correct in.treasuredata.com domain and resume sending events.
Nov 29, 18:41 PST
Update - We will be undergoing scheduled maintenance during this time.
Nov 26, 04:31 PST
Update - We will be undergoing scheduled maintenance during this time.
Nov 22, 06:00 PST
Scheduled - This maintenance notice interests customers of both the Arm Treasure Data US and Tokyo regions sending events through the Javascript and Mobile (Android, iOS, and Unity) SDKs.

On Monday, December 3rd starting at 5:00 PM PST (December 4th starting at 10:00 AM JST) we will begin the upgrade process to renew the Mobile (Android, iOS, and Unity) and Javascript Event Collection Backends for the US and Tokyo regions. The renewal is necessary to enable automatic scale-out of the Backend in case of sudden traffic spikes and will greatly contribute to increase the reliability of the system.

The upgrade will complete approximately Monday, December 10th at 5:00 PM PST (December 11th at 10:00 AM JST), when the current Backend will be replaced and will be brought offline.
At that time, Mobile devices and Browsers sending events that wrongly cache the in.treasuredata.com and tokyo.in.treasuredata.com domains, or have cached it for a longer period of time than expected, may experience request failure and drop in events. Following this isolated failure, the Mobile devices and Browsers will be expected to automatically resolve to the correct in.treasuredata.com domain and resume sending events.
Nov 22, 00:39 PST
Dec 2, 2018

No incidents reported.

Dec 1, 2018

No incidents reported.

Nov 30, 2018

No incidents reported.

Nov 29, 2018

No incidents reported.