Live

Some users unable to log in with SSO

0

SSO and enterprise login did not work for dbt Cloud users. The incident is resolved. Sign-in worked normally after the fix.

State

Resolved

Started

Lasted

5 h 38 min

Worst impact

Partial outage

Timeline

12 updates
09:0810:3211:5713:2214:46
Partial outageUpdate postedTimes in UTC

Investigating

1 h 37 min 29%

Identified

1 h 36 min 28%

Monitoring

2 h 25 min 43%

Updates

Times in UTC

As posted by dbt Cloud

Monitoring

We’ve deployed a fix across all affected regions, and users who reset their password can now sign in normally. We’re monitoring to make sure sign-in stays stable. No action is needed on your side. If you still can’t sign in, contact [support@getdbt.com](mailto:support@getdbt.com) and include the time of your attempt.

Monitoring

We’re reopening this incident. SSO and email/password sign-ins are working normally for most users. However, some users may be unable to sign in after resetting their password. We’ve identified the cause and are deploying a fix across affected regions. We’ll share another update as the rollout progresses. If you’re unable to sign in, contact [support@getdbt.com](mailto:support@getdbt.com) and include the time of your attempt and whether you recently reset your password.

Resolved

The issue has been resolved. An issue affecting SSO sign-in and password reset caused login failures for a number of users. This has been fixed, and we’ve put measures in place to prevent a recurrence. If you’re still unable to sign in, please contact Support at [support@getdbt.com](mailto:support@getdbt.com).

Resolved

This incident has been resolved. Between about 08:03 and 13:15 UTC on 19 November, customers were unable to sign in to dbt platform through SSO or enterprise login. SSO sign-in, including logins started from your identity provider, has been fully restored, and we have confirmed that it has been working normally since then. No action is needed on your side. If you still have trouble signing in, please contact [support@getdbt.com](mailto:support@getdbt.com). We apologise for the disruption. We will share a root cause analysis with affected customers.

Monitoring

We have applied a fix for the remaining affected customers, and SSO sign-in has now been restored for customers. This includes logins started from your identity provider. We are continuing to monitor to make sure sign-in stays stable. No action is needed on your side. If you still can’t sign in through SSO, please try a private browser window. If it still fails, contact [support@getdbt.com](mailto:support@getdbt.com) and include the time of your attempt.

Monitoring

More affected customers can now sign in through SSO again, and we are continuing to restore access for the remaining customers. No action is needed on your side.

Monitoring

We have started restoring SSO sign-in, and some affected customers can now log in again. We are continuing to restore access for the remaining customers. No action is needed on your side. If you still can’t sign in through SSO, please try again shortly. We will post another update by 13:00 UTC, or sooner if things change.

Monitoring

We have applied a fix, and SSO sign-in has been restored for customers. We are monitoring to make sure logins stay stable. No action is needed on your side. If you still can’t sign in through SSO, please clear your browser cache or try a private window. If it still fails, contact [support@getdbt.com](mailto:support@getdbt.com).

Identified

We are continuing to work on restoring SSO sign-in for affected customers. No action is needed on your side. We will post another update by 12:15 UTC, or sooner if things change.

Identified

We have identified the cause of the SSO sign-in failures affecting customers, which began at about 08:03 UTC on 19 November. Users signing in through SSO or enterprise login, including logins started from your identity provider, may still see a “client not found” or “Server error” page. A change to our sign-in configuration disconnected customer SSO connections. Our engineers are now restoring those connections on each affected instance. Customers on other regions are not affected. We will post another update by 11:30 UTC, or sooner if things change.

Investigating

We are continuing to investigate SSO sign-in failures affecting customers. Since about 08:03 UTC on 19 November, users signing in through SSO or enterprise login may see a “client not found” or “Server error” page. Our engineering teams are actively working on this, and we have paused related changes to our sign-in service while we investigate. Customers on other regions are not affected. We will post another update by 10:45 UTC, or sooner if things change.

Investigating

We are investigating reports that some users can’t sign in to dbt platform through SSO (enterprise login). Since about 08:00 UTC on 19 November 2026, affected users may see a “client not found” or “Server error” page when signing in. Scheduled jobs and other running processes are not known to be affected. Our team is working on this now. We will post another update by 10:00 UTC, or sooner if things change.

dbt Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

34

Days with an incident

32

Median duration

1 h 46 min

This incident

3.2× 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