- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 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-07-07 07:57 UTC and 2026-07-07 06:45 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 that one of the queue shards is down and are currently working to recover it. Only a subset of customers is affected.
provider
- monitoring
We’ve recovered the queue shard and it is now operational. We’re continuing to monitor it closely.
provider
- resolved
The incident is now resolved and the system is full 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-2821f28dd8
Is Inngest still down?
No, this incident was resolved 2026-07-07 06:45 UTC. For Inngest's live state, see https://down.guide/inngest.
How long did it last?
0m, from 2026-07-07 07:57 UTC to 2026-07-07 06:45 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.