Live

Authentication Maintenance – Possible Login Disruption

MaintenanceOfficial update

We are performing a platform-wide maintenance update and rotating authentication secrets used by our identity provider. Impact window: 19 Nov 2026 02:00 – 04:00 UTC During this window, you may be unable to log in to dbt. If you are already logged in, you may be signed out and will need to log in again once the rotation is complete. We do not expect any impact to scheduled jobs or uncommitted work in the Studio (IDE), but unsaved changes in the dbt platform UI (eg, environment, job, or project settings) may be lost. We will post updates here as the work progresses and confirm once the rotation is complete.

The latest update from dbt Cloud.

State

Scheduled

Started

Ongoing for

15 min

Worst impact

Maintenance

Timeline

1 update
01:3801:4101:4501:4901:53
MaintenanceUpdate postedTimes in UTC

Scheduled

15 min 100%

Updates

Times in UTC

As posted by dbt Cloud

Scheduled

We are performing a platform-wide maintenance update and rotating authentication secrets used by our identity provider. Impact window: 19 Nov 2026 02:00 – 04:00 UTC During this window, you may be unable to log in to dbt. If you are already logged in, you may be signed out and will need to log in again once the rotation is complete. We do not expect any impact to scheduled jobs or uncommitted work in the Studio (IDE), but unsaved changes in the dbt platform UI (eg, environment, job, or project settings) may be lost. We will post updates here as the work progresses and confirm once the rotation is complete.

dbt Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

33

Days with an incident

31

Median duration

1 h 42 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

30 h 37 min
median 1 h 42 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