dbt Cloud Outage History

dbt Cloud is up right now

dbt Cloud had 724 outages in the last 2 years totaling 20h 23m of downtime — averaging 30 incidents per month.

There were 724 dbt Cloud outages since January 27, 2026 totaling 20h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor October 2, 2026

[APAC AWS] Increased errors for Wizard CLI requests using Anthropic models

Detected by Pingoru
Oct 02, 2026, 11:50 AM UTC
Resolved
Oct 02, 2026, 12:34 PM UTC
Duration
44m
Timeline · 4 updates
  1. identified Oct 02, 2026, 11:05 AM UTC

    Status: Identified 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

    Status: Identified 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. Affected components Admin API (APAC AWS) (Degraded performance)

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

    Status: Identified 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. Affected components Admin API (APAC AWS) (Operational)

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

    Status: Resolved 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. Affected components Admin API (APAC AWS) (Operational)

Read the full incident report →

Minor October 2, 2026

[US AWS] Increased errors for Wizard CLI requests using Anthropic models

Detected by Pingoru
Oct 02, 2026, 11:50 AM UTC
Resolved
Oct 02, 2026, 12:34 PM UTC
Duration
44m
Timeline · 4 updates
  1. identified Oct 02, 2026, 11:05 AM UTC

    Status: Identified 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

    Status: Identified 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

    Status: Identified 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. Affected components IDE (US AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components IDE (US AWS) (Operational)

Read the full incident report →

Minor September 30, 2026

[EMEA AWS] dbt deps failures impacting private packages

Detected by Pingoru
Sep 30, 2026, 11:09 PM UTC
Resolved
Sep 30, 2026, 11:09 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 30, 2026, 10:13 PM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

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

    Status: Monitoring We have deployed a fix and are beginning to see recovery in scheduled jobs. We will continue to monitor. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components Scheduled Jobs (EMEA AWS) (Operational)

Read the full incident report →

Minor September 30, 2026

[US AWS] dbt deps failures impacting private packages

Detected by Pingoru
Sep 30, 2026, 11:09 PM UTC
Resolved
Sep 30, 2026, 11:09 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 30, 2026, 10:13 PM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (US AWS) (Degraded performance)

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

    Status: Monitoring We have deployed a fix and are beginning to see recovery in scheduled jobs. We will continue to monitor. Affected components Scheduled Jobs (US AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor September 25, 2026

[US Cell 1 AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 05:24 AM UTC
Resolved
Sep 25, 2026, 05:24 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (US Cell 1 AWS) (Degraded performance) Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance) IDE (US Cell 1 AWS) (Degraded performance)

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

    Status: Monitoring 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/. Affected components IDE (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational)

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

    Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components Scheduled Jobs (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor September 25, 2026

[US Cell 1 AZURE] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 05:24 AM UTC
Resolved
Sep 25, 2026, 05:24 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance) IDE (US Cell 1 AZURE) (Degraded performance)

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

    Status: Identified 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/. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance) IDE (US Cell 1 AZURE) (Degraded performance)

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

    Status: Monitoring 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/. Affected components IDE (US Cell 1 AZURE) (Operational) Scheduled Jobs (US Cell 1 AZURE) (Operational)

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

    Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components Scheduled Jobs (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor September 25, 2026

[US Cell 1 GCP] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 05:24 AM UTC
Resolved
Sep 25, 2026, 05:24 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (US Cell 1 GCP) (Degraded performance) Scheduled Jobs (US Cell 1 GCP) (Degraded performance)

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

    Status: Identified 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/. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance) IDE (US Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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/. Affected components IDE (US Cell 1 GCP) (Operational) Scheduled Jobs (US Cell 1 GCP) (Operational)

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

    Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components Scheduled Jobs (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor September 25, 2026

[US Cell 2 AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 05:24 AM UTC
Resolved
Sep 25, 2026, 05:24 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (US Cell 2 AWS) (Degraded performance) Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (US Cell 2 AWS) (Degraded performance) Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

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

    Status: Monitoring 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/. Affected components IDE (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational)

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

    Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components IDE (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor September 25, 2026

[US Cell 3 AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 05:24 AM UTC
Resolved
Sep 25, 2026, 05:24 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (US Cell 3 AWS) (Degraded performance) Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance) IDE (US Cell 3 AWS) (Degraded performance)

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

    Status: Monitoring 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/. Affected components IDE (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational)

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

    Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components IDE (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor September 25, 2026

[US Cell 4 AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 05:24 AM UTC
Resolved
Sep 25, 2026, 05:24 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance) IDE (US Cell 4 AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (US Cell 4 AWS) (Degraded performance) Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

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

    Status: Monitoring 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/. Affected components Scheduled Jobs (US Cell 4 AWS) (Operational) IDE (US Cell 4 AWS) (Operational)

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

    Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components Scheduled Jobs (US Cell 4 AWS) (Operational) IDE (US Cell 4 AWS) (Operational)

Read the full incident report →

Major September 25, 2026

[APAC AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (APAC AWS) (Degraded performance) Scheduled Jobs (APAC AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (APAC AWS) (Degraded performance) Scheduled Jobs (APAC AWS) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[AU2 Cell 1 Azure] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components Scheduled Jobs (AU2 Cell 1 Azure) (Degraded performance) IDE (AU2 Cell 1 Azure) (Degraded performance)

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

    Status: Identified 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/. Affected components Scheduled Jobs (AU2 Cell 1 Azure) (Degraded performance) IDE (AU2 Cell 1 Azure) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[EMEA AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (EMEA AWS) (Degraded performance) Scheduled Jobs (EMEA AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (EMEA AWS) (Degraded performance) Scheduled Jobs (EMEA AWS) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[EMEA Cell 1 AZURE] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance) Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)

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

    Status: Identified 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/. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance) IDE (EMEA Cell 1 AZURE) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[EU Cell 1 GCP] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (EU Cell 1 GCP) (Degraded performance) Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (EU Cell 1 GCP) (Degraded performance) Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[EU4 Cell 1 GCP] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance) IDE (EU4 Cell 1 GCP) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance) Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[JP Cell 1 AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (JP Cell 1 AWS) (Degraded performance) Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (JP Cell 1 AWS) (Degraded performance) Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[US AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components IDE (US AWS) (Degraded performance) Scheduled Jobs (US AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (US AWS) (Degraded performance) Scheduled Jobs (US AWS) (Degraded performance)

Read the full incident report →

Major September 25, 2026

[US5 Cell 1 AWS] GitLab service disruption

Detected by Pingoru
Sep 25, 2026, 12:19 AM UTC
Resolved
Sep 25, 2026, 02:25 AM UTC
Duration
2h 6m
Timeline · 2 updates
  1. investigating Sep 24, 2026, 11:56 PM UTC

    Status: Investigating 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/. Affected components Scheduled Jobs (US5 Cell 1 AWS) (Degraded performance) IDE (US5 Cell 1 AWS) (Degraded performance)

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

    Status: Identified 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/. Affected components IDE (US5 Cell 1 AWS) (Degraded performance) Scheduled Jobs (US5 Cell 1 AWS) (Degraded performance)

Read the full incident report →

Minor September 23, 2026

[US AWS] Intermittent dbt deps failures

Detected by Pingoru
Sep 23, 2026, 11:03 PM UTC
Resolved
Sep 23, 2026, 11:03 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 23, 2026, 08:16 PM UTC

    Status: Investigating 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. Affected components IDE (US AWS) (Degraded performance) Scheduled Jobs (US AWS) (Degraded performance) dbt platform CLI (US AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components IDE (US AWS) (Degraded performance) Scheduled Jobs (US AWS) (Degraded performance) dbt platform CLI (US AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components IDE (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) dbt platform CLI (US AWS) (Operational)

Read the full incident report →

Minor September 23, 2026

[US Cell 1 AWS] Intermittent dbt deps failures

Detected by Pingoru
Sep 23, 2026, 11:03 PM UTC
Resolved
Sep 23, 2026, 11:03 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 23, 2026, 08:16 PM UTC

    Status: Investigating 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. Affected components IDE (US Cell 1 AWS) (Degraded performance) Scheduled Jobs (US Cell 1 AWS) (Degraded performance) dbt platform CLI (US Cell 1 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components dbt platform CLI (US Cell 1 AWS) (Degraded performance) IDE (US Cell 1 AWS) (Degraded performance) Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components dbt platform CLI (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor September 23, 2026

[US Cell 1 GCP] Intermittent dbt deps failures

Detected by Pingoru
Sep 23, 2026, 11:03 PM UTC
Resolved
Sep 23, 2026, 11:03 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 23, 2026, 08:16 PM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance) dbt platform CLI (US Cell 1 GCP) (Degraded performance) IDE (US Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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. Affected components dbt platform CLI (US Cell 1 GCP) (Degraded performance) IDE (US Cell 1 GCP) (Degraded performance) Scheduled Jobs (US Cell 1 GCP) (Degraded performance)

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

    Status: Resolved 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. Affected components dbt platform CLI (US Cell 1 GCP) (Operational) Scheduled Jobs (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor September 23, 2026

[US Cell 2 AWS] Intermittent dbt deps failures

Detected by Pingoru
Sep 23, 2026, 11:03 PM UTC
Resolved
Sep 23, 2026, 11:03 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 23, 2026, 08:16 PM UTC

    Status: Investigating 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. Affected components IDE (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance) Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components IDE (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance) Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components IDE (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor September 23, 2026

[US Cell 3 AWS] Intermittent dbt deps failures

Detected by Pingoru
Sep 23, 2026, 11:03 PM UTC
Resolved
Sep 23, 2026, 11:03 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Sep 23, 2026, 08:16 PM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance) IDE (US Cell 3 AWS) (Degraded performance) dbt platform CLI (US Cell 3 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components IDE (US Cell 3 AWS) (Degraded performance) dbt platform CLI (US Cell 3 AWS) (Degraded performance) Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components dbt platform CLI (US Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →