Inngest experienced a minor incident on April 28, 2026 affecting Function execution, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 28, 2026, 07:11 PM UTC
Status: Investigating We are actively investigating increased function execution latency on a subset of customer shards starting around 5pm UTC. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Degraded performance)
- monitoring Apr 28, 2026, 10:27 PM UTC
Status: Monitoring Function execution latency has returned to normal for affected customers. Some customer shards were affected and we've pinpointed the cause of a slow degradation that compounded over time. We are working on adding new monitoring to catch performance regressions in this part of the system more quickly. Affected components Function execution (Operational)
- resolved Apr 28, 2026, 10:48 PM UTC
Status: Resolved 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. Affected components Function execution (Operational)