dbt Cloud reported this minor-impact incident on its official status page on Oct 15, 2026, 13:09 UTC. It was resolved after 3h.
Right now dbt Cloud is operational. Live dbt Cloud status →
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 [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.
The package download failures have stopped, and we’re monitoring the service to confirm the issue remains resolved. We’ll share another update if the symptoms return or as more information becomes available.
We’re continuing to investigate intermittent package download failures affecting dbt Cloud jobs. Some runs may fail during `dbt deps` with a “not a gzip file” error. Our Engineering team is investigating the issue, and we’ll share another update as more information becomes available.
We’re investigating intermittent failures during `dbt deps` that prevent some dbt Cloud jobs from downloading and installing packages. Affected runs receive a response that is not a valid gzip archive. The issue has been observed across multiple customer accounts, packages, and regions. Our findings point to the package CDN delivery path, but the root cause is not yet confirmed. Engineering is investigating, and we’ll provide updates as we learn more.
Overlapping incidents aren't necessarily related.
dbt Cloud reported 30 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 17m. See dbt Cloud's uptime and incident history