Major impactResolvedDevOps

Inngest outage: Function execution down for a small subset of customers

Inngest reported this major-impact incident on its official status page on Jul 7, 2026, 07:57 UTC. It has since been resolved.

Right now Inngest is operational. Live Inngest status →

🔔 Get alerted when Inngest has issuesFree · email alerts · no credit card
Jul 7, 2026, 07:57 UTC
started
Jul 7, 2026, 06:45 UTC
resolved
—
duration
Major
impact

Timeline

updates from Inngest's status page ↗
  1. resolvedJul 7, 2026, 06:45 UTC

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

  2. monitoringJul 7, 2026, 06:33 UTC

    We’ve recovered the queue shard and it is now operational. We’re continuing to monitor it closely.

  3. identifiedJul 7, 2026, 06:16 UTC

    We’ve identified that one of the queue shards is down and are currently working to recover it. Only a subset of customers is affected.

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

← Previous: Support Portal Unavailable (Jun 19, 2026)Next: Degraded function execution performance (Jul 7, 2026) →
Inngest outage on Jul 7, 2026: Function execution down for a small subset of customers · APIStatus.watch