outages.live
Live

Inngest

Inngest is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

8

Median duration

1 h 19 min

Longest incident

22 h

Components

5
Function execution Operational
90 days agoNo incidentsToday
Event API Operational
90 days agoNo incidentsToday
API (REST and GraphQL) Operational
90 days agoNo incidentsToday
Observability Operational
90 days agoNo incidentsToday
Inngest Dashboard Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 11, 2026

Duration22 h04:26 to 02:26Intermittent Degraded Function ExecutionDegraded

The system has been operationally stable for the last 22 hours

Oct 10, 2026

Duration1 h 54 min15:45 to 17:38Degraded function executionDegraded

The incident is now resolved and the system is full operational.

Oct 9, 2026

Duration1 h 56 min21:33 to 23:29Degraded Function ExecutionDegraded

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

Sep 26, 2026

Duration19 min13:39 to 13:58Delayed observability of eventsDegraded

The delay in events observability is now resolved and the system is fully operational.

Duration18 min06:01 to 06:20Delays with function executionPartial outage

The system is full operational.

Sep 18, 2026

Duration4 h 46 min16:31 to 21:17Degraded Function ExecutionPartial outage

The incident is now resolved and the system is full operational.

Sep 4, 2026

Duration43 min18:26 to 19:10Degraded Function ExecutionPartial outage

The incident is now resolved and the system is full operational.

Aug 20, 2026

Duration50 min21:44 to 22:35We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.Degraded

Run history delay has caught up and the incident is now resolved.

Duration1 h 19 min13:44 to 15:04Delays in Function ExecutionDegraded

The incident is now resolved and the system is full operational.

Follow Inngest

Your coding agent knows when Inngest is down, and tells you when a failure is theirs, not yours. You can also get Inngest incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "inngest" and tell me if Inngest has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=inngest
Slack
/feed subscribe https://outages.live/feed.xml?providers=inngest

Go from tracking outages to fixing production issues with Polylane.

Try Polylane