rewindex

Companiesdbt LabsIncidents

dbt Labs: Delayed and stuck job runs in EMEA

MinorStatus: resolvededitedStarted Resolved (8.2 h)6 updatesstatus.getdbt.com (opens in new tab)
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 from the archived incident (Sol). Check the timeline before relying on it.

Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents

dbt Labs’s incident blames Google Cloud as the cause. (hop 1, posted +48 min vs Google Cloud’s own post)

“…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…”

Swipe sideways to see the whole diagram.

Google Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed Google CloudJFrogWithin an hour4 vendors, 4 blamed Google CloudAiven, Northflank, Elastic Cloud, dbt Labs1 to 4 hours later4 vendors, 4 blamed Google CloudMongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse CloudLater2 vendors, 1 blamed Google CloudGrafana Cloud, Confluentdbt Labs (this incident)posted +48 min
Google Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed GoogleCloudJFrogWithin an hour4 vendors, 4 blamed GoogleCloudAiven, Northflank, Elastic Cloud,dbt Labs1 to 4 hours later4 vendors, 4 blamed GoogleCloudMongoDB Atlas, Sourcegraph,CockroachDB, ClickHouseCloudLater2 vendors, 1 blamed GoogleCloudGrafana Cloud, Confluentdbt Labs (this incident)posted +48 min
dbt Labs is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
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

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: 01K1EH8NN54JRJDH7XQ13T5JMF01K1EH8NN6PK7YBC7EV6QHG2WZ

Timeline of updates

  1. investigating

    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.

  2. investigating

    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.

  3. identified

    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.

  4. identifiedEdited

    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.

  5. monitoring

    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.

  6. resolved

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.getdbt.com (opens in new tab).

dbt Labs profileRecent dbt Labs incidentsMarkdownJSON