rewindex

Companiesdbt LabsIncidents

dbt Labs: Some users unable to log in with SSO

MajorStatus: monitoringeditedStarted Not resolved10 updatesstatus.getdbt.com (opens in new tab)
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 from the archived incident (Sol). Check the timeline before relying on it.

Affected components: 01JBCBN0GSSHNCJV04B2ZJDK5C01JBCBN0GSSHNCJV04B2ZJDK5C01JBCBN0GSSHNCJV04B2ZJDK5C01JBCBN1R2PYS6R4ZB2R7YJAJP01JBCBN1R2PYS6R4ZB2R7YJAJP01JBCBN30DJ5BZVF93H8VK91N901JBCBN30DJ5BZVF93H8VK91N901JBCBN5GN1XXEKXXFZFWH019B01JBCD301RF72EFA9T0SYQMPGK01JBCQR98ZHT9HPXEP653E7STS01JBCQR98ZHT9HPXEP653E7STS01JBCQR98ZHT9HPXEP653E7STS01JBCQW0M71TB54AJ1SQD3PCPA01JBCQW0M71TB54AJ1SQD3PCPA01JBCR0YNN55BHKE1DXAAH95AD01JH8R89TPXSS7PMS53QAW76B801JH8R89TPXSS7PMS53QAW76B801JRKCJTBQ1RY4B0JJ4322XX1F01K1EH8NHV58CPRW4SGEFMMWQQ01K4T29F32GG16H0DEC4G3NZG501KF46A8MMX1VQV3XE7B0PE0BC01KX12QA4BDFTS3T44GBTA3PBA

Timeline of updates

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. monitoringDeleted 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.getdbt.com (opens in new tab).

Cite this

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

Title
Some users unable to log in with SSO
Vendor
dbt Labs
Date
URL
https://rewindex.com/company/dbt-labs/incidents/01M7SH0PTWMXV432VMWE60Q180

dbt Labs profileRecent dbt Labs incidentsAll outages on November 19, 2026dbt Labs in November 2026MarkdownJSON