Looking for an update now? Check the current status, or follow dbt Cloud for future changes.
70.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
66.7%
30
10
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
49 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Unable to create or edit environment variables in dbt platform user interface
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.
identified
We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.
investigating
We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides.
The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.
investigating
We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides.
The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.
Job runs failing at the git clone step
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again.
Any runs that failed during the incident can now be retried.
We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.
identified
We have identified the cause as an upstream GitHub incident affecting SSH authentication for **deploy keys**. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from **GitHub** are failing at the "Clone git repository" step with a `Permission denied (publickey)` error.
Runs that connect to other providers (for example GitLab or Azure DevOps) are **not** affected.
This is being addressed on GitHub's side. You can follow their...
investigating
We're investigating an issue with **repository cloning** that is causing **scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step**. This is impacting **job runs across all regions (multi-tenant and single-tenant)** anytime after **approximately 3:40 AM ET (07:40 UTC)**. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
**Update — 10:29 UTC**
Git clone errors have remained at normal levels since our last update, with no recurrence. No fix was deployed on our side, and a specific root cause has not yet been confirmed.
We are continuing to monitor
monitoring
Update — 09:50 UTC
Git clone error rates for scheduled and triggered job runs in the EMEA region via our GitHub App integration are starting to return to normal.
The issue appears to be resolving on its own; no fix has been deployed on our side. We have not yet confirmed a specific root cause — investigation is ongoing, with focus on the GitHub App's authentication path.
We are closely monitoring to confirm this recovery holds.
investigating
Update — 08:04 UTC
We've confirmed this issue is isolated to scheduled and triggered job runs in the EMEA region that use our GitHub App integration to clone repositories. The dbt platform IDE and CLI are not affected — we've verified successful Git activity through those paths throughout the incident window.
Our team has traced the failures to the GitHub App's authentication path and is now working on validating the installation configuration for this region.
We will continue to provi...
investigating
We're investigating an issue with Git clone operations via our GitHub App integration that is causing scheduled jobs to fail when cloning repositories. Starting from 2026-07-18 23:00 UTC.
The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
Studio IDE experiencing issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Studio IDE has returned to its normal state and we are continuing to monitor.
investigating
We're investigating an issue with Studio IDE that is causing the page to refresh. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
Deployment jobs are not impacted and should be running as expected.
Intermittent slowness on login.dbt.com and loading account information
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Beginning at approximately 2026-07-10 09:40 UTC, some users experienced intermittent slowness when signing in to [login.dbt.com](http://login.dbt.com) or loading account information, caused by an infrastructure resource constraint affecting a backend service. We identified the cause and applied a mitigation at approximately 2026-07-10 10:45 UTC, and performance returned to normal by approximately 2026-07-10 10:50 UTC. We are continuing to monitor while we work on a permanent fix.
Minor delay in job runs starting
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
From ~00:01 UTC until ~00:06 UTC, a small number of deployment jobs may have experience a brief delay of ~4s (minimum) to ~5m (maximum) before starting. The underlying transient network issue has been resolved and we are continuing to monitor. There has been no other impact. Please contact us at support@getdbt.com with any questions or concerns.
June 2026
Snowflake Authentication failure in Development environments if the Account name has an '_'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants.
We are monitoring to confirm error rates remain at baseline. Please reach out to support@getdbt.com if you have any further questions.
identified
We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures.
Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials.
**Workaround:** Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for e...
LSP connection errors in Studio
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a fix with the Studio IDE that is causing the LSP Server connection to error. We are continuing to monitor.
identified
We have identified an issue with the Studio IDE that is causing the LSP Server connection to error. A fix is being implemented, and we will provide an update shortly.
investigating
We're investigating an issue with the Studio IDE that is causing the LSP Server connection to error. This is impacting server status and compilation in the Studio IDE anytime after June 18th around 2 PM Eastern. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
Login Distruption
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have Identified and deployed a fix for the global login service that was causing users not to be able to login. The global Login services has returned to its normal state and we are continuing to monitor.
Customer login access disruption
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a fix for the login issue that was causing users to encounter "Access denied" error. This has returned to its normal state and we are continuing to monitor.
identified
We have identified an issue with user's access to dbt platform. This is causing customers to see an "Access denied" error when attempting to authenticate. A fix is being implemented, and we will provide an update shortly.
