dbt Cloud Outage History

dbt Cloud is up right now

Pingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 201 in the last 90 days.

Source: status.getdbt.com

767incidents recorded

767last 12 months

201last 90 days

7 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking dbt Cloud in April 2026, so earlier months are not shown. Hover a bar for its value.

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 599 (11%)

Incidents, newest first

Minor March 6, 2026 [US 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.

Read the full incident report →

Minor March 6, 2026 [US Cell 2 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.

Read the full incident report →

Minor March 6, 2026 [US Cell 3 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.

Read the full incident report →

Minor March 6, 2026 [US Cell 4 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.

Read the full incident report →

Critical March 5, 2026 Connectivity Errors When Starting dbt Studio and Deployment Runs 2h 58m

Started Mar 05, 2026, 03:57 PM UTC· resolved Mar 05, 2026, 06:55 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 5, 2026 [EU Cell 1 GCP] Connectivity Errors When Starting dbt Studio and Deployment Runs 2h 58m

Started Mar 05, 2026, 03:57 PM UTC· resolved Mar 05, 2026, 06:55 PM UTC

investigating Mar 05, 2026, 03:57 PM UTC

We are investigating an intermittent issue with an internal service that is causing connectivity failures. As a result, some users in the GCP US and EMEA regions may experience: 1. Failures when starting dbt Studio sessions 2. Delays when executing or cancelling deployment runs This behavior has been observed starting around 10:18 AM Eastern. Our engineering team is actively working on a resolution. We will post the next update in approximately 15 minutes, or sooner if new information becomes available.
monitoring Mar 05, 2026, 05:11 PM UTC

We have deployed a fix for connectivity issues in an internal service that was causing failures in starting dbt Studio and delays in executing/canceling deployment runs. Both dbt Studio and scheduled jobs have returned to its normal state and we are continuing to monitor.
resolved Mar 05, 2026, 06:55 PM UTC

The issue has been resolved, and all affected systems are now functioning normally as of 2026-03-05 8:06 PM EST. Between 10:18 AM EST and 8:06 PM EST an issue with an internal service resulted in failures in starting dbt Studio and scheduled jobs . We have put measures in place to prevent a recurrence and the dbt Studio and scheduled jobs have 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.

Read the full incident report →

Minor March 5, 2026 [US Cell 1 GCP] Connectivity Errors When Starting dbt Studio and Deployment Runs 2h 58m

Started Mar 05, 2026, 03:57 PM UTC· resolved Mar 05, 2026, 06:55 PM UTC

investigating Mar 05, 2026, 03:57 PM UTC

We are investigating an intermittent issue with an internal service that is causing connectivity failures. As a result, some users in the GCP US and EMEA regions may experience: 1. Failures when starting dbt Studio sessions 2. Delays when executing or cancelling deployment runs This behavior has been observed starting around 10:18 AM Eastern. Our engineering team is actively working on a resolution. We will post the next update in approximately 15 minutes, or sooner if new information becomes available.
monitoring Mar 05, 2026, 05:11 PM UTC

We have deployed a fix for connectivity issues in an internal service that was causing failures in starting dbt Studio and delays in executing/canceling deployment runs. Both dbt Studio and scheduled jobs have returned to its normal state and we are continuing to monitor.
resolved Mar 05, 2026, 06:55 PM UTC

The issue has been resolved, and all affected systems are now functioning normally as of 2026-03-05 8:06 PM EST. Between 10:18 AM EST and 8:06 PM EST an issue with an internal service resulted in failures in starting dbt Studio and scheduled jobs . We have put measures in place to prevent a recurrence and the dbt Studio and scheduled jobs have 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.

Read the full incident report →

Minor March 4, 2026 Linting Error from Request Dependency Warning 4h 44m