Minor impactResolvedDevOps

Inngest incident: Latency and Execution Errors

Inngest reported this minor-impact incident on its official status page on Jul 16, 2026, 11:45 UTC. It was resolved after 1h 12m.

Right now Inngest is operational. Live Inngest status →

🔔 Get alerted when Inngest has issuesFree · email alerts · no credit card
Jul 16, 2026, 11:45 UTC
started
Jul 16, 2026, 12:57 UTC
resolved
1h 12m
duration
Minor
impact
  1. resolvedJul 16, 2026, 12:57 UTC

    Throughput and latency have recovered and the system should be fully operational again. The core issue is related to the part of the system that persists run state. Some operations experienced and increase in errors and retries, causing a backlog in some parts of the system and some failed operations like checkpoints or signals. We are continuing a thorough post-mortem investigation to prevent reoccurrance.

  2. monitoringJul 16, 2026, 12:35 UTC

    We identified issues in the system and have deployed changes to mitigate the issues. Throughput has increased across the system. We continue to monitor latency as well as we expect it to reduce with the throughput increases. We are continuing to investigate for any additional issues that may have occurred.

  3. investigatingJul 16, 2026, 09:45 UTC

    We are actively investigating an issue with latency and execution errors. We will provider further updates as we identify the cause and resolve the issue.

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 Jul 16, 2026: Latency and Execution Errors · APIStatus.watch