- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 22h it lasted.
Anything that failed between 2026-10-11 04:26 UTC and 2026-10-12 02:26 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
- investigating
We are actively investigating an issue with intermittent degraded execution of a subset cron functions. We will provide further updates as we identify the cause and resolve the issue.
provider
- monitoring
Our new database connection poolers ran out of capacity today. We are rerouting traffic through multiple poolers that caused some latency spikes and delayed runs. We'll keep monitoring the system for any anomalies.
provider
- resolved
The system has been operationally stable for the last 22 hours
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-a67366fe1e
Is Inngest still down?
No, this incident was resolved 2026-10-12 02:26 UTC. For Inngest's live state, see https://down.guide/inngest.
How long did it last?
22h, from 2026-10-11 04:26 UTC to 2026-10-12 02:26 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.