dbt Cloud incident

[APAC AWS] Metadata API returning HTTP 500 errors

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

Update timeline

  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (APAC AWS) (Partial outage) Metadata API (APAC AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. 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 Web Application (APAC AWS) (Operational) Metadata API (APAC 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