Minor impactResolvedDevOps

Inngest incident: Elevated latency in runs and event details lookups

Inngest reported this minor-impact incident on its official status page on May 21, 2026, 13:42 UTC. It was resolved after 6h 38m.

Right now Inngest is operational. Live Inngest status →

🔔 Get alerted when Inngest has issuesFree · email alerts · no credit card
May 21, 2026, 13:42 UTC
started
May 21, 2026, 20:20 UTC
resolved
6h 38m
duration
Minor
impact
  1. resolvedMay 21, 2026, 20:20 UTC

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

  2. monitoringMay 21, 2026, 19:59 UTC

    We're monitoring the system to ensure the system is fully operational.

  3. monitoringMay 21, 2026, 19:40 UTC

    A failover event in our data store provider changed the query plan behavior for some queries negatively and we had to adjust those plans to restore performance. Runs and event detail lookups are again performing normally. We're monitoring the system to ensure the system is fully operational.

  4. investigatingMay 21, 2026, 14:21 UTC

    We are actively investigating elevated latency with the backing data store powering runs and event lookups for the dashboard at [https://app.inngest.com/](https://app.inngest.com/. "https://app.inngest.com/.") as well as our REST APIs. We will provider further updates as we identify the cause and resolve the issue.

  5. investigatingMay 21, 2026, 13:42 UTC

    We are actively investigating elevated latency with the backing data store powering runs and event lookups for the dashboard at https://app.inngest.com/. 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 May 21, 2026: Elevated latency in runs and event details lookups · APIStatus.watch