Skip to content

Outage tracker / Inngest / In the US

Is Inngest down in the US?

Vendor reports no incidentWhat Inngest reports

Inngest reports no incident on its status page.

As of the last successful poll, 2026-11-05 21:29 UTC.

Inngest's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Inngest at Nov 5, 2026, 9:33 PM UTC.

Over the last 24 hours we completed 253 checks from Ashburn and San Jose and 253 answered cleanly, 100.00% availability.

Of the 2 other regions we check Inngest from, all 2 read checks passing right now.

Email me when Inngest reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Inngest's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing111 checks in 24h, 100.00%

Last checked Nov 5, 2026, 9:33 PM UTC.

Inngest from Ashburn and San Jose over the last 30 days

Over the last 30 days, Inngest answered our Ashburn probe in 1,192 ms on average, and 1 check in 20 took longer than 1,647 ms.

Over the last 30 days, Inngest answered our San Jose probe in 1,412 ms on average, and 1 check in 20 took longer than 2,021 ms.

Ranked by average response time across the 4 cities we check Inngest from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 616 ms and Tokyo slowest at 2,390 ms.

From Ashburn and San Jose we ran 832 checks of Inngest in 4 days, and 832 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), Inngest was slowest around 2 PM, at 1,385 ms on average over the last 14 days, and quickest around 2 AM, at 668 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5226100.00%1,165 ms
Wed, Nov 4253100.00%1,230 ms
Tue, Nov 3248100.00%1,377 ms
Mon, Nov 2105100.00%1,490 ms

Inngest outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Inngest outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Inngest from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 98 checks
TokyoChecks passing100.00% of 61 checks

Other countries we check Inngest from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Inngest's public endpoints. They are not user reports, and they are not Inngest's own status page.

See Inngest's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Inngest has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter