dbt Cloud Outage History

Started Oct 08, 2026, 04:19 PM UTC· resolved Oct 08, 2026, 05:53 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.

Read the full incident report →

Started Oct 08, 2026, 04:19 PM UTC· resolved Oct 09, 2026, 10:56 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

   We have deployed a fix for GCP network maintenance that was 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:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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 07, 2026, 07:23 AM UTC· resolved Oct 07, 2026, 08:03 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:05 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 Oct 02, 2026, 11:05 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, 10:13 PM UTC· resolved Sep 30, 2026, 11:09 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 30, 2026, 10:13 PM UTC· resolved Sep 30, 2026, 11:09 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 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 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/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 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/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 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/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 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/.

Read the full incident report →