Is Inngest Down?

No — Inngest is up

Inngest's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 209 ms

Right now

The verdict is the worse of these two. How we decide

Inngest's status page

status.inngest.com · read 4 minutes ago · checked every 3 minutes

Operational

Inngest's components, as its status page reports them
Component	Status
Function execution	Operational
Event API	Operational
API (REST and GraphQL)	Operational
Observability	Operational
Inngest Dashboard	Operational

Open their status page

FlareWarden checks

inngest.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 209 ms
Checked: 5 hours ago

By region

Ashburn reachable, 220 ms
Chicago reachable, 141 ms
Johannesburg reachable, 290 ms
London reachable, 141 ms
Los Angeles reachable, 140 ms
San Jose reachable, 321 ms
Singapore reachable, 230 ms
Tokyo reachable, 191 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	86 ms	2 ms	9 ms	213 ms
Chicago	56 ms	1 ms	24 ms	129 ms
Johannesburg	103 ms	1 ms	75 ms	252 ms
London	20 ms	3 ms	8 ms	130 ms
Los Angeles	42 ms	2 ms	26 ms	128 ms
San Jose	35 ms	4 ms	13 ms	313 ms
Singapore	181 ms	1 ms	8 ms	224 ms
Tokyo	109 ms	2 ms	9 ms	182 ms

We check that inngest.com loads, not every feature behind it. Test it yourself

History

Incidents Inngest reported

Since Oct 22, 15 days · from status.inngest.com

Incidents: 1
Major or critical: 0
Median to resolve: 2h 7m

Investigating System Degradation
Unrated · Nov 3
lasted 2h 7m

Inngest website availability

Measured by FlareWarden · inngest.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 225ms

Last 30 days

65-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of inngest.com from multiple regions every 6 hours. Inngest's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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.

Test it yourself

Related services

Vercel

AWS

Upstash

Sentry

Inngest outage FAQ

My events are being accepted but nothing runs. Is Inngest down?

That is the shape of a Function execution incident. Inngest reports the Event API separately, so it can keep returning success for events your application sends while the functions subscribed to them do not execute. Your code sees no error because the send succeeded. Check the Function execution row on status.inngest.com before debugging your own handlers.

Will events sent during an Inngest outage be lost?

Events accepted by the Event API are recorded, so an execution incident usually means delayed rather than dropped work. Inngest does not publish a guarantee covering every failure mode, so confirm against the incident's own updates rather than assuming. Avoid re-sending events during the window, because both copies will run once execution recovers.

The Inngest dashboard will not load. Are my functions still running?

Probably, and the two are reported separately. Inngest lists the Inngest Dashboard and Observability as components apart from Function execution, so you can lose the ability to inspect runs while the runs themselves continue normally. Treat it as lost visibility, and avoid triggering replays whose results you cannot see.

How do I tell an Inngest outage from a bug in my own function?

Compare the scope. A fault in your function affects that function and shows up in its run history with errors, while an Inngest incident stops or delays runs across every function at once, often with no run recorded at all. status.inngest.com publishes per-component uptime, so a dip on Function execution confirms the platform side.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Inngest itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Inngest goes down

We check Inngest every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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

Free plan available No credit card required