dbt Cloud incident

[US Cell 3 AWS] Incident: Discovery API Returning Stale Model Metadata

Minor Resolved View vendor source →
Started
Apr 07, 2026, 03:49 PM UTC
Resolved
Apr 07, 2026, 03:49 PM UTC
Duration
Detected by Pingoru
Apr 07, 2026, 03:49 PM UTC

Update timeline

  1. monitoring Apr 07, 2026, 03:46 PM UTC

    Status: Monitoring Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows. Affected components Metadata API (US Cell 3 AWS) (Degraded performance)

  2. resolved Apr 07, 2026, 03:49 PM UTC

    Status: Resolved Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata. Affected components Metadata API (US Cell 3 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