Inngest reported this major-impact incident on its official status page on Sep 4, 2026, 18:26 UTC. It was resolved after 43 min.
Right now Inngest is operational. Live Inngest status →
The incident is now resolved and the system is full operational.
We have identified the cause of the issue and we're monitoring the system as it is currently recovering. If users experienced any failed runs, you are able to replay failed runs in the UI. More info can be found here: <https://www.inngest.com/docs/platform/replay#how-to-create-a-new-replay>
We are actively investigating an issue with execution. Users may experience failed runs or delayed scheduling of runs from incoming events. We will provider further updates as we identify the cause and resolve the issue.
We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
Our 5-minute checks didn't record a change in Inngest's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Inngest reported 14 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 1h 12m. See Inngest's uptime and incident history