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.
August 2026
Intermittent Databricks connection Errors
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
majorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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.
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
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
criticalSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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.
