dbt Cloud Outage History

Started Nov 10, 2026, 02:05 AM UTC· resolved Nov 10, 2026, 02:05 AM UTC

1. resolved Nov 10, 2026, 02:05 AM UTC

   This incident has been resolved. Between 02:05 and 04:13 UTC on November 10, 2026, the dbt State service had intermittent availability problems and timeouts. During this window, some dbt platform runs couldn’t reach dbt State and ran without it. Those runs completed normally and produced correct results, but they didn’t get the State-based optimizations, such as reusing prior results and making clone decisions. As a result, some runs may have taken longer than usual. Apologies for the inconveniences caused. Please contact us at [email protected] with any questions or concerns.

Read the full incident report →

Started Nov 04, 2026, 01:53 PM UTC· resolved Nov 04, 2026, 08:57 PM UTC

1. investigating Nov 04, 2026, 07:06 PM UTC

   We began investigating at 2026-11-04 19:06 UTC an issue affecting the Jobs page, Project and Environment pages, and run logs for some accounts. Affected users may see an empty jobs list or an error when loading these pages, and may be unable to view, edit, create, or manually trigger jobs. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Nov 04, 2026, 08:44 PM UTC

   We have identified an issue with the Jobs page, Project and Environment pages, and run logs that was caused by a recent deployment. Some accounts may see an empty jobs list or errors when loading these pages. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. A fix is being implemented and we will provide an update shortly.

3. monitoring Nov 04, 2026, 08:57 PM UTC

   We have deployed a fix for the issue affecting the Jobs page, Project and Environment pages, and run logs, and these pages returned to normal as of 2026-11-04 20:57 UTC. We are continuing to monitor. Some scheduled and API-triggered runs during the incident did not start and may need to be re-triggered manually.

4. resolved Nov 04, 2026, 11:24 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:57 UTC. We have put measures in place to prevent a recurrence and the API has returned to normal. Please contact Support via email [email protected]: http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Nov 04, 2026, 09:37 AM UTC· resolved Nov 04, 2026, 11:50 AM UTC

1. investigating Nov 04, 2026, 09:37 AM UTC

   We're investigating an issue with git operations that is causing job runs to fail at the "Clone git repository" step and dbt Studio git actions to fail with "Permission denied (publickey)". This is impacting Scheduled Jobs and the IDE for projects that use a dbt-managed repository or connect to GitHub with a deploy key, across multi-tenant regions on AWS, Azure and GCP, anytime after 09:37 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Projects that connect through the native GitHub integration or use other git providers are not impacted and should be running as expected.

2. identified Nov 04, 2026, 10:07 AM UTC

   We've identified the cause as an incident at GitHub affecting Git operations (https://www.githubstatus.com/incidents/smtdswd1h2w4). Until GitHub resolves it, job runs and dbt Studio git actions may fail intermittently with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Accounts with repository caching enabled may see affected runs continue from the cached copy of the repository. We'll provide another update as GitHub makes progress.

3. monitoring Nov 04, 2026, 11:30 AM UTC

   GitHub has mitigated the issue, and we're no longer seeing these errors in job runs or dbt Studio. We're monitoring to confirm things stay stable. Job runs that failed with this error can be re-run.

4. resolved Nov 04, 2026, 11:50 AM UTC

   This incident has been resolved. Between 09:37 and 11:23 UTC, an incident at GitHub caused some job runs and dbt Studio git actions to fail with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Git operations have been stable since GitHub's fix. Any job run that failed with this error during that window can be re-run.

Read the full incident report →

Started Nov 03, 2026, 01:00 PM UTC· resolved Nov 03, 2026, 06:21 PM UTC

1. investigating Nov 03, 2026, 05:44 PM UTC

   We're investigating an issue with dbt Studio/IDE that is causing an error loop (restart dbt Studio). This is impacting projects running v1.6 and 1.7 in multi-tenant anytime after 1:00 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. investigating Nov 03, 2026, 05:50 PM UTC

   We're investigating reports of an issue with dbt Studio/IDE that is causing an error loop (dbt Studio prompts to be restarted, resulting in a loop). The currently identified scope of impact is Projects running on legacy v1.6 and 1.7 anytime after 1:00 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.

