Increased job run times for some accounts
dbt Cloud job runs take longer than usual for some accounts, and BigQuery jobs are particularly affected. dbt Cloud reports that the issue is identified and a fix is in progress. Users with longer run times can contact support@getdbt.com with their account ID and example run IDs.
State
Identified
Started
Ongoing for
26 min
Worst impact
Degraded
Timeline
2 updatesIdentified
26 min 100%
Updates
Times in UTCAs posted by dbt Cloud
We’ve identified an issue with job runs that is causing longer than usual run times. BigQuery jobs are particularly affected. The team is working on a resolution and we will provide updates as soon as new information becomes available. If you are experiencing longer than usual run times, please reach out to [support@getdbt.com](mailto:support@getdbt.com) with your account ID and example run IDs.
We have identified an issue with [`X component/system`] that resulted in [`Y customer impact`]. A fix is being implemented, and we will provide an update shortly.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
33
Days with an incident
31
Median duration
1 h 46 min
This incident
75% shorter than the median
Other dbt Cloud incidents
All incidentsdbt Cloud·500 errors when attempting to access Studio and link Github account
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.
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.
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.
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.
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.
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.
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.
https://outages.live/feed.xml?providers=dbt/feed subscribe https://outages.live/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane