outages.live
Live

dbt Cloud

dbt Cloud is operational

Checked 1 min ago Operational

History

90 days agoToday

Incidents in 90 days

22

Days with an incident

24

Median duration

2 h 58 min

Longest incident

30 h 37 min

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration1 h 27 min17:10 to 18:38dbt Wizard SQL execution failingPartial outage

The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.

Oct 28, 2026

Duration4 h 22 min20:34 to 00:56Degraded performance across dbt platformDegraded

The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause

Oct 22, 2026

Duration12 h 6 min17:21 to 05:27dbt deps failures in dbt job runs and StudioDegraded

The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Oct 20, 2026

Duration8 h 11 min06:55 to 15:07Delayed and stuck job runs in EMEADegraded

**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.

Oct 15, 2026

Duration3 h13:09 to 16:10Intermittent dbt package download failuresDegraded

The issue has been resolved, and all affected systems are now functioning normally as of 16:10 UTC. We have put measures in place to prevent a recurrence and dbt package installations have returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Oct 13, 2026

Duration6 h 5 min22:28 to 04:33Unable to Access dbt PlatformMajor outage

This incident has been resolved. A fix was deployed for the dbt platform issue that was causing problems with access to the web application and the Admin API. Both are now operating normally. If you are still experiencing issues, please contact us at [support@getdbt.com](mailto:support@getdbt.com).

Oct 8, 2026

Duration30 h 37 min16:19 to 22:56Run logs and artifacts missing for some runs (US Cell 3, GCP)Degraded

The issue has been resolved, and all affected systems are now functioning normally as of 1:20 PM Eastern on October 8. Between 11:30 AM and 1:20 PM Eastern, an issue with run artifact and log storage in US Cell 3 (GCP) resulted in some job runs completing without their logs and artifacts (such as manifest.json and run_results.json) being available, and some runs that use deferral failing. We have put measures in place to prevent a recurrence and run artifact and log storage has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.

Oct 2, 2026

Duration1 h 29 min11:05 to 12:34Increased errors for Wizard CLI requests using Anthropic modelsDegraded

The issue has been resolved, and all affected systems are now functioning normally as of 12:30 UTC. We have put measures in place to prevent a recurrence and the system has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Sep 30, 2026

Duration56 min22:13 to 23:09dbt deps failures impacting private packagesDegraded

The issue has been resolved, and all affected systems are now functioning normally as of 9:55 PM UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Sep 24, 2026

Duration5 h 28 min23:56 to 05:24GitLab service disruptionDegraded

This incident has now been resolved. Please refer to GitLab for more details:

Duration12 h 23 min13:27 to 01:50Intermittent BigQuery job failures using Workload Identity Federation in EMEADegraded

The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Sep 23, 2026

Duration4 min22:59 to 23:03Intermittent dbt deps failuresDegraded

The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Sep 18, 2026

Duration14 h 58 min23:31 to 14:30Schema Hydration PanicPartial outage

This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Follow dbt Cloud

Your coding agent knows when dbt Cloud is down, and tells you when a failure is theirs, not yours. You can also get dbt Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dbt" and tell me if dbt Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=dbt
Slack
/feed subscribe https://outages.cc/feed.xml?providers=dbt

Go from tracking outages to fixing production issues with Polylane.

Try Polylane