- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, us
- Down Index
- 33of 100
What to do
Check whether you use dbt Cloud in eu, 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 12h 23m it lasted.
Anything that failed between 2026-09-24 13:27 UTC and 2026-09-25 01:50 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 8
- investigating
We're investigating an issue with BigQuery authentication that is causing some job runs to fail intermittently. This is impacting jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) while authenticating with Google Cloud, before any queries run. The team is working on a resolution and we will provide updates as soon as new information becomes available. In the meantime, rerunning a failed job or using Rerun from failure will usually succeed. Jobs using other BigQuery authentication methods, jobs on other data platforms, and dbt Studio are not impacted and should be running as expected.
provider
- investigating
We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) during the token exchange with Google Cloud. We haven't found any changes on our side, and the error appears to originate on Google Cloud's side. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.
provider
- investigating
We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.
provider
- investigating
We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.
provider
- monitoring
We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.
provider
- identified
We have identified an issue with intermittent failures for jobs that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.
provider
- monitoring
The impacted component appears to be recovering, we will continue to monitor the performance. Please contact us at support@getdbt.com with any questions or concerns.
provider
- resolved
The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "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-c94d97b814
Is dbt Cloud still down?
No, this incident was resolved 2026-09-25 01:50 UTC. For dbt Cloud's live state, see https://down.guide/dbt-cloud.
How long did it last?
12h 23m, from 2026-09-24 13:27 UTC to 2026-09-25 01:50 UTC, by the times dbt Cloud posted.
What was affected?
dbt Cloud named in eu, 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.