Authentication Errors Affecting Semantic Layer and Scheduled Runs
dbt Cloud has authentication errors that cause job run failures in the Semantic Layer Gateway and scheduled job dispatch. The problem started after 03:20 UTC on November 20, 2026. dbt Cloud is investigating.
State
Investigating
Started
Ongoing for
25 min
Worst impact
Partial outage
Timeline
1 updateInvestigating
25 min 100%
Updates
Times in UTCAs posted by dbt Cloud
We’re investigating an issue with the Semantic Layer Gateway and scheduled job dispatch that is causing job run failures due to authentication errors. This issue has been occurring anytime after 03:20 UTC on November 20, 2026. 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 historyIncidents in 90 days
35
Days with an incident
33
Median duration
1 h 46 min
This incident
77% shorter than the median
Other dbt Cloud incidents
All incidentsdbt Cloud·Some users unable to log in with SSO
SSO and enterprise login did not work for dbt Cloud users. The incident is resolved. Sign-in worked normally after the fix.
dbt Cloud·Increased job run times for some accounts
dbt Cloud job runs took longer than usual for some accounts, and BigQuery jobs were particularly affected. dbt Cloud reports that the incident is resolved. It lasted about 94 minutes.
dbt 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.
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