dbt Cloud Outage History

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 10, 2026, 11:26 PM UTC· resolved Aug 11, 2026, 01:30 AM UTC

1. investigating Aug 10, 2026, 11:26 PM UTC

   We're investigating an issue with our system's memory that is causing intermittent 500 or 502 errors with admin APIs requests. The team is working on a resolution and we will provide updates as soon as new information comes in.

2. monitoring Aug 11, 2026, 12:25 AM UTC

   We have deployed a fix for the memory issue that caused intermittent errors on admin APIs requests. Our admin API has returned to its normal state and we are continuing to monitor.

3. resolved Aug 11, 2026, 01:30 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 10 Aug 22:16 - 23:33 UTC an issue with our platform's memory resulted in intermittent 500 or 502 errors with admin APIs requests. We have put measures in place to prevent a recurrence and the admin API requests have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Aug 09, 2026, 04:25 PM UTC· resolved Aug 09, 2026, 05:43 PM UTC

1. investigating Aug 09, 2026, 04:25 PM 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.

2. investigating Aug 09, 2026, 04:32 PM 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.

3. monitoring Aug 09, 2026, 05:19 PM 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.

4. resolved Aug 09, 2026, 05:43 PM 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 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] "[email protected]": mailto:[email protected] if you continue to experience issues or have any follow-up questions

Read the full incident report →

Started Jul 29, 2026, 09:12 AM UTC· resolved Jul 29, 2026, 09:18 AM UTC

1. monitoring Jul 29, 2026, 09:12 AM UTC

   Reported at 08:21 UTC on 29 July 2026, we identified errors affecting AI Codegen (Wizard) for users in EMEA. A fix was deployed at 08:35 UTC, and we are currently monitoring — the system appears to be functioning normally. We apologise for any disruption this may have caused.

2. resolved Jul 29, 2026, 09:18 AM UTC

   Since our last update, we've continued to monitor AI Codegen (Wizard) in EMEA and error rates have remained normal. As of 09:16 UTC, 29 July 2026, this incident is resolved.

Read the full incident report →