Minor impactResolvedDevOps

Inngest incident: Degraded performance for REST API (runs/events data)

Inngest reported this minor-impact incident on its official status page on Apr 23, 2026, 20:06 UTC. It was resolved after 1d 21h.

Right now Inngest is operational. Live Inngest status →

🔔 Get alerted when Inngest has issuesFree · email alerts · no credit card
Apr 23, 2026, 20:06 UTC
started
Apr 25, 2026, 18:04 UTC
resolved
1d 21h
duration
Minor
impact
  1. resolvedApr 25, 2026, 18:04 UTC

    The incident is now resolved and the system is full operational.

  2. monitoringApr 25, 2026, 01:54 UTC

    We have fixed the issue affecting a subset of users utilizing our REST API for retrieving runs and events data for recent updates and are monitoring for issues with availability of historical data over the REST API.

  3. identifiedApr 23, 2026, 20:06 UTC

    We are currently experiencing degraded performance affecting a subset of users utilizing our REST API for retrieving runs and events data. Responses may be delayed or temporarily return incomplete data, with recent updates not appearing immediately. We have identified the cause of the issue. We're actively working on implementing a fix to resume normal operation of the REST API. Function execution is not affected and is working as expected.

What APIStatus.watch saw

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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Inngest have incidents?

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

Inngest incident on Apr 23, 2026: Degraded performance for REST API (runs/events data) · APIStatus.watch