outages.live
Live
InngestIncident · 2026-11-03 08:21 UTC

Investigating System Degradation

NoticeOfficial update
0

Inngest reports a system degradation that affects operations. Inngest identified the cause and is working on a fix. The problem started at 08:21 UTC and continues.

State

Identified

Started

1 h ago

2026-11-03 08:21 UTC

Ongoing for

1 h 7 min

Worst impact

Notice

Timeline

2 updates
08:2108:3808:5509:1209:29
NoticeUpdate postedTimes in UTC

Investigating

53 min 79%

Identified

14 min 21%

Updates

Times in UTC

As posted by Inngest

Identified2026-11-03 09:15 UTC

We have identified the cause of the issue. We're actively working on implementing a fix to resume normal operation of the system.

Investigating2026-11-03 08:24 UTC

Our team is aware of and actively investigating a service degradation and will provide further details.

Inngest in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

9

Median duration

1 h 19 min

This incident

15% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 h
median 1 h 19 min
90 days agoToday

Other Inngest incidents

All incidents

Inngest·Intermittent Degraded Function Execution

The system has been operationally stable for the last 22 hours

Resolvedresolved 22 d ago

Inngest·Degraded function execution

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

Resolvedresolved 24 d ago

Inngest·Degraded Function Execution

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

Resolvedresolved 24 d ago

Inngest·Delayed observability of events

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

Resolvedresolved 38 d ago

Inngest·Delays with function execution

The system is full operational.

Resolvedresolved 38 d ago

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.cc/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.cc/feed.xml?providers=inngest
Slack
/feed subscribe https://outages.cc/feed.xml?providers=inngest

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane