dbt Cloud Outage History
Daily status observations, past incidents, and reported issue history for dbt Cloud.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 68% | 25 | 8 |
| July 2026 | 67.7% | 31 | 10 |
| June 2026 | 76.7% | 30 | 7 |
| May 2026 | 20% | 5 | 4 |
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.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Intermittent Databricks connection Errors
Started:
monitoring
We have observed recovery for the issue affecting a some customers in our AU multi-tenant environment using Databricks connections. Errors have not recurred since 9:07 PM PDT / 12:07 PM AEST.
We are continuing to monitor and will provide another update once the issue is fully resolved.
investigating
We are investigating an issue affecting some customers in the AU multi-tenant environment using Databricks connections. Impacted customers may see failed runs or IDE connection errors due to intermittent errors refreshing Databricks credential tokens.
Our team is investigating and will provide another update as we learn more.
Degraded Discovery API performance
Started:
identified
We have identified an issue with the Discovery API that may have resulted is failed API requests.. A fix has been implemented, and we will provide an update shortly.
Studio AI assistant (Wizard) tool errors
Started:
identified
We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.
investigating
We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.
Git Failures in dbt Platform
Started:
monitoring
The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.
identified
An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories.
This is being addressed on GitHub's side. You can follow their progress here: [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx "https://www.githubstatus.com/incidents/zkxwbgr0cnmx")
We are monitoring close...
investigating
We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern.
This is being addressed on GitHub's side. You can follow their progress here: [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx "https://www.githubstatus.com/incidents/zkxwbgr0cnmx")
ai-codegen-api-increased-error-rate
Started:
monitoring
A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.
identified
Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.
identified
We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused
by a change in an upstream service. A fix is being implemented and we will provide an
update shortly.
investigating
We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio.
Users may see errors or failed responses when running agent requests, and conversations
that have already hit the error may continue to fail. Other areas of the dbt platform,
including the IDE, job orchestration, and MCP connections, are not impacted. The team is
working on a resolution and we will provide updates as soon as new information becomes
available.
Potential intermittent admin APIs requests failing
Started:
monitoring
We have deployed a fix for the memory issue that caused intermittent errors on admin APIs requests. Our admin API has returned to its normal state and we are continuing to monitor.
investigating
We're investigating an issue with our system's memory that is causing intermittent 500 or 502 errors with admin APIs requests. The team is working on a resolution and we will provide updates as soon as new information comes in.
Fusion Stable: BigQuery incremental model builds affected, rolled back
Started:
monitoring
We've rolled back the affected Fusion builds and are monitoring the results. This issue affected customers using BigQuery as their connected data warehouse where the execution project differs from the target project. If you continue to experience issues, please contact support. Next update by 18:15 UTC or sooner if the status changes.
investigating
We're investigating an issue where a very small percentage of job runs on dbt Fusion Stable were served the Fusion canary release track (v2.0.0-preview.206). Runs on this canary fusion version specifically affected incremental model builds. We are working on rolled back the affected build and are working to identify all impacted runs. We'll post an update by 17:32 UTC.
investigating
We're investigating an issue where a very small percentage of job runs on dbt Fusion Stable were served the Fusion canary release track (v2.0.0-preview.206). Runs on this canary Fusion version specifically affected incremental model builds. We are working on rolling back the affected build and are working to identify all impacted runs. We'll post an update by 17:25 UTC.
July 2026
AI Codegen (Wizard) unavailable in EMEA
Started:
monitoring
Reported at 08:21 UTC on 29 July 2026, we identified errors affecting AI Codegen (Wizard) for users in EMEA. A fix was deployed at 08:35 UTC, and we are currently monitoring — the system appears to be functioning normally.
We apologise for any disruption this may have caused.
Major - insecure connection in dbt Platform
Started:
monitoring
We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor.
investigating
We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.
Scheduled jobs are intermittently affected by job failures caused by 403 error
Started:
monitoring
Failure rates for job runs during the git repository clone step in our EMEA infrastructure remain at normal levels, with no further occurrences in the last 60 minutes. We have not identified or deployed a specific fix, and we are continuing to closely monitor. We will provide a further update once we can confirm full resolution, or sooner if the issue recurs.
investigating
> We're continuing to closely monitor an issue causing intermittent job failures during the git repository clone step within our EMEA infrastructure. We have seen no further occurrences in the last 45 minutes, though a root cause has not yet been confirmed. We will provide a further update within the hour, or sooner if there is a material change.
investigating
We're continuing to investigate intermittent job failures during the git repository clone step, affecting our EMEA infrastructure. Failure rates have dropped significantly since earlier today, and we've seen no further occurrences in the last 30 minutes. A root cause has not yet been confirmed. We're continuing to closely monitor and will provide a further update within the hour, or sooner if there is a material change.
investigating
We saw a further burst of job failures during the git repository clone step earlier, consistent with the intermittent pattern we've seen throughout this incident. A root cause has not yet been confirmed. We're continuing to closely monitor and investigate, and will provide a further update within the hour, or sooner if there is a material change.
investigating
The rate of job failures during the git repository clone step remains much lower than earlier today, though we're continuing to see occasional, isolated failures. A root cause has not yet been confirmed. We're continuing to closely monitor and will provide a further update within the hour, or sooner if there is a material change.
investigating
The rate of job failures during the git repository clone step has dropped significantly. We have not identified or deployed a specific fix, and we're continuing to closely monitor to confirm this improvement holds. We'll provide a further update once we can confirm full recovery, or sooner if the issue resumes.
investigating
We're continuing to investigate an issue causing intermittent job run failures during the git repository clone step, with an error referencing an HTTP 403 response, affecting our EMEA infrastructure only. Based on further investigation, we do not believe the dbt Studio IDE has been affected by this issue. Our engineering team continues to investigate and we will provide a further update within the hour.
investigating
We're continuing to investigate an issue causing intermittent job run failures during the git repository clone step, with an error referencing an HTTP 403 response. We've reduced the scope of this issue, it is affecting our EMEA infrastructure only. We're still confirming whether the dbt Studio IDE is affected for any users. Our engineering team continues to investigate and we will provide a further update within the hour.
investigating
We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available.
investigating
We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.
Unable to create or edit environment variables in dbt platform user interface
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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 '_'
Started:
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
Started:
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
Started:
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
Started:
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.
Discovery API returning stale data
Started:
investigating
We're investigating an issue with the Discovery API that is causing stale data. This is impacting systems using metadata, such as dbt Catalog and dbt Mesh, in US MT anytime after 10:30 PM UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.
All other systems are not impacted and should be running as expected.
May 2026
Compile button error in Studio IDE
Started:
monitoring
identified
investigating
dbt1410 noisy warning logs
Started:
monitoring
identified
investigating
dbt Platform experiencing connectivity issues
Started:
monitoring
identified
investigating
investigating
Elevated errors affecting Studio IDE sessions – US Azure region
Started:
monitoring
identified
investigating
Snowflake jobs may time out on Latest release track
Started:
monitoring
identified
investigating
Billing Admin Page Requests Intermittently Failing
Started:
monitoring
identified
monitoring
investigating
dbt Platform CI Outage for AzureDevOps Integrations
Started:
monitoring
identified
investigating
dbt Platform CLI State Selector Failing
Started:
monitoring
identified
investigating
Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
Started:
monitoring
investigating
Degraded performance for dbt Copilot
Started:
monitoring
identified
investigating
dbt Studio failing to load
Started:
monitoring
identified
identified
investigating
Delayed Audit logs
Started:
investigating
target.user resolving to None in development environments
Started:
monitoring
identified
identified
investigating
April 2026
FlightSQL authentication error on Semantic Layer failing with working service token
Started:
monitoring
Small percentage of 429 errors impacting very few users
Started:
investigating
Login Authentication code exchange failures
Started:
monitoring
investigating
deps failures due to private packages in dbt Platform
Started:
monitoring
identified
identified
investigating
Job Run logs unavailable
Started:
identified
identified
investigating
Latest versions of files not showing recent commits in Studio
Started:
monitoring
identified
investigating
Runs not Starting
Started:
investigating
"Something went wrong" message displaying on dbt Platform job pages
Started:
monitoring
identified
investigating
dbt cloud is unreachable - 502 bad gateway on US MT
Started:
monitoring
investigating
Delays in artifact processing for completed job runs
Started:
monitoring
identified
March 2026
Azure US MC is down
Started:
monitoring
investigating
Experiencing issues with Copilot/AI functionality due to OpenAI outage
Started:
identified
investigating
Orchestration jobs failing in US MT C2
Started:
monitoring
identified
Audit Log Events Delayed
Started:
monitoring
identified
investigating
Studio Errors with Snowflake OAuth Authentication
Started:
monitoring
identified
identified
identified
resolved
monitoring
investigating