rewindex

Changesdbt LabsDelayed and stuck job runs in EMEA

dbt Labs: Incident updated: Delayed and stuck job runs in EMEA

Incident updateNormal progress (rule, 100%)Changed status.getdbt.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

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

See the cascade chart and every vendor →

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.

What changed

Struck in red is what dbt Labs removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: identified
AddedUpdateidentified#2
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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.

History of this incident

TodayTuesday, October 20Tue, Oct 20

1 rewrite, 5 incident changes

All dbt Labs changesdbt Labs profileMarkdownJSON