Is Inngest Down?
Reachable from all 8 checked regions
Average response time: 207ms
Last checked · checks run every 6 hours
Official status page: https://status.inngest.com
A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Inngest fail from enough regions to rule out probe noise.
Inngest uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 40 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
40-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Inngest does
Inngest is a durable execution platform for background jobs and workflows. Applications send it events over an HTTP API, and Inngest runs the functions subscribed to those events with retries, concurrency limits, delays and multi-step flows. Teams use it instead of running their own queue and worker infrastructure, so scheduled work and asynchronous processing depend on it.
What an outage looks like
Background work stops happening while the application itself looks healthy. Inngest reports Event API separately from Function execution, so events can be accepted normally while the functions subscribed to them never run, leaving a backlog with no error anywhere in your code. Scheduled and delayed steps are the first thing users notice missing.
What to do about it
Read status.inngest.com, which publishes uptime per component next to the current state. If Function execution is the affected row, treat queued work as not yet run rather than lost, and avoid re-sending events, since duplicates will execute once the backlog clears. If only the Inngest Dashboard is affected, functions are still running and you have lost visibility rather than execution.
Is it down for everyone, or just you?
If this page says Inngest is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Inngest outage FAQ
My events are being accepted but nothing runs. Is Inngest down?
Will events sent during an Inngest outage be lost?
The Inngest dashboard will not load. Are my functions still running?
How do I tell an Inngest outage from a bug in my own function?
How we measure this
- We request Inngest's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Inngest publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Inngest goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring