Incident report for April 15, 2026 - Function scheduling and execution delays

On April 15, 2026, Inngest experienced a 19-hour system-wide incident that significantly delayed function scheduling and execution for all customers due to a spike in event volume overloading a shared state store shard. The root cause was identified as a bug in Inngest's SDK that led to abnormal event volume, combined with insufficient tenant isolation in the state store and event stream layers. Despite the delays, no data was lost, and all events were processed eventually. Inngest has implemented several immediate fixes, including adding state store shards, optimizing batch processing, and addressing the SDK bug. The company is prioritizing further improvements in tenant isolation and alert systems to prevent recurrence and has committed to better communication with customers during future incidents.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.