3. identified Nov 03, 2026, 06:04 PM UTC

   We have identified an issue with recent release that resulted in the dbt Studio restart loop on dbt Project Environments running on version 1.6 and 1.7. A rollback of this release is being implemented, and we will provide an update shortly.

4. monitoring Nov 03, 2026, 06:21 PM UTC

   We have deployed a fix for Studio IDE that was causing a restart loop on dbt Project Environments utilizing dbt versions 1.6 and 1.7. Studio IDE has returned to its normal state and we are continuing to monitor.

5. resolved Nov 03, 2026, 07:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning. We have put measures in place to prevent a recurrence and the Studio IDE has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Nov 03, 2026, 06:00 AM UTC· resolved Nov 03, 2026, 02:15 PM UTC

1. investigating Nov 03, 2026, 12:24 PM UTC

   We’re investigating an issue with the GitLab integration that is causing CI job commit statuses to not post back to GitLab. This is limited to existing projects with a GitLab integration whose project access token has expired and was not refreshed. It is impacting a small number of customers on the EU2 (Azure) region anytime after 06:00 UTC (01:00 AM Eastern) on 3 November. Affected customers may see missing pipeline statuses on merge requests, which can block merges that require passing statuses. New project configurations and new GitLab integrations are not impacted. There is currently no known workaround for affected existing projects, and reconnecting the repository does not resolve it. Our engineers are working on a resolution and we will provide updates approximately every 30 minutes, or as soon as new information becomes available. Please contact Support at [email protected]: mailto:[email protected] if you believe you are affected.

2. identified Nov 03, 2026, 01:24 PM UTC

   We have identified an issue with Gitlab project access tokens not being refreshed. Our engineers are working on a fix for this, and we will provide an update shortly.

3. resolved Nov 03, 2026, 02:15 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally . Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Oct 29, 2026, 04:32 PM UTC· resolved Oct 29, 2026, 05:50 PM UTC

1. investigating Oct 29, 2026, 04:32 PM UTC

   We’re investigating an issue with dbt Wizard that is causing requests that run SQL or Semantic Layer queries to fail with an error. This is impacting dbt Wizard in all multi-tenant regions anytime after 16:32 UTC (12:32 PM Eastern Time). The team is working on a resolution and we will provide updates as soon as new information becomes available. dbt platform jobs, and the Studio IDE are not impacted and should be running as expected.

2. identified Oct 29, 2026, 05:22 PM UTC

   We have identified an issue with dbt Wizard that resulted in failed parsing of semantic layer's QueryResult response. A fix is being implemented, and we will provide an update shortly.

3. monitoring Oct 29, 2026, 05:49 PM UTC

   We have deployed a fix for dbt wizard that was causing failed parsing of semantic layer's QueryResult response. dbt Wizard has returned to its normal state and we are continuing to monitor.

4. resolved Oct 29, 2026, 06:38 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [email protected]: http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Oct 28, 2026, 07:18 PM UTC· resolved Oct 28, 2026, 07:35 PM UTC

1. investigating Oct 28, 2026, 08:20 PM UTC

   We’re investigating an issue affecting dbt platform services. Customers may experience errors or slow responses when loading dbt Studio, running jobs, or using the API. The team is actively working on a resolution and we’ll share updates as soon as we know more.

2. monitoring Oct 28, 2026, 09:33 PM UTC

   We’ve deployed a fix and services are returning to normal. Customers should no longer see errors when loading dbt Studio, running jobs, or using the API. We’re continuing to monitor closely and will confirm here once the issue is fully resolved.

