Live

Authentication Errors Affecting Semantic Layer and Scheduled Runs

Partial outageOfficial update
0

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 update
05:2505:3105:3705:4305:49
Partial outageUpdate postedTimes in UTC

Investigating

25 min 100%

Updates

Times in UTC

As posted by dbt Cloud

Investigating

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 history
90 days agoToday

Incidents in 90 days

35

Days with an incident

33

Median duration

1 h 46 min

This incident

77% 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

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