dbt Cloud incident: Fusion Stable: BigQuery incremental model builds affected

1. resolvedAug 9, 2026, 17:43 UTC

   A regression in a recent Fusion build affecting the BigQuery adapter led to incremental models being rebuilt from empty instead of updating incrementally. This impacted some customers using BigQuery as their connected data warehouse with cross-project execution/target configurations between August 4, 2026 at 20:00 UTC and August 9, 2026 at 17:15 UTC. The affected Fusion build was rolled back to the last known-good version, and all affected systems are functioning normally. Please contact Support at [[email protected]](mailto:[email protected] "[email protected]") if you continue to experience issues or have any follow-up questions

2. monitoringAug 9, 2026, 17:19 UTC

   We've rolled back the affected Fusion builds and are monitoring the results. This issue affected customers using BigQuery as their connected data warehouse where the execution project differs from the target project. If you continue to experience issues, please contact support. Next update by 18:15 UTC or sooner if the status changes.

3. investigatingAug 9, 2026, 16:32 UTC

   We're investigating an issue where a very small percentage of job runs on dbt Fusion Stable were served the Fusion canary release track (v2.0.0-preview.206). Runs on this canary fusion version specifically affected incremental model builds. We are working on rolled back the affected build and are working to identify all impacted runs. We'll post an update by 17:32 UTC.

4. investigatingAug 9, 2026, 16:25 UTC

   We're investigating an issue where a very small percentage of job runs on dbt Fusion Stable were served the Fusion canary release track (v2.0.0-preview.206). Runs on this canary Fusion version specifically affected incremental model builds. We are working on rolling back the affected build and are working to identify all impacted runs. We'll post an update by 17:25 UTC.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in dbt Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Elasticsearch 9.5.0 contains a query-correctness defectMajor · Aug 5, 2026, 22:59 UTC
• Twilio: SMS Delivery Receipt Delays from Twilio to Liberty Mobile Puerto RicoMinor · Jul 29, 2026, 19:53 UTC
• Twilio: Voice Call Audio Quality Degradation From Network Subscribers to Twilio Colombia Landline NumbersMinor · Aug 6, 2026, 20:09 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio Long Codes to Multiple Networks in South AfricaMinor · Aug 8, 2026, 23:39 UTC
• Twilio: Voice Call Failures from Network Subscribers to a Subset of Twilio United States Phone NumbersMinor · Aug 9, 2026, 14:56 UTC

How often does dbt Cloud have incidents?

dbt Cloud reported 24 incidents in the last 90 days, 6 of them major or critical. A typical incident lasted 2h 4m. See dbt Cloud's uptime and incident history