dbt Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:55 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...

2. investigating 2026-10-20 07:58 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 2026-10-20 08:21 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 2026-10-20 10:21 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 2026-10-20 12:27 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 2026-10-20 15:07 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...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 13:09 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...

2. investigating 2026-10-15 13:56 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...

3. monitoring 2026-10-15 15:10 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 2026-10-15 16:10 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...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-14 16:51 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...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-14 10:30 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...

2. resolved 2026-10-14 10:54 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...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 22:28 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...

2. identified 2026-10-13 23:30 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 2026-10-14 00:14 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 2026-10-14 00:50 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...

5. resolved 2026-10-14 04:33 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...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-07 07:23 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 2026-10-07 08:03 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....

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations..

1. investigating 2026-10-08 16:19 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...

2. monitoring 2026-10-08 20:12 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...

3. resolved 2026-10-09 22:56 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...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. identified 2026-10-02 11:05 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...

2. identified 2026-10-02 11:46 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...

3. identified 2026-10-02 11:50 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...

4. resolved 2026-10-02 12:34 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 [support@getdbt.com](http://support@getdbt.com...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-30 22:13 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 2026-09-30 22:23 UTC

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

3. resolved 2026-09-30 23:09 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 [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-24 23:56 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...

2. identified 2026-09-25 00:19 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...

3. monitoring 2026-09-25 02:09 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...

4. resolved 2026-09-25 05:24 UTC

   This incident has now been resolved. Please refer to GitLab for more details:

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS, Google Cloud.

1. investigating 2026-09-24 13:27 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...

2. investigating 2026-09-24 15:19 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...

3. investigating 2026-09-24 17:32 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...

4. investigating 2026-09-24 18:41 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...

5. monitoring 2026-09-24 20:21 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 2026-09-24 20:59 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...

7. monitoring 2026-09-25 00:43 UTC

   The impacted component appears to be recovering, we will continue to monitor the performance. Please contact us at support@getdbt.com with any questions or concerns.

8. resolved 2026-09-25 01:50 UTC

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

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 20:16 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...

2. monitoring 2026-09-23 20:54 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 2026-09-23 23:03 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 [support@getdbt.com](http://support@getdbt.com...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-18 23:31 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...

2. identified 2026-09-19 00:03 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 2026-09-19 03:20 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 [support@dbtlabs.com](mailto:support@dbtlabs.com "support@dbtlabs.com")...

4. identified 2026-09-19 05:31 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 [support@dbtlabs.com](mailto:support@dbtlabs.com) if you are unsure whether your...

5. identified 2026-09-19 13:00 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 [support@dbtlabs.com](mailto:support@dbtlabs.com) if you are unsure whether your...

6. monitoring 2026-09-19 13:30 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...

7. resolved 2026-09-19 14:30 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.

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-10 14:28 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...

2. resolved 2026-09-10 16:45 UTC

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

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 13:46 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 2026-09-10 14:08 UTC

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

3. resolved 2026-09-10 14:27 UTC

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

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 08:02 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...

2. identified 2026-09-10 08:14 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...

3. monitoring 2026-09-10 08:52 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...

4. resolved 2026-09-10 09:14 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

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-08 18:44 UTC

   We're investigating an issue with dbt Platform logins where users may have been logged out of active sessions and unable to login for a period of time. The service has recovered and we will continue to provide more information as it becomes available.

2. investigating 2026-09-08 18:51 UTC

   We're investigating an issue with dbt Platform logins where users may have been logged out of active sessions and unable to login for a period of time. The service has recovered and we will continue to provide more information as it becomes available.

3. identified 2026-09-08 19:44 UTC

   We have identified the cause of the current issue affecting login sessions. Our team is actively working on a fix. We will provide an update by 20:30 UTC

4. identified 2026-09-08 20:30 UTC

   Our team is still actively working on a fix. We will provide an update by 21:00 UTC

5. identified 2026-09-08 22:17 UTC

   Our team is still actively working on a fix to prevent sessions from terminating. We will provide an update by 23:00 UTC

6. monitoring 2026-09-08 22:54 UTC

   A fix has been deployed and we are monitoring the results. If you continue to experience issues, please contact support. Next update by 00:00 UTC or sooner if the status changes.

7. resolved 2026-09-08 23:16 UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience login issues and are unsure of the root cause.

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-09-04 14:20 UTC

   We're investigating an issue with the dbt Platform that is causing increased API errors in the US Cell 1 GCP instance impacting multiple components and access to dbt anytime after 10:00 AM Eastern. The team is working on a resolution and we will provide updates at approximately...

2. investigating 2026-09-04 14:40 UTC

   The dbt Platform in US Cell 1 GCP has recovered and all services are returning to normal state. We are continuing to investigate into the loss of availability of this instance and will provide updates as soon as more information becomes available.

3. investigating 2026-09-04 15:06 UTC

   We are continuing to investigate. All dbt services have recovered and should be running as expected. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") if you continue to experience issues.

4. resolved 2026-09-04 15:51 UTC

   The issue has been resolved, and all affected systems are functioning normally as of 11:30 AM Eastern. Between 9:50 AM Eastern and 10:30 AM Eastern an issue with the dbt Platform resulted in users being unable to access dbt and all services were down during this time. We have...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-03 13:24 UTC

   A configuration change affecting new account onboarding caused some customers signing up for a dbt State or dbt Wizard trial to be unable to create a project or proceed past the billing setup step. This impacted new trial sign-ups between 2026-09-03 11:48 UTC and 2026-09-03...

2. resolved 2026-09-03 13:25 UTC

   A configuration change affecting new account onboarding caused some customers signing up for a dbt State or dbt Wizard trial to be unable to create a project or proceed past the billing setup step. This impacted new trial sign-ups between 2026-09-03 11:48 UTC and 2026-09-03...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 11:05 UTC

   We're investigating delayed metadata processing affecting the Discovery (Metadata) API in our EU2 region. Customers hosted in EU2 may see newly ingested metadata take up to a few hours to become available, along with intermittent latency on Discovery API requests. Job...

2. identified 2026-09-02 15:01 UTC

   Our team has identified the contributing factor and is actively working on a resolution. We'll provide updates at approximately 30-minute intervals or as soon as new information becomes available.

3. identified 2026-09-02 16:29 UTC

   We are continuing to work on implementing a fix, and we will provide an update as soon as more information is available.

4. resolved 2026-09-02 17:57 UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 1:45 PM Eastern. Between 7:05 AM Eastern and 1:45 PM Eastern an issue with delayed metadata impacted the Discovery (Metadata) API in our EU2 region. We have put measures in place to prevent...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 15:58 UTC

   We're investigating an issue with the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email...

2. investigating 2026-08-26 16:14 UTC

   We have deployed a fix for the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional...

3. monitoring 2026-08-26 17:20 UTC

   Support emails from and to [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") have returned to its normal state and we are continuing to monitor.

4. resolved 2026-08-26 21:49 UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email resulted in customers receiving...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 04:23 UTC

   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...

2. monitoring 2026-08-25 04:46 UTC

   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 04:07 UTC. We are continuing to monitor and will provide another update once the issue is fully resolved.

3. resolved 2026-08-25 04:59 UTC

   This incident is resolved. Connections to Databricks warehouses in our AU region returned to normal operation at approximately August 25, 04:07 UTC, and we have seen no further errors since. Development sessions in the IDE and job runs that rely on Databricks credentials are...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-24 14:25 UTC

   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.

2. resolved 2026-08-24 15:00 UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 3:00PM UTC.

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-18 09:15 UTC

   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...

2. identified 2026-08-18 10:04 UTC

   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...

3. resolved 2026-08-18 11:19 UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple...

Excerpts are shortened. Read the full incident on dbt Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. investigating 2026-08-17 15:02 UTC

   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...

2. identified 2026-08-17 15:51 UTC

   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....

3. monitoring 2026-08-17 17:31 UTC

   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.

4. resolved 2026-08-17 21:21 UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform....

Excerpts are shortened. Read the full incident on dbt Cloud's status page.