dbt Labs: dbt deps failures in dbt job runs and Studio
The 10-22 15:58 UTC investigating update was archived with no visible wording change, still describing dbt deps failures affecting dbt invocations. dbt Labs said it was working on a resolution; no impact level, start time, duration, cause, or fix was provided.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: 01JBCBN080JGEJ8B0AWCAJK9RN01JBCBN1FAA7M1PF1A390EAREG01JBCBN2QJGPW8YNXDQY26T41V01JBCBN580QQW3WAG5DQTB2V3G01JBCBN6G24WEX8Y2DDGMQ2V7501JBCQQF8K02PQMM5WPGGVA2TC01JBCQQZ41M6BZCP649F5FFZYS01JBCQV9S7HYCF0Q81H55VWBGA01JBCR08X8CFND61GD5DW19N7801JH8R89TPYCY0Z9X6W4DDPH2G01JRKCJTBSJDQA2SECTV7GE3BT01K1EH8NN4BA0WB81Z7PKWHZGY01K4T29F336RNJ2A0NFNNNAM7X01KF46A8M6SCNZD8WWFNPB1QJA01KSMXDZMBBVGS7F0J1867BF8401KX12QA4CYG2K1N0XW50BRB3X
Timeline of updates
- investigating
We're investigating an issue with dbt invocations that is causing dbt deps failures. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified
We've identified an issue affecting dbt deps for projects in Studio and in some job runs, and our engineering team is rolling back the change we believe caused it. We will provide an update shortly.
- monitoring
We have deployed a fix and are continuing to monitor. Please contact us at support@getdbt.com if you're still experiencing any issues and are unsure of the root cause.
- resolved
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 "support@getdbt.com": http://support@getdbt.com (opens in new tab) if you continue to experience delays and are unsure of the root cause.
Changes Rewindex caught on this incident
- Incident updated: dbt deps failures in dbt job runs and Studio
- Incident silently edited: dbt deps failures in dbt job runs and Studio
- Incident silently edited: dbt deps failures in dbt job runs and Studio
- Incident silently edited: dbt deps failures in dbt job runs and Studio
- Incident updated: dbt deps failures in dbt job runs and Studio
- Incident updated: dbt deps failures in dbt job runs and Studio
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d3ab00f717b0ebd6…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a3df2973cd330a00…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8bf1398a20242337…Version 4 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
748e5f9f7795de43…Version 5 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0ac79765e6cf8712…Version 6 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a7332142d19a01ff…Version 7 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c8b60abdb579a0ab…
Impact, status and times are the vendor’s own, as last archived. View on status.getdbt.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by dbt Labs, started 2026-10-22 17:21 UTC, resolved after 12 h, 4 update(s); edited after publishing.
- Title
- dbt deps failures in dbt job runs and Studio
- Vendor
- dbt Labs
- Date
- URL
- https://rewindex.com/company/dbt-labs/incidents/01M5JA320K691B3002C81GSH5Z
dbt Labs profileRecent dbt Labs incidentsAll outages on October 22, 2026dbt Labs in October 2026MarkdownJSON