- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 33of 100
What to do
Check whether you use dbt Cloud in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 6h it lasted.
Anything that failed between 2026-10-08 16:19 UTC and 2026-10-09 22:56 UTC may need a replay.Subscribe to dbt Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=dbt-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from dbt Cloud 3
- investigating
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.
provider
- monitoring
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.
provider
- resolved
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 [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-92bf77d93e
Is dbt Cloud still down?
No, this incident was resolved 2026-10-09 22:56 UTC. For dbt Cloud's live state, see https://down.guide/dbt-cloud.
How long did it last?
1d 6h, from 2026-10-08 16:19 UTC to 2026-10-09 22:56 UTC, by the times dbt Cloud posted.
What was affected?
dbt Cloud named in us.
What caused it?
dbt Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
dbt Cloud's official status page, https://status.getdbt.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.