Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

dbt Cloud Outage History

Every past dbt Cloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 402 dbt Cloud outages since February 2022. The 123 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 29, 2026

May 2026: Compile button error in Studio IDE

Detected May 29, 2026 3:22 PM EDT · Resolved May 31, 2026 4:38 PM EDT · Duration 2 days

The dbt Cloud Studio IDE experienced an issue where the compile button failed with a "dbt9002: Failed to find compiled SQL" error on the Fusion-Latest environment, affecting users after 2 PM Eastern time. While the compile button was broken, inline compilation for builds and data preview continued to function normally. The team identified the root cause and deployed a fix after 49.3 hours of investigation and monitoring.

Minor May 28, 2026

May 2026: dbt1410 noisy warning logs

Detected May 28, 2026 1:36 PM EDT · Resolved May 28, 2026 5:25 PM EDT · Duration about 4 hours

dbt Cloud experienced incorrect logging that caused "Warn dbt1410: dbt State service was requested but no validated client is available for node" messages to appear during Scheduled Jobs execution after 12 PM Eastern. The warning logs did not cause actual errors and jobs continued to complete successfully, but created noise in the logging output. The team deployed a fix after 3.8 hours to resolve the incorrect logging issue.

Major May 26, 2026

May 2026: dbt Platform experiencing connectivity issues

Detected May 26, 2026 12:02 PM EDT · Resolved May 26, 2026 2:29 PM EDT · Duration about 2 hours

dbt Cloud experienced connectivity issues that affected all warehouse connections across the Studio IDE, CLI, and Jobs for 2.5 hours. The team identified the root cause and deployed a fix to resolve the connectivity problems. All affected services were restored and continued to be monitored following the resolution.

Minor May 24, 2026

May 2026: Error retrieving publications: the Cloud Artifacts API is currently unavailable. Please try again later.

Detected May 24, 2026 5:26 PM EDT · Resolved May 24, 2026 5:30 PM EDT · Duration 4 minutes

Between May 24, 8:52 pm – 8:55 pm UTC, a small number of dbt Cloud runs experienced failures when trying to retrieve publication artifacts due to the Cloud Artifacts API being unavailable. Users encountered the error "Error retrieving publications: the Cloud Artifacts API is currently unavailable. Please try again later." The issue was resolved after 4 minutes and the service returned to normal operation.

Minor May 22, 2026

May 2026: Elevated errors affecting Studio IDE sessions – US Azure region

Detected May 22, 2026 4:15 PM EDT · Resolved May 22, 2026 4:32 PM EDT · Duration 17 minutes

A CLI Server issue in dbt Cloud's US Multi-Cell Azure region caused elevated 5xx errors that prevented Studio IDE sessions from loading properly for 17 minutes. Job runs continued to operate normally and were not affected by the incident. The team identified the root cause with the CLI Server and deployed a fix, restoring the Studio IDE to normal functionality.

Minor May 22, 2026

May 2026: Snowflake jobs may time out on Latest release track

Detected May 22, 2026 12:59 PM EDT · Resolved May 25, 2026 5:07 PM EDT · Duration 3 days

A Snowflake adapter issue on dbt Cloud's Latest release track caused jobs to fail with connection timeouts when fetching large query result sets, with the connector timing out after 7 seconds while retrieving data from Snowflake's internal storage. The issue affected deployments using Snowflake on the Latest release track for 76.1 hours. The problem was resolved by deploying a fix to the Snowflake adapter, with users able to work around the issue by switching to the Compatible or Extended release tracks.

Minor May 22, 2026

May 2026: Billing Admin Page Requests Intermittently Failing

Detected May 22, 2026 12:22 PM EDT · Resolved May 22, 2026 5:04 PM EDT · Duration about 5 hours

The dbt Cloud Billing Admin Page experienced intermittent failures and timeouts with 5XX errors for 4.7 hours, affecting billing usage functionality across all instances. The issue was caused by a bug in a third-party dependency, which the vendor resolved with a deployed fix. Other dbt platform services including the IDE, scheduler, runs, and API remained unaffected throughout the incident.

Minor May 15, 2026

May 2026: dbt Platform CI Outage for AzureDevOps Integrations

Detected May 15, 2026 2:23 PM EDT · Resolved May 15, 2026 5:12 PM EDT · Duration about 3 hours

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.

Minor May 15, 2026

May 2026: dbt Platform CLI State Selector Failing

Detected May 15, 2026 12:24 PM EDT · Resolved May 15, 2026 1:04 PM EDT · Duration 40 minutes

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.

Minor May 12, 2026

May 2026: Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected May 12, 2026 3:30 AM EDT · Resolved May 12, 2026 4:51 AM EDT · Duration about 1 hour

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.