- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-10-20 14:16 UTC and 2026-10-20 13:20 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
- identified
We've identified intermittent errors affecting the Event API due to connectivity issues with a downstream database provider. We're investigating the issue.
provider
- monitoring
The connectivity issues with our downstream database provider have subsided, and the Event API is operating normally again. We're continuing to monitor the service while investigating the root cause.
provider
- resolved
The incident is now resolved and the system is fully operational.
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-a25bfd5bdf
Is Inngest still down?
No, this incident was resolved 2026-10-20 13:20 UTC. For Inngest's live state, see https://down.guide/inngest.
How long did it last?
0m, from 2026-10-20 14:16 UTC to 2026-10-20 13:20 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.