# dbt Labs: Delayed and stuck job runs in EMEA

- Impact (vendor’s label): minor
- Status: resolved · edited after publishing
- Started: 2026-10-20 06:55 UTC · Resolved: 2026-10-20 15:07 UTC · Duration: 8.2 h
- Updates: 6 · Affected components: 01K1EH8NN54JRJDH7XQ13T5JMF, 01K1EH8NN6PK7YBC7EV6QHG2WZ
- [Vendor status page: https://status.getdbt.com/incidents/01M5C1G9A94RM2V1D864GCFHRP](https://status.getdbt.com/incidents/01M5C1G9A94RM2V1D864GCFHRP)
- [Company: dbt Labs](https://rewindex.com/company/dbt-labs.md)

## Part of an outage event

- [Google Cloud europe-west2 outage, Oct 20, 2026: 19 vendors, 19 incidents](https://rewindex.com/events/2026-10-20-google-cloud-europe-west2)
- This incident blames Google Cloud as the cause. (hop 1, posted +48 min vs Google Cloud’s own post)
- Evidence: “…as 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, delaye…”

```mermaid
flowchart LR
  root["Google Cloud europe-west2<br/>posted 06:08 UTC"]:::root
  before["Posted before Google Cloud did<br/>1 vendor, 1 blamed Google Cloud<br/>JFrog"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed Google Cloud<br/>Aiven, Northflank, Elastic Cloud, dbt Labs"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Google Cloud<br/>MongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 1 blamed Google Cloud<br/>Grafana Cloud, Confluent"]:::blames
  root --> later
  me["dbt Labs (this incident)<br/>posted +48 min"]:::me
  h1 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Summary

dbt Labs edited its EMEA incident update to say affected metadata ingestion may leave some customers seeing out-of-date information in dbt Explorer, replacing the reference to delayed or outdated Catalog metadata. The update still links the issue to an ongoing GCP incident. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-10-20 06:55 UTC: 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.
- **investigating** 2026-10-20 07:58 UTC: 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.
- **identified** 2026-10-20 08:21 UTC: 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.
- **identified** 2026-10-20 10:21 UTC _(edited after publishing)_: 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.
- **monitoring** 2026-10-20 12:27 UTC: 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.
- **resolved** 2026-10-20 15:07 UTC: 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.

## Rewindex changes for this incident

- 2026-10-20 08:03 UTC: [Incident updated: Delayed and stuck job runs in EMEA](https://rewindex.com/change/rdc63a8f536269f.md)
- 2026-10-20 08:23 UTC: [Incident updated: Delayed and stuck job runs in EMEA](https://rewindex.com/change/r9c19f36a59c272.md)
- 2026-10-20 10:23 UTC: [Incident updated: Delayed and stuck job runs in EMEA](https://rewindex.com/change/r71aff35efc72c5.md)
- 2026-10-20 10:33 UTC: [Incident silently edited: Delayed and stuck job runs in EMEA](https://rewindex.com/change/r45d742a70276e4.md)
- 2026-10-20 12:33 UTC: [Incident updated: Delayed and stuck job runs in EMEA](https://rewindex.com/change/rc0bd24e249be1e.md)
- 2026-10-20 15:13 UTC: [Incident updated: Delayed and stuck job runs in EMEA](https://rewindex.com/change/r72e87b7b3eb254.md)


---
Canonical: https://rewindex.com/company/dbt-labs/incidents/01M5C1G9A94RM2V1D864GCFHRP · Markdown: https://rewindex.com/company/dbt-labs/incidents/01M5C1G9A94RM2V1D864GCFHRP.md · JSON: https://rewindex.com/api/v1/companies/dbt-labs/incidents/01M5C1G9A94RM2V1D864GCFHRP · Generated 2026-10-21T00:27:19.422Z