Latency and Execution Errors

What to do

• Check whether your product depends on Inngest. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 12m it lasted.

  Anything that failed between 2026-07-16 11:45 UTC and 2026-07-16 12:57 UTC may need a replay.

• Subscribe to Inngest's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=inngest works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Inngest 3

1. investigatingJul 16, 2026, 9:45 AM 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.

   provider

2. monitoringJul 16, 2026, 12:35 PM 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.

   provider

3. resolvedJul 16, 2026, 12:57 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.