Inngest outage, 28 April 2026

Increased function execution latency

Started
Resolved
28 Apr 2026, 22:48 UTC (after 3 h 37 min)
Impact
Minor

Last update from Inngest

Performance on all shards is back to normal levels. The degradation was caused by a change that aimed to improve concurrency metrics for Inngest accounts. The change, while out for a full 24 hours and fairly benign, began to compound and produced slowness for some queue shards within our system earlier today. We have reverted that change and are working to understand the performance impact of this change.

28 Apr 2026, 22:48 UTC

Is Inngest down now?

This page is the record of one past incident. For the live status, see Is Inngest down right now? - it reads the official status page every 2 minutes.

Other Inngest incidents

  1. Intermittent Degraded Function Execution

  2. Degraded function execution

  3. Degraded Function Execution

  4. Delayed observability of events

  5. Delays with function execution

  6. Degraded Function Execution

  7. Degraded Function Execution

  8. Connect Message Routing Delays - for Connect users only

All recorded Inngest incidents