Delayed and stuck job runs in EMEA
**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.
The latest update from dbt Cloud.
State
Resolved
Started
13 d ago
2026-10-20 06:55 UTC
Lasted
8 h 11 min
until 2026-10-20 15:07 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
1 h 26 min 17%
Identified
4 h 6 min 50%
Monitoring
2 h 39 min 32%
Updates
Times in UTCAs posted by dbt Cloud
**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.
**Update posted at 12:27 UTC:** Services in EMEA are returning to normal. Job runs, run cancellations, notifications and metadata ingestion should now be working as expected. We are monitoring to confirm full recovery.
**Update posted at 10:20 UTC:** This issue is related to an ongoing incident with our cloud provider (GCP). Metadata ingestion in EMEA is now also affected, so some customers may see out-of-date information in dbt Explorer.
**Update posted at 08:20 UTC:** This issue is related to an ongoing incident with our cloud provider (GCP). We have cleared the runs that were stuck in “Running”. Until the provider incident is resolved, some run cancellations may still fail.
**Update posted at 07:56 UTC:** We are continuing to investigate the issue causing delayed and stuck job runs in EMEA. Our engineering team is working to restore normal service. We will post another update within 60 minutes.
We are investigating an issue affecting a small number of dbt platform accounts in our EMEA region. Starting around 06:00 UTC, some job runs may be stuck in a “Running” state and can’t be cancelled. Stuck runs may count against your account’s run concurrency, so new runs may start late. Our engineering team is working on a fix. We will post another update within 60 minutes.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
22
Days with an incident
24
Median duration
2 h 58 min
This incident
2.8× the median
Other dbt Cloud incidents
All incidentsdbt Cloud·dbt Wizard SQL execution failing
The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Degraded performance across dbt platform
The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform 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
dbt Cloud·dbt deps failures in dbt job runs and Studio
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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.
dbt Cloud·Intermittent dbt package download failures
The issue has been resolved, and all affected systems are now functioning normally as of 16:10 UTC. We have put measures in place to prevent a recurrence and dbt package installations have returned to normal. 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.
dbt Cloud·Unable to Access dbt Platform
This incident has been resolved. A fix was deployed for the dbt platform issue that was causing problems with access to the web application and the Admin API. Both are now operating normally. If you are still experiencing issues, please contact us at [support@getdbt.com](mailto:support@getdbt.com).
Follow dbt Cloud
Your coding agent knows when dbt Cloud is down, and tells you when a failure is theirs, not yours. You can also get dbt Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dbt" and tell me if dbt Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=dbt/feed subscribe https://outages.cc/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane