Outage in Treasure Data
[US Region] Presto partial performance degradation and potential job failure
Resolved MinorIncident Report
We are investigating the cause. Queries may be delayed.
Components affected
Treasure Data Presto Query EngineNeed to monitor Treasure Data outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
RESOLVED
over 2 years ago - at 09/04/2023 12:45PM
This incident has been resolved.
INVESTIGATING
over 2 years ago - at 09/04/2023 10:56AM
There was a potential status inconsistency issue on one of our Presto cluster in US region during AM 1:04 - 3:10 UTC on Sep 4. Queries issued during this period have been potentially affected.
You may see failure of INSERT/DELETE jobs with error messages like below. Please do not rerun those especially INSERT jobs because even if the job failed, the writing to your table might have done.
- cannot get transactionId for null transaction
- Cannot complete uploading. This error is temporary and should be recovered by retrying.
CTAS failed with the following error might be also affected by this incident:
- Query exceeded the maximum execution time limit of 6.00h
Also, some of your queries might stuck during this incident.
We are sure that newly issued queries are not affected while we are still working on to identify the impact of this incident.
INVESTIGATING
over 2 years ago - at 09/04/2023 10:55AM
We are continuing to investigate this issue.
INVESTIGATING
over 2 years ago - at 09/04/2023 08:05AM
There was a potential status inconsistency issue on one of our Presto cluster in US region during AM 1:04 - 3:10 UTC on Sep 4. Queries issued during this period have been potentially affected.
You may see failure of INSERT/DELETE jobs with error messages like below. Please do not rerun those especially INSERT jobs because even if the job failed, the writing to your table might have done.
- cannot get transactionId for null transaction
- Cannot complete uploading. This error is temporary and should be recovered by retrying.
CTAS failed with the following error might be also affected by this incident:
- Query exceeded the maximum execution time limit of 6.00h
Also, some of your queries might stuck during this incident.
We are sure that newly issued queries are not affected while we are still working on to identify the impact of this incident.
INVESTIGATING
over 2 years ago - at 09/04/2023 05:33AM
There might be potential status inconsistency in your INSERT jobs if they failed with error messages like below:
- Cannot complete uploading. This error is temporary and should be recovered by retrying
- cannot get transactionId for null transaction
Please do not rerun those jobs because even if the job failed, the writing to your table might work. We are still working on to identify the impact of this incident.
INVESTIGATING
over 2 years ago - at 09/04/2023 03:10AM
We are investigating the cause. Queries may be delayed.
Latest Treasure Data outages
US region: Treasure Insights unavailable - about 2 months ago
[US/Tokyo Region] Performance issues - 2 months ago
[All Region] Service Disruption on Treasure Insights - 4 months ago
[All Regions] Profile API Errors and SSO Logins - 6 months ago
Never miss outages in third-party dependencies
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with
