# dbt Labs: Some users unable to log in with SSO

> dbt Labs reported a major SSO login outage starting at 2026-11-19 09:08 UTC, with symptoms since about 08:00 UTC: some users saw “client not found” or “Server error.” Scheduled jobs and running processes were not known to be affected; the incident remained under investigation when archived (open for

Canonical: https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180
Last updated: 2026-11-19T23:53:07Z

- Impact (vendor’s label): major
- Status: resolved · edited after publishing
- Started: 2026-11-19 09:08 UTC · Resolved: 2026-11-19 23:52 UTC · Duration: 15 h
- Updates: 12 · Affected components: 01JBCBN0GSSHNCJV04B2ZJDK5C, 01JBCBN0GSSHNCJV04B2ZJDK5C, 01JBCBN0GSSHNCJV04B2ZJDK5C, 01JBCBN1R2PYS6R4ZB2R7YJAJP, 01JBCBN1R2PYS6R4ZB2R7YJAJP, 01JBCBN30DJ5BZVF93H8VK91N9, 01JBCBN30DJ5BZVF93H8VK91N9, 01JBCBN5GN1XXEKXXFZFWH019B, 01JBCD301RF72EFA9T0SYQMPGK, 01JBCQR98ZHT9HPXEP653E7STS, 01JBCQR98ZHT9HPXEP653E7STS, 01JBCQR98ZHT9HPXEP653E7STS, 01JBCQW0M71TB54AJ1SQD3PCPA, 01JBCQW0M71TB54AJ1SQD3PCPA, 01JBCR0YNN55BHKE1DXAAH95AD, 01JH8R89TPXSS7PMS53QAW76B8, 01JH8R89TPXSS7PMS53QAW76B8, 01JRKCJTBQ1RY4B0JJ4322XX1F, 01K1EH8NHV58CPRW4SGEFMMWQQ, 01K4T29F32GG16H0DEC4G3NZG5, 01KF46A8MMX1VQV3XE7B0PE0BC, 01KX12QA4BDFTS3T44GBTA3PBA
- [Vendor status page: https://status.getdbt.com/incidents/01M7SH0PTWMXV432VMWE60Q180](https://status.getdbt.com/incidents/01M7SH0PTWMXV432VMWE60Q180)
- [Company: dbt Labs](https://rewindex.com/company/dbt-labs.md)

## Summary

dbt Labs reported a major SSO login outage starting at 2026-11-19 09:08 UTC, with symptoms since about 08:00 UTC: some users saw “client not found” or “Server error.” Scheduled jobs and running processes were not known to be affected; the incident remained under investigation when archived (open for 0 min at the last update). _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-11-19 09:08 UTC: 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.
- **investigating** 2026-11-19 10:04 UTC: 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.
- **identified** 2026-11-19 10:45 UTC: 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.
- **identified** 2026-11-19 11:38 UTC: 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.
- **monitoring** 2026-11-19 12:19 UTC _(deleted by the vendor)_: 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.
- **monitoring** 2026-11-19 12:27 UTC: 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** 2026-11-19 12:29 UTC: 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** 2026-11-19 13:19 UTC: 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.
- **resolved** 2026-11-19 14:46 UTC: 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** 2026-11-19 19:11 UTC: 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.
- **monitoring** 2026-11-19 21:51 UTC: 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.
- **resolved** 2026-11-19 23:52 UTC: 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.

## Rewindex changes for this incident

- 2026-11-19 09:08 UTC: [Major incident: Some users unable to log in with SSO](https://rewindex.com/change/i8a50c494e96630.md)
- 2026-11-19 10:13 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r5bfa884f933038.md)
- 2026-11-19 10:53 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r68b62c8fb49d95.md)
- 2026-11-19 11:43 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r568909a5088ccd.md)
- 2026-11-19 12:23 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/ra0cbc2ae43382a.md)
- 2026-11-19 12:33 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r38a33ddc47f376.md)
- 2026-11-19 13:23 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r483a6c47cc1ca5.md)
- 2026-11-19 14:53 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r7b81f53f5b4c05.md)
- 2026-11-19 19:13 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r3c6e1d915e33c0.md)
- 2026-11-19 21:53 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r5d45f93ad5d6eb.md)
- 2026-11-19 23:53 UTC: [Incident updated: Some users unable to log in with SSO](https://rewindex.com/change/r9653a888f64a7e.md)

## Cite this

Status incident (vendor impact label: major) posted by dbt Labs, started 2026-11-19 09:08 UTC, resolved after 15 h, 12 update(s); edited after publishing.

- Canonical URL: https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180
- Citation: dbt Labs, “Some users unable to log in with SSO” (2026-11-19 09:08 UTC). Archived by Rewindex: https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180 (CC BY 4.0).
- Markdown link: `[dbt Labs: Some users unable to log in with SSO (2026-11-19)](https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180)`


---
Canonical: https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180 · Markdown: https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180.md · JSON: https://rewindex.com/api/v1/companies/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-20T01:01:08.309Z
