dbt Cloud reported this minor-impact incident on its official status page on Oct 8, 2026, 16:19 UTC. It was resolved after 1d 6h.
Right now dbt Cloud is operational. Live dbt Cloud status →
The issue has been resolved, and all affected systems are now functioning normally as of 1:20 PM Eastern on October 8. Between 11:30 AM and 1:20 PM Eastern, an issue with run artifact and log storage in US Cell 3 (GCP) resulted in some job runs completing without their logs and artifacts (such as manifest.json and run_results.json) being available, and some runs that use deferral failing. We have put measures in place to prevent a recurrence and run artifact and log storage has returned to normal. Please contact Support via email at [[email protected]](mailto:[email protected]) if you continue to experience delays and are unsure of the root cause.
GCP has completed mitigations on their end that were causing some job runs to complete without their logs and artifacts (such as [manifest.json](https://manifest.json) and [run_results.json](https://run_results.json)) being available. Scheduled jobs and metadata ingestion have returned to their normal state and we are continuing to monitor.
We're investigating an issue with run artifact and log storage that is causing some job runs to complete without their logs and artifacts (such as manifest.json and run_results.json) being available. This is impacting some runs in the US Cell 3 (GCP) region anytime after 11:30 AM Eastern. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Other dbt Cloud components are not impacted and should be running as expected. Job runs that use deferral and depend on artifacts from affected runs may fail.
Overlapping incidents aren't necessarily related.
dbt Cloud reported 30 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 37m. See dbt Cloud's uptime and incident history