Inngest experienced a minor incident on February 9, 2026 affecting Function execution, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 09, 2026, 03:31 PM UTC
Status: Investigating We are actively investigating delayed function execution. Affected components Function execution (Degraded performance)
- monitoring Feb 09, 2026, 03:52 PM UTC
Status: Monitoring We scaled up the infrastructure served the affected subset of customers, which will begin to reduce latency to normal levels. Affected components Function execution (Degraded performance)
- resolved Feb 09, 2026, 06:13 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
- identified Feb 09, 2026, 09:39 PM UTC
Status: Identified Function execution delays have returned for a subset of users. As we mitigated issues from earlier, some queue related slowness has returned affecting a subset of users running on certain shards. Affected components Function execution (Degraded performance)
- resolved Feb 09, 2026, 10:50 PM UTC
Status: Resolved After an extended monitoring period, function execution has returned to normal rates across all queue shards. During this issue, only a subset of users were affected on part of our infrastructure. Our infrastructure team is in the midst of rolling out additional system capacity going forward. Affected components Function execution (Operational)