dbt Cloud incident

[EMEA AWS] Failed runs in Studio IDE

Minor Resolved View vendor source →
Started
Mar 03, 2026, 10:20 PM UTC
Resolved
Mar 03, 2026, 10:20 PM UTC
Duration
Detected by Pingoru
Mar 03, 2026, 10:20 PM UTC

Update timeline

  1. monitoring Mar 03, 2026, 10:12 PM UTC

    Status: Monitoring We have deployed a fix for Studio IDE that was causing failed runs. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components IDE (EMEA AWS) (Degraded performance)

  2. resolved Mar 03, 2026, 10:20 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 6:02 AM Eastern Between 4:31 AM Eastern and 6:02 AM Eastern an issue with Studio IDE resulted in failed runs. We have put measures in place to prevent a recurrence and the Studio IDE 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 IDE (EMEA AWS) (Operational)

Looking to track dbt Cloud downtime and outages?

Pingoru polls dbt Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when dbt Cloud reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track dbt Cloud alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring dbt Cloud for free

5 free monitors · No credit card required