dbt Cloud incident

[US Cell 2 AWS] Cloud CLI server impacted by transient DNS resolution error

Minor Resolved View vendor source →
Started
Feb 24, 2026, 04:05 PM UTC
Resolved
Feb 24, 2026, 04:05 PM UTC
Duration
Detected by Pingoru
Feb 24, 2026, 04:05 PM UTC

Update timeline

  1. monitoring Feb 24, 2026, 04:02 PM UTC

    Status: Monitoring We're investigating an issue with cloud CLI that caused a transient DNS resolution failure for the Cloud CLI server for a small number of customer. This is impacted Cloud CLI servers were in (us-c1, us-c2, us-c3) instances anytime between 10:00 AM EST and between 11:00 AM EST. Affected components dbt platform CLI (US Cell 2 AWS) (Degraded performance)

  2. resolved Feb 24, 2026, 04:05 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of11:00 AM EST. Between 10:00 AM EST and 11:00 AM ESTan issue with cloud CLI resulted in a small number of customers requests failing. We have put measures in place to prevent a recurrence and the cloud CLI 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 dbt platform CLI (US Cell 2 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