dbt Cloud Outage History

dbt Cloud experienced authentication failures that prevented users from logging in, affecting the EMEA and AU regions for approximately 1.6 hours. The issue was caused by an outage with an upstream dependent system. The service was restored after error rates declined and login successes increased, with operational status confirmed through manual verification.

dbt Cloud experienced dependency resolution failures affecting scheduled jobs and Studio IDE sessions for customers using private packages with Azure DevOps, starting at 3:20 PM Eastern. The issue prevented jobs from running successfully and disrupted IDE functionality for the affected subset of users. The team deployed a fix after 2.5 hours, restoring normal operations for all impacted systems.

dbt Cloud experienced an issue where Job Run logs were unavailable, displaying "No logs found" messages for users. The problem was identified as an issue preventing Job Runs from pulling in debug logs. The team released a fix that resolved the missing logs issue for new job runs, while continuing to work on restoring logs for existing affected job runs.

dbt Cloud Studio experienced an issue where stale versions of files were displaying despite recent commits being made to the repository. The problem was identified as browser caching behaviors that prevented users from seeing their latest code changes in the Studio interface. The issue was resolved after 3.7 hours by deploying a fix, with users required to refresh their Studio sessions to apply the update.

dbt Cloud experienced a 27-minute outage where scheduled jobs failed to start in the EMEA Azure region beginning at 02:08 Eastern time. The team deployed a fix that restored normal operations, with all other components remaining unaffected throughout the incident.

A recent web application release caused job pages in dbt Cloud to display "Something went wrong" errors starting at 21:24 UTC on April 10, 2026. The issue prevented users from accessing job pages in the UI for approximately 1.5 hours. The team deployed a fix and the UI returned to normal operation.

dbt Cloud experienced a major outage in the US multi-tenant environment starting at 10:00 AM UTC, causing 502 Bad Gateway errors and complete inability to access the application, CLI, Semantic Layer, and AI features, with all dbt runs failing. The service team deployed a fix after 1.5 hours, restoring full functionality and returning the service to normal operation.

The dbt Cloud API experienced an outage that prevented users from logging in, returning 502 bad gateway errors. The incident lasted 9 minutes and affected user access to the dbt Cloud platform. The issue was resolved by the engineering team.

dbt Cloud experienced delays in artifact processing that caused stale metadata to display in the Catalog feature, affecting all Catalog functionality after 20:37 UTC on April 8th. The issue persisted for 48.5 hours before a fix was deployed that restored normal Catalog operations. The service team identified the root cause as artifact processing delays and successfully resolved it with continued monitoring.

The dbt Cloud Discovery API returned stale model metadata from April 6 at 3:00 PM ET to April 7 at 11:30 AM ET, causing outdated execution timestamps and metadata to display in dbt Explorer despite successful job runs. Users experienced incorrect "last updated" timestamps and stale execution data for their models. The issue was resolved by deploying a fix to the metadata ingestion pipeline, though affected models require re-running jobs to refresh their metadata to the correct state.