Dash0 incident

Log ingest delay in us-west-2

Minor Resolved View vendor source →

Dash0 experienced a minor incident on July 8, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 08, 2026, 09:18 AM UTC
Resolved
Jul 08, 2026, 09:18 AM UTC
Duration
Detected by Pingoru
Jul 08, 2026, 09:18 AM UTC

Update timeline

  1. investigating Jul 06, 2026, 06:40 PM UTC

    Status: Investigating We are investigating delays in log ingestion in us-west-2 that started 18:35 CEST Affected components AWS - Oregon (us-west-2) (Partial outage)

  2. identified Jul 06, 2026, 07:03 PM UTC

    Status: Identified We have identified the problem and took first steps to mitigate. We are seeing log ingesting recover now Affected components AWS - Oregon (us-west-2) (Partial outage)

  3. monitoring Jul 06, 2026, 07:26 PM UTC

    Status: Monitoring Long ingestion is still recovering and catching up lag. The delay was related to a bug in Log AI. The feature has been disabled in us-west-2 until we have a full fix ready. Affected components AWS - Oregon (us-west-2) (Degraded performance)

  4. monitoring Jul 06, 2026, 08:04 PM UTC

    Status: Monitoring Log ingestion has fully recovered. Log AI remains disabled until further analysis. Affected components AWS - Oregon (us-west-2) (Operational)

  5. resolved Jul 08, 2026, 09:18 AM UTC

    Status: Resolved All outstanding fixes haven been shipped and all Log AI features are enabled again Affected components AWS - Oregon (us-west-2) (Operational)