dbt Cloud Outage History

dbt Cloud experienced a 3-hour major incident caused by connectivity failures in an internal service, affecting users in GCP US and EMEA regions who encountered failures when starting dbt Studio sessions and delays when executing or cancelling deployment runs. The engineering team deployed a fix that restored both dbt Studio and scheduled jobs to normal operation.

dbt Cloud experienced a linting issue that generated Request Dependency Warnings for users. The problem affected the linting functionality within the platform for approximately 4.8 hours. A fix was deployed and the service was restored to normal operation with ongoing monitoring.

dbt Cloud's Studio IDE experienced failed runs for 9 minutes due to a technical issue. The problem prevented users from successfully executing runs within the Studio IDE interface. A fix was deployed and the service returned to normal operation.

dbt Cloud experienced a "Table Not Found in Schema" error affecting dbt Studio users running on dbt-fusion release v2.0.0-preview.143 starting March 2, 2026 at 1PM EST. Engineers initially rolled back dbt-fusion to a previous state as a temporary measure, then deployed a permanent fix after 28.9 hours. dbt Studio returned to normal operation following the fix deployment.

dbt Cloud experienced background errors affecting the Insights feature, though core Insights functionality remained operational throughout the incident. The issue was resolved after 41 minutes when the team deployed a fix that restored the service to normal operation.

GitLab experienced an outage causing 403 and 429 errors that impacted git operations in dbt Cloud. The incident lasted 1.6 hours and affected users' ability to perform git-related functions within the dbt Cloud service. GitLab shipped a fix to resolve the underlying outage.

dbt Cloud experienced a 20.3-hour incident where the compare changes step in advanced CI jobs failed for users of the Databricks adapter. The issue was identified as a problem with partial success handling in the advanced CI system. A fix was implemented to resolve the failing CI job step.

A transient DNS resolution error affected dbt Cloud CLI servers in the us-c1, us-c2, and us-c3 instances, impacting a small number of customers for 6 minutes between 10:00-11:00 AM EST. The DNS failure prevented affected users from properly connecting to the Cloud CLI service during this timeframe.