dbt Cloud incident
[EMEA Cell 1 AZURE] Delayed metadata ingestion and Discovery API latency
dbt Cloud experienced a minor incident on September 2, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Sep 02, 2026, 11:05 AM UTC
Status: Investigating We're investigating delayed metadata processing affecting the Discovery (Metadata) API in our EU2 region. Customers hosted in EU2 may see newly ingested metadata take up to a few hours to become available, along with intermittent latency on Discovery API requests. Job orchestration, the dbt platform UI, and all other services are not impacted and are running as expected. This is limited to the EU2 region. Affected components Metadata Ingestion (EMEA Cell 1 AZURE) (Degraded performance)
- identified Sep 02, 2026, 03:01 PM UTC
Status: Identified Our team has identified the contributing factor and is actively working on a resolution. We'll provide updates at approximately 30-minute intervals or as soon as new information becomes available. Affected components Metadata Ingestion (EMEA Cell 1 AZURE) (Degraded performance)
- identified Sep 02, 2026, 04:29 PM UTC
Status: Identified We are continuing to work on implementing a fix, and we will provide an update as soon as more information is available. Affected components Metadata Ingestion (EMEA Cell 1 AZURE) (Degraded performance)
- resolved Sep 02, 2026, 05:57 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:45 PM Eastern. Between 7:05 AM Eastern and 1:45 PM Eastern an issue with delayed metadata impacted the Discovery (Metadata) API in our EU2 region. We have put measures in place to prevent a recurrence and metadata ingestion has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Metadata Ingestion (EMEA Cell 1 AZURE) (Operational)