- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 100
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 7m it lasted.
Anything that failed between 2026-07-23 14:17 UTC and 2026-07-23 15:24 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 4
- investigating
We are actively investigating an issue with function execution that is leading to delays starting function runs after events are received. We will provider further updates as we identify the cause and resolve the issue.
provider
- identified
We have identified the cause of the issue - the team has deployed a fix and is scaling to catch up on function delays.
provider
- monitoring
New function execution has resumed and nearly caught up from the incurred backlog. Wait for event and cancel on handlers are still in a backlog and are catching up with processing. No events were dropped during this issue, all functions will be executed, but with delays. The root cause has been confirmd and changes are underway to prevent reoccurrence.
provider
- resolved
The incident is now resolved and the system is full operational. Delays began around 14:03 UTC caused by an issue publishing to a new Kafka topic. Recovery began around 14:40 UTC as the team was able to isolate this topic. The consuming services which schedules new function runs was scaled out and began to consume the backlog. No events were dropped during this incident, all functions were scheduled, but with delays during this time window. No action is needed for manual recovery.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-84c8843ffc
Is Inngest still down?
No, this incident was resolved 2026-07-23 15:24 UTC. For Inngest's live state, see https://down.guide/inngest.
How long did it last?
1h 7m, from 2026-07-23 14:17 UTC to 2026-07-23 15:24 UTC, by the times Inngest posted.
What caused it?
Inngest hasn't published a root cause. If it does, it shows here.
Where does this come from?
Inngest's official status page, https://status.inngest.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.