Resolved after 7 hours 19 minutes, affecting Function execution, on February 9, 2026.
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
Update timeline
- investigating Feb 09, 2026, 03:31 PM UTC
We are actively investigating delayed function execution.
- monitoring Feb 09, 2026, 03:52 PM UTC
We scaled up the infrastructure served the affected subset of customers, which will begin to reduce latency to normal levels.
- resolved Feb 09, 2026, 06:13 PM UTC
The incident is now resolved and the system is full operational.
- identified Feb 09, 2026, 09:39 PM UTC
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.
- resolved Feb 09, 2026, 10:50 PM UTC
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.
Your product runs on more than Inngest
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services