Inngest incident

Delayed function run status

Minor Resolved View vendor source →

Inngest experienced a minor incident on February 9, 2026 affecting Observability, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 09, 2026, 07:51 AM UTC
Resolved
Feb 09, 2026, 07:51 AM UTC
Duration
Detected by Pingoru
Feb 09, 2026, 07:51 AM UTC

Affected components

Observability

Update timeline

  1. monitoring Feb 09, 2026, 06:58 AM UTC

    Status: Monitoring Run status and traces are currently delayed. The system has been scaled and is catching up. Function execution is unaffected. Affected components Observability (Degraded performance)

  2. monitoring Feb 09, 2026, 07:26 AM UTC

    Status: Monitoring The run trace and event history ingestion pipeline is nearly caught up. We further increased the capacity here to catch up on the backlog cause by very high load. Affected components Observability (Degraded performance)

  3. resolved Feb 09, 2026, 07:51 AM UTC

    Status: Resolved Runs, traces and events data are all caught up from their temporary backlog. The dashboard metrics are all being processed with no backlog. Affected components Observability (Operational)