dbt Cloud incident
[EMEA Cell 1 AZURE] dbt invocation delays and failures
dbt Cloud experienced a minor incident on March 31, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Mar 31, 2026, 07:43 PM UTC
Status: Identified We have identified an issue with an internal service latency that resulted in delayed and failed dbt run invocations. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (EMEA Cell 1 AZURE) (Operational) Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance) IDE (EMEA Cell 1 AZURE) (Degraded performance) dbt Copilot (EMEA Cell 1 AZURE) (Operational) Admin API (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Degraded performance) Semantic Layer API (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational) Metadata Ingestion (EMEA Cell 1 AZURE) (Operational)
- resolved Mar 31, 2026, 08:09 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. Between 19:43 UTC and 20:09 UTC an issue with an internal service latency resulted in delays and failures of dbt invocations. We have put measures in place to prevent a recurrence and dbt invocations have returned to normal. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience delays and are unsure of the root cause. Affected components Metadata API (EMEA Cell 1 AZURE) (Operational) Admin API (EMEA Cell 1 AZURE) (Operational) Semantic Layer API (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational) dbt Copilot (EMEA Cell 1 AZURE) (Operational) IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational) Scheduled Jobs (EMEA Cell 1 AZURE) (Operational) Metadata Ingestion (EMEA Cell 1 AZURE) (Operational)