Inngest reported this major-impact incident on its official status page on Mar 31, 2026, 11:14 UTC. It was resolved after 45 min.
Right now Inngest is operational. Live Inngest status →
The incident is now resolved and the system is full operational. During this incident step.fetch and step.ai.infer were failing due to a bug causing empty request bodies to be returned. The root cause was determined, the system was rolled back and a fix will be rolled out today.
A fix has been deployed for step.fetch and step.ai.infer and we're monitoring the system to ensure the system is fully operational. We continue to investigate the root cause.
We are actively investigating an issue with proxied requests via step.fetch or step.ai.infer. We will provider further updates as we identify the cause and resolve the issue. If you are not using these features your system should remain unaffected.
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