dbt Cloud Outage History

dbt Cloud experienced a CI outage affecting Azure DevOps integrations, causing missing Pull Requests tabs in CI jobs and displaying incorrect error messages about repository connectivity. The issue was caused by a recent change to the ADO integration and impacted CI functionality for approximately 2.8 hours. The team deployed a fix that restored CI triggers and the UI to normal operation.

The dbt Platform CLI State Selector experienced runtime errors when using version 2026.5.12+b52ab1d, affecting users' ability to properly execute state selection functionality. The issue was identified and a fix was deployed within 40 minutes, with the team continuing to monitor the resolution.

dbt Cloud experienced an issue where deployment jobs using BigQuery connections were failing to generate profiles and getting cancelled due to incorrect credential errors. The problem affected users' ability to run their BigQuery-connected deployment jobs, causing job cancellations with credential-related error messages. The underlying issue was identified and fixed after 1.3 hours of investigation.

dbt Cloud experienced degraded performance affecting dbt Copilot for 30 minutes, preventing some users from loading conversation history or using the dev agent in the AI Codegen API. The team identified the root cause and deployed a fix to resolve the issue.

dbt Studio experienced a major outage where users encountered blank pages when attempting to load the IDE interface. The incident lasted 2.5 hours and prevented users from accessing the development environment. The team identified the underlying issue and deployed a fix, restoring normal functionality to dbt Studio.

dbt Cloud experienced a 49-minute incident where the Audit Log service had delayed delivery, affecting audit logs in the US multi-cell AWS region and AU multi-tenant clusters. Audit events were queued during the outage and backfilled once resolved, with no data loss occurring. All other dbt Cloud services including jobs, scheduler, IDE, and API continued operating normally throughout the incident.

A Snowflake SSO profile generation issue in dbt Cloud caused the target.user variable to resolve to "None" in development environments for 3.7 hours. This affected users' ability to properly reference user context in their dbt development work. The issue was identified and resolved with a deployed fix, returning dbt Studio to normal operation.

dbt Cloud experienced a major service incident where jobs were failing during the dbt deps step due to an issue with private package authentication. The incident affected users' ability to run jobs that depended on private packages. The issue was identified and a fix was implemented, with the incident resolved within 6 minutes.

dbt Cloud's Semantic Layer experienced FlightSQL authentication errors where valid service tokens were failing to authenticate properly. The authentication failures prevented users from accessing Semantic Layer functionality through service token-based connections. A fix was deployed after 8 minutes, restoring the Semantic Layer to normal operation.

dbt Cloud experienced 429 "too many requests" errors affecting a small percentage of users for 44 minutes. The errors primarily impacted login, IDE, and CLI operations across the multi-tenant and multi-cell infrastructure. The incident was classified as minor due to the limited scope of affected users and requests.