outages.live
Live
dbt CloudIncident ·

Cloud IDE sessions failed to load

ResolvedOfficial update
0

The issue has been resolved, and all affected systems are now functioning normally as of 17:47 UTC. Between 11:24 UTC and 17:47 UTC an issue with a long running CLI worker node resulted in indefinite load times in the IDE. We have put measures in place to prevent a recurrence and IDE behavior 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.

The latest update from dbt Cloud.

State

Resolved

Started

Lasted

8 min

Worst impact

Notice

Timeline

1 update
18:3918:4118:4318:4518:47
NoticeUpdate postedTimes in UTC

Resolved

8 min 100%

Updates

Times in UTC

As posted by dbt Cloud

Resolved

The issue has been resolved, and all affected systems are now functioning normally as of 17:47 UTC. Between 11:24 UTC and 17:47 UTC an issue with a long running CLI worker node resulted in indefinite load times in the IDE. We have put measures in place to prevent a recurrence and IDE behavior 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.

dbt Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

27

Median duration

2 h 17 min

This incident

94% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

30 h 37 min
median 2 h 17 min
90 days agoToday

Other dbt Cloud incidents

All incidents

dbt Cloud·Jobs list and Environment pages failing to load

dbt Cloud could not load the Jobs page, the Project and Environment pages, and run logs for some accounts on the US and EMEA instances. Scheduled jobs continued to run. dbt Cloud reports that the issue is resolved. The outage lasted about 3 hours and 25 minutes.

Resolved

dbt Cloud·Git errors for projects connected to GitHub over SSH

Git operations failed for dbt Cloud projects that use a dbt-managed repository or connect to GitHub with a deploy key. The errors were "Permission denied (publickey)" in job runs and dbt Studio git actions. dbt Cloud reports that this incident is resolved. It lasted 1 minute and 43 seconds.

Resolved

dbt Cloud·dbt Studio error loop with restarting dbt Studio

dbt Cloud reported an error loop in dbt Studio that asked users to restart dbt Studio. The issue affected dbt Project Environments on versions 1.6 and 1.7. dbt Cloud resolved the issue after 86 minutes.

Resolved

dbt Cloud·Expired GitLab project access tokens not refreshing causing failures in posting commit statuses

dbt Cloud did not post GitLab CI job commit statuses for existing projects with expired GitLab project access tokens. This affected a small number of customers in the EU2 (Azure) region. dbt Cloud reports that the issue is resolved and that it lasted about 111 minutes.

Resolved

dbt Cloud·dbt Wizard SQL execution failing

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.

Resolved

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.live/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.live/feed.xml?providers=dbt
Slack
/feed subscribe https://outages.live/feed.xml?providers=dbt

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane