Live

500 errors when attempting to access Studio and link Github account

0

dbt Cloud had 500 errors that stopped access to dbt Studio and the linking of GitHub accounts. dbt Cloud reports that the issue is resolved. The outage lasted 50 minutes.

State

Resolved

Started

Lasted

50 min

Worst impact

Partial outage

Timeline

3 updates
19:4719:5920:1220:2420:37
Partial outageDegradedUpdate postedTimes in UTC

Investigating

50 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 19:48 UTC. Customers were reporting 500 errors when attempting to access dbt Studio or when linking Github accounts due to an external issue with IP allowlist rules. Please contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.

Investigating

We’re investigating an issue with the Github integration that is causing 500 errors when attempting to access dbt Studio or linking Github accounts. The team is working on a resolution and we will provide updates as soon as new information becomes available.

Investigating

We’re investigating an issue with the Github integration that is causing 500 errors when attempting to access dbt Studio or linking Github accounts. The team is working on a resolution and we will provide updates as soon as new information becomes available.

dbt Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

32

Days with an incident

30

Median duration

1 h 46 min

This incident

53% 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 1 h 46 min
90 days agoToday

Other dbt Cloud incidents

All incidents

dbt Cloud·dbt Jobs failing for some accounts with dbt State

dbt Cloud jobs that use dbt State failed for some accounts. Runs failed with the error "Cannot determine the account ID. Please make sure dbt State is enabled in your account." The incident is resolved. dbt Cloud reports the problem lasted from 20:41 UTC to 21:30 UTC.

Resolved

dbt Cloud·Update to spark-utils package causing job run failures

dbt Cloud job runs failed with a compilation error for projects that use the spark-utils package on adapters other than Databricks/Spark. dbt Cloud released version 0.3.5 on the dbt Hub as a fix. The issue is resolved and lasted 58 minutes.

Resolved

dbt Cloud·Wizard agent conversations returning errors

dbt Cloud Wizard agent conversations that use Anthropic models returned an error on every new message. dbt Cloud reports that the incident is resolved. The incident lasted about 102 minutes.

Resolved

dbt Cloud·Wizard agent conversations returning errors

dbt Cloud Wizard agent conversations returned errors on new messages. The issue affected conversations that used Anthropic models. dbt Cloud resolved the incident after about 62 minutes. As a workaround, switching to an OpenAI model restored functionality.

Resolved

dbt Cloud·Cloud IDE sessions failed to load

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.

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