Inngest: We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.

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 50m it lasted.
Anything that failed between 2026-08-20 21:44 UTC and 2026-08-20 22:35 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.

monitoringAug 20, 2026, 9:44 PM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
provider
resolvedAug 20, 2026, 10:35 PM UTC
Run history delay has caught up and the incident is now resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Inngest still down?

No, this incident was resolved 2026-08-20 22:35 UTC. For Inngest's live state, see https://down.guide/inngest.

How long did it last?

50m, from 2026-08-20 21:44 UTC to 2026-08-20 22:35 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.