Skip to content

Outage tracker

Inngest: incident history

The last 24 hours in detail, Inngest's declared incident record, and our regional check results beside it.

← Back to Inngest's check readings

We started checking Inngest on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

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.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Inngest's own status page declared. Below it, any public chatter we saw about Inngest and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Inngest's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Inngest in the last 24 hours, which is not evidence that nothing is wrong.
Inngest's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Inngest's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Inngest next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%447
US-West100.00%347
Europe100.00%316
Asia-Pacific99.48%193

Their declared record

Inngest's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Degraded Function ExecutionMinor incident
Nov 3, 2026, 8:21 AM UTC to Nov 3, 2026, 10:29 AM UTC (2h 7m)resolved
their latest update (Nov 3, 2026, 10:29 AM UTC): The incident is now resolved and the system is fully operational.
Intermittent Event API Connectivity IssuesMinor incident
Oct 20, 2026, 1:07 PM UTC to Oct 20, 2026, 1:20 PM UTC (13 min)resolved
their latest update (Oct 20, 2026, 1:20 PM UTC): The incident is now resolved and the system is fully operational.
Intermittent Degraded Function ExecutionMinor incident
Oct 11, 2026, 4:26 AM UTC to Oct 12, 2026, 2:26 AM UTC (22h)resolved
their latest update (Oct 12, 2026, 2:26 AM UTC): The system has been operationally stable for the last 22 hours
Degraded function executionMinor incident
Oct 10, 2026, 3:45 PM UTC to Oct 10, 2026, 5:38 PM UTC (1h 54m)resolved
their latest update (Oct 10, 2026, 5:38 PM UTC): The incident is now resolved and the system is full operational.
Degraded Function ExecutionMinor incident
Oct 9, 2026, 9:33 PM UTC to Oct 9, 2026, 11:29 PM UTC (1h 56m)resolved
their latest update (Oct 9, 2026, 11:29 PM UTC): One of our datacenter providers, Rackspace, had a network outage from 2:05 pm Pacific to 2:49 pm Pacific (21:05 UTC to 21:49 UTC). This resulted in degraded performance. We apologize for the inconvenience. We're going to keep monitoring and update if anything changes
Delayed observability of eventsMinor incident
Sep 26, 2026, 1:39 PM UTC to Sep 26, 2026, 1:58 PM UTC (19 min)resolved
their latest update (Sep 26, 2026, 1:58 PM UTC): The delay in events observability is now resolved and the system is fully operational.
Delays with function executionPartial outage
Sep 26, 2026, 6:01 AM UTC to Sep 26, 2026, 6:20 AM UTC (18 min)resolved
their latest update (Sep 26, 2026, 6:20 AM UTC): The system is full operational.
Degraded Function ExecutionPartial outage
Sep 18, 2026, 4:31 PM UTC to Sep 18, 2026, 9:17 PM UTC (4h 46m)resolved
their latest update (Sep 18, 2026, 9:17 PM UTC): The incident is now resolved and the system is full operational.
Degraded Function ExecutionPartial outage
Sep 4, 2026, 6:26 PM UTC to Sep 4, 2026, 7:10 PM UTC (43 min)resolved
their latest update (Sep 4, 2026, 7:10 PM UTC): The incident is now resolved and the system is full operational.
Connect Message Routing Delays - for Connect users onlyAll systems operational
Aug 26, 2026, 12:31 AM UTC to Aug 26, 2026, 12:31 AM UTC (0 min)resolved
their latest update (Aug 26, 2026, 12:31 AM UTC): Between August 26 00:31 to 01:13 UTC, a subset of customers using Inngest Connect experienced delayed and failed function runs due to an internal networking issue that disrupted connectivity between Connect services. We reverted the change and restored service. Although Connect …

Showing the 10 most recent of 26 incidents Inngest has declared in the history we hold.

These entries are Inngest's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Inngest's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.