Inngest incident

Increased failures with step.fetch, step.ai.infer

Resolved after 44 minutes, on March 31, 2026.

resolved Mar 31, 2026, 11:59 AM UTC

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.

Started
Mar 31, 2026, 11:14 AM UTC
Resolved
Mar 31, 2026, 11:59 AM UTC
Duration
44m
Detected by Pingoru
Mar 31, 2026, 11:14 AM UTC

Update timeline

  1. investigating Mar 31, 2026, 11:14 AM UTC

    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.

  2. monitoring Mar 31, 2026, 11:45 AM UTC

    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.

  3. resolved Mar 31, 2026, 11:59 AM UTC

    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.

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.

Add your stack →