Inngest incident: Delayed function executions for a subset of customers

1. resolvedAug 19, 2026, 04:41 UTC

   Execution latencies are back to normal across all customers, and the incident is now resolved.

2. identifiedAug 19, 2026, 02:10 UTC

   We’re investigating execution slowness affecting a subset of customers, where steps may be delayed by a few seconds to a couple of minutes in the worst cases, caused by elevated memory usage on one of our shards.

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.

• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 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
• Resend: Contact webhook events are delayed in deliveryMinor · Aug 18, 2026, 19:53 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