Inngest incident

Delayed function executions for a subset of customers

Inngest experienced a minor incident on August 19, 2026 affecting Function execution, lasting 2h 31m. The incident has been resolved; the full update timeline is below.

Started: Aug 19, 2026, 02:10 AM UTC
Resolved: Aug 19, 2026, 04:41 AM UTC
Duration: 2h 31m
Detected by Pingoru: Aug 19, 2026, 02:10 AM UTC

Affected components

Function execution

Update timeline

identified Aug 19, 2026, 02:10 AM UTC

Status: Identified We’re investigating execution slowness affecting a subset of customers, where steps may be delayed by a few seconds to a couple of minutes in the worst cases, caused by elevated memory usage on one of our shards. Affected components Function execution (Degraded performance)
resolved Aug 19, 2026, 04:41 AM UTC

Status: Resolved Execution latencies are back to normal across all customers, and the incident is now resolved. Affected components Function execution (Operational)