Inngest incident: We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.

1. resolvedAug 20, 2026, 22:35 UTC

   Run history delay has caught up and the incident is now resolved.

2. monitoringAug 20, 2026, 21:44 UTC

   A fix has been deployed and we're monitoring the system to ensure the system is fully operational.

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.

• GitHub: Intermittent failures creating agent tasksCritical · Aug 20, 2026, 14:43 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Elasticsearch: Elevated Error Rates Affecting Managed OTLPMinor · Aug 20, 2026, 20:22 UTC
• LiveKit: Investigating reports of elevated egress & connector API errorsMinor · Aug 20, 2026, 21:10 UTC

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