Inngest incident

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

Minor Resolved View vendor source →
Started
Mar 31, 2026, 11:59 AM UTC
Resolved
Mar 31, 2026, 11:59 AM UTC
Duration
Detected by Pingoru
Mar 31, 2026, 11:59 AM UTC

Update timeline

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

    Status: Investigating 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. Affected components API (REST and GraphQL) (Partial outage)

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

    Status: Monitoring 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. Affected components API (REST and GraphQL) (Operational)

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

    Status: Resolved 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. Affected components API (REST and GraphQL) (Operational)

Looking to track Inngest downtime and outages?

Pingoru polls Inngest's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Inngest reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Inngest alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Inngest for free

5 free monitors · No credit card required