dbt Cloud Outage History
dbt Cloud is up right nowPingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 201 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 82 | 70 of 720 (10%) |
| May 2026 | 126 | 155 of 744 (21%) |
| June 2026 | 55 | 40 of 720 (6%) |
| July 2026 | 81 | 29 of 744 (4%) |
| August 2026 | 78 | 22 of 744 (3%) |
| September 2026 | 77 | 53 of 720 (7%) |
| October 2026 | 44 | 69 of 596 (12%) |
Incidents, newest first
Critical March 9, 2026 dbt cloud application is down in US GCP instance 2h 58m
Started Mar 09, 2026, 12:11 PM UTC· resolved Mar 09, 2026, 03:10 PM UTC
No vendor updates were posted for this incident.
Minor March 9, 2026 [US Cell 1 AZURE] dbt Studio Unavailable 4h 29m
Started Mar 09, 2026, 09:11 AM UTC· resolved Mar 09, 2026, 01:40 PM UTC
- investigating Mar 09, 2026, 09:11 AM UTC
We're investigating an issue with dbt Studio in Azure US. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- monitoring Mar 09, 2026, 01:38 PM UTC
We have deployed a fix that was causing issues with dbt Studio. dbt Studio has returned to its normal state and we are continuing to monitor.
- resolved Mar 09, 2026, 01:40 PM UTC
The issue has been resolved, and all affected systems are now functioning normally/ We have put measures in place to prevent a recurrence and the dbt Studio has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Major March 6, 2026 Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h
Started Mar 06, 2026, 07:04 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
No vendor updates were posted for this incident.
Minor March 6, 2026 [APAC AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EMEA AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EMEA Cell 1 AZURE] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EU Cell 1 GCP] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EU4 Cell 1 GCP] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [JP Cell 1 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 1 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 1 AZURE] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 1 GCP] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 2 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 3 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 4 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances 3h 33m
Started Mar 06, 2026, 06:32 PM UTC· resolved Mar 06, 2026, 10:05 PM UTC
- investigating Mar 06, 2026, 06:32 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 06:47 PM UTC
We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 07:02 PM UTC
We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor.
- investigating Mar 06, 2026, 07:05 PM UTC
We're investigating the session occupied errors in Studio. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
- identified Mar 06, 2026, 08:29 PM UTC
We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 09:07 PM UTC
We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 10:05 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Major March 6, 2026 Metadata API returning HTTP 500 errors 3m
Started Mar 06, 2026, 06:06 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
No vendor updates were posted for this incident.
Minor March 6, 2026 [APAC AWS] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EMEA AWS] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EMEA Cell 1 AZURE] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EU Cell 1 GCP] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [EU4 Cell 1 GCP] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US AWS] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 1 AWS] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor March 6, 2026 [US Cell 1 AZURE] Metadata API returning HTTP 500 errors 35m
Started Mar 06, 2026, 05:35 PM UTC· resolved Mar 06, 2026, 06:10 PM UTC
- identified Mar 06, 2026, 05:35 PM UTC
We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly.
- monitoring Mar 06, 2026, 06:03 PM UTC
We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor.
- resolved Mar 06, 2026, 06:10 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.