3. resolved Oct 29, 2026, 12:56 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform has returned to normal. Please contact Support via email at [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause

Read the full incident report →

Started Oct 22, 2026, 05:21 PM UTC· resolved Oct 23, 2026, 02:04 AM UTC

1. investigating Oct 22, 2026, 11:16 AM UTC

   We're investigating an issue with dbt invocations that is causing dbt deps failures. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Oct 22, 2026, 01:02 PM UTC

   We've identified an issue affecting dbt deps for projects in Studio and in some job runs, and our engineering team is rolling back the change we believe caused it. We will provide an update shortly.

3. monitoring Oct 22, 2026, 11:49 PM UTC

   We have deployed a fix and are continuing to monitor. Please contact us at [email protected] if you're still experiencing any issues and are unsure of the root cause.

4. resolved Oct 23, 2026, 05:27 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Oct 20, 2026, 06:55 AM UTC· resolved Oct 20, 2026, 12:27 PM UTC

1. investigating Oct 20, 2026, 06:55 AM UTC

   We are investigating an issue affecting a small number of dbt platform accounts in our EMEA region. Starting around 06:00 UTC, some job runs may be stuck in a “Running” state and can’t be cancelled. Stuck runs may count against your account’s run concurrency, so new runs may start late. Our engineering team is working on a fix. We will post another update within 60 minutes.

2. investigating Oct 20, 2026, 07:58 AM UTC

   Update posted at 07:56 UTC: We are continuing to investigate the issue causing delayed and stuck job runs in EMEA. Our engineering team is working to restore normal service. We will post another update within 60 minutes.

3. identified Oct 20, 2026, 08:21 AM UTC

   Update posted at 08:20 UTC: This issue is related to an ongoing incident with our cloud provider (GCP). We have cleared the runs that were stuck in “Running”. Until the provider incident is resolved, some run cancellations may still fail.

4. identified Oct 20, 2026, 10:21 AM UTC

   Update posted at 10:20 UTC: This issue is related to an ongoing incident with our cloud provider (GCP). Metadata ingestion in EMEA is now also affected, so some customers may see out-of-date information in dbt Explorer.

5. monitoring Oct 20, 2026, 12:27 PM UTC

   Update posted at 12:27 UTC: Services in EMEA are returning to normal. Job runs, run cancellations, notifications and metadata ingestion should now be working as expected. We are monitoring to confirm full recovery.

6. resolved Oct 20, 2026, 03:07 PM UTC

   Update posted at 15:05 UTC: This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.

Read the full incident report →

Started Oct 15, 2026, 01:09 PM UTC· resolved Oct 15, 2026, 04:10 PM UTC

1. investigating Oct 15, 2026, 01:09 PM UTC

   We’re investigating intermittent failures during dbt deps that prevent some dbt Cloud jobs from downloading and installing packages. Affected runs receive a response that is not a valid gzip archive. The issue has been observed across multiple customer accounts, packages, and regions. Our findings point to the package CDN delivery path, but the root cause is not yet confirmed. Engineering is investigating, and we’ll provide updates as we learn more.

2. investigating Oct 15, 2026, 01:56 PM UTC

   We’re continuing to investigate intermittent package download failures affecting dbt Cloud jobs. Some runs may fail during dbt deps with a “not a gzip file” error. Our Engineering team is investigating the issue, and we’ll share another update as more information becomes available.

3. monitoring Oct 15, 2026, 03:10 PM UTC

   The package download failures have stopped, and we’re monitoring the service to confirm the issue remains resolved. We’ll share another update if the symptoms return or as more information becomes available.

4. resolved Oct 15, 2026, 04:10 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 16:10 UTC. We have put measures in place to prevent a recurrence and dbt package installations have returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Oct 15, 2026, 12:51 AM UTC· resolved Oct 15, 2026, 01:20 AM UTC

1. resolved Oct 14, 2026, 04:51 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 00:51 AM UTC and 01:20 AM UTC some scheduled runs were cancelled . We have put measures in place to prevent a recurrence and the scheduled runs have returned to normal. If you are still experiencing issues, please contact us at [email protected]: mailto:[email protected].

Read the full incident report →

Started Oct 14, 2026, 12:14 PM UTC· resolved Oct 14, 2026, 12:15 PM UTC

1. investigating Oct 14, 2026, 10:30 AM UTC

   We’re investigating an issue with the Discovery API that caused sporadic errors for customers on prod-us-c3 from approximately 11:30 to 11:54 UTC on October 14. The team increased API gateway capacity, and the service has recovered. We’ll provide further updates if new information becomes available. Other components and regions are not impacted and are operating as expected.

2. resolved Oct 14, 2026, 10:54 AM UTC

   Resolved: The Discovery API issue affecting customers on prod-us-c3 has been resolved. Customers may have experienced sporadic errors between approximately 11:30 and 11:54 UTC on October 14. We increased API gateway capacity, and the service has recovered. Other components and regions were not affected.

Read the full incident report →

Started Oct 13, 2026, 10:04 PM UTC· resolved Oct 13, 2026, 11:24 PM UTC

1. investigating Oct 13, 2026, 10:28 PM UTC

   We're investigating an issue with dbt Platform that is causing the web application to not load. This is impacting logins and access the web application anytime after 6 PM Eastern. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Oct 13, 2026, 11:30 PM UTC

   We have identified an issue with the web application that has resulted in users being unable to access the dbt Platform. A fix is being implemented, and we will provide an update shortly.

3. monitoring Oct 14, 2026, 12:14 AM UTC

   We have deployed a fix for the dbt Platform that was causing access issues to the web application. We are seeing recovery and are continuing to monitor.

4. monitoring Oct 14, 2026, 12:50 AM UTC

   We are continuing to monitor the recovery following the fix we deployed for the dbt Platform. Access to the web application is improving, and we have not seen any new issues since the fix went out. If you are still experiencing issues on your end, please contact us at [email protected]: mailto:[email protected].

5. resolved Oct 14, 2026, 04:33 AM UTC

   This incident has been resolved. A fix was deployed for the dbt platform issue that was causing problems with access to the web application and the Admin API. Both are now operating normally. If you are still experiencing issues, please contact us at [email protected]: mailto:[email protected].

Read the full incident report →

Started Oct 08, 2026, 03:30 PM UTC· resolved Oct 08, 2026, 05:20 PM UTC

1. investigating Oct 08, 2026, 04:19 PM UTC

   We're investigating an issue with run artifact and log storage that is causing some job runs to complete without their logs and artifacts (such as manifest.json and run_results.json) being available. This is impacting some runs in the US Cell 3 (GCP) region anytime after 11:30 AM 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. Other dbt Cloud components are not impacted and should be running as expected. Job runs that use deferral and depend on artifacts from affected runs may fail.

2. monitoring Oct 08, 2026, 08:12 PM UTC

   GCP has completed mitigations on their end that were causing some job runs to complete without their logs and artifacts (such as manifest.json: https://manifest.json and run_results.json: https://run_results.json) being available. Scheduled jobs and metadata ingestion have returned to their normal state and we are continuing to monitor.

3. resolved Oct 09, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 1:20 PM Eastern on October 8. Between 11:30 AM and 1:20 PM Eastern, an issue with run artifact and log storage in US Cell 3 (GCP) resulted in some job runs completing without their logs and artifacts (such as manifest.json and run_results.json) being available, and some runs that use deferral failing. We have put measures in place to prevent a recurrence and run artifact and log storage has returned to normal. Please contact Support via email at [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Oct 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:16 AM UTC

1. identified Oct 07, 2026, 07:23 AM UTC

   We identified that a rate-limit change being previewed by GitLab was causing Git fetch and clone requests from the native GitLab integration to fail for some customers. This affected IDE pull and fetch operations and job run clone steps.

2. resolved Oct 07, 2026, 08:03 AM UTC

   A rate-limit change being previewed by GitLab caused failures for some customers using the native GitLab integration with GitLab.com: http://GitLab.com. This impacted IDE pull and fetch operations and job run clone steps between 2026-10-07 15:23 UTC and 2026-10-07 16:03 UTC. Git operations returned to normal at the end of that window, and we have since seen only isolated rate-limit errors. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Oct 02, 2026, 11:50 AM UTC· resolved Oct 02, 2026, 12:34 PM UTC

1. identified Oct 02, 2026, 11:05 AM UTC

   We're investigating an issue with Wizard CLI requests to Anthropic models that is causing increased errors for affected customers. This is impacting AI-assisted CLI functionality in our multi-tenant US production environment this morning. The team is working on a resolution and we will provide updates as soon as new information becomes available. All other dbt Cloud functionality is not impacted and should be running as expected.

2. identified Oct 02, 2026, 11:46 AM UTC

   We've identified the cause of the increased errors affecting Wizard CLI requests to Anthropic models — introduced during a recent inference endpoint upgrade. A fix has been prepared and is being deployed. We have not yet confirmed full recovery and will provide another update once that's verified. All other dbt Cloud functionality is not impacted and should be running as expected.

3. identified Oct 02, 2026, 11:50 AM UTC

   We've identified the cause of the increased errors affecting Wizard CLI requests to Anthropic models — introduced during a recent inference endpoint upgrade. A fix has been prepared and is being deployed. We have not yet confirmed full recovery and will provide another update once that's verified. All other dbt Cloud functionality is not impacted and should be running as expected.

4. resolved Oct 02, 2026, 12:34 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 12:30 UTC. We have put measures in place to prevent a recurrence and the system has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 30, 2026, 05:00 PM UTC· resolved Sep 30, 2026, 09:55 PM UTC

1. investigating Sep 30, 2026, 10:13 PM UTC

   We're investigating an issue with private packages due to the error "No matching Git URLs for private definition" that is causing the dbt deps run step to fail. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. monitoring Sep 30, 2026, 10:23 PM UTC

   We have deployed a fix and are beginning to see recovery in scheduled jobs. We will continue to monitor.

3. resolved Sep 30, 2026, 11:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 9:55 PM UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 02:09 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 01:27 PM UTC· resolved Sep 25, 2026, 12:43 AM UTC

1. investigating Sep 24, 2026, 01:27 PM UTC

   We're investigating an issue with BigQuery authentication that is causing some job runs to fail intermittently. This is impacting jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) while authenticating with Google Cloud, before any queries run. The team is working on a resolution and we will provide updates as soon as new information becomes available. In the meantime, rerunning a failed job or using Rerun from failure will usually succeed. Jobs using other BigQuery authentication methods, jobs on other data platforms, and dbt Studio are not impacted and should be running as expected.

2. investigating Sep 24, 2026, 03:19 PM UTC

   We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) during the token exchange with Google Cloud. We haven't found any changes on our side, and the error appears to originate on Google Cloud's side. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

3. investigating Sep 24, 2026, 05:32 PM UTC

   We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

4. investigating Sep 24, 2026, 06:41 PM UTC

   We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

5. monitoring Sep 24, 2026, 08:21 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

6. identified Sep 24, 2026, 08:59 PM UTC

   We have identified an issue with intermittent failures for jobs that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

7. monitoring Sep 25, 2026, 12:43 AM UTC

   The impacted component appears to be recovering, we will continue to monitor the performance. Please contact us at [email protected] with any questions or concerns.

8. resolved Sep 25, 2026, 01:50 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 23, 2026, 08:16 PM UTC· resolved Sep 23, 2026, 08:54 PM UTC

1. investigating Sep 23, 2026, 08:16 PM UTC

   We're investigating an issue with job runs that is causing intermittent failures on dbt deps. Affected runs failed with a certificate verification error while retrieving git-hosted packages. This is impacting job runs anytime after 20:16 UTC. The team is working on a resolution and we will provide updates at as soon as new information becomes available.

2. monitoring Sep 23, 2026, 08:54 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

3. resolved Sep 23, 2026, 11:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:39 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:30 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 10, 2026, 04:39 PM UTC· resolved Sep 10, 2026, 06:00 PM UTC

1. investigating Sep 10, 2026, 04:39 PM UTC

   We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly.

Read the full incident report →

Started Sep 10, 2026, 01:03 PM UTC· resolved Sep 10, 2026, 01:35 PM UTC

1. monitoring Sep 10, 2026, 02:28 PM UTC

   We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved.

2. resolved Sep 10, 2026, 04:45 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 10, 2026, 12:44 PM UTC· resolved Sep 10, 2026, 01:57 PM UTC

1. investigating Sep 10, 2026, 01:46 PM UTC

   We're currently investigating an increase in errors related to dbt MCP and Wizard. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. monitoring Sep 10, 2026, 02:08 PM UTC

   We have deployed a fix to mitigate the issue and are currently monitoring.

3. resolved Sep 10, 2026, 02:27 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 1:57 PM UTC

Read the full incident report →

Started Sep 10, 2026, 01:19 AM UTC· resolved Sep 10, 2026, 08:52 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →