Investigating Degraded Performance
Inngest reported degraded performance. Inngest investigated the problem, then reported recovery. Inngest resolved the incident, which lasted about 67 minutes.
State
Resolved
Started
Lasted
1 h 7 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 7 min 100%
Updates
Times in UTCAs posted by Inngest
The incident is now resolved and the system is full operational.
We have recovered from degraded performance that occurred 11:45 - 11:50 AM PT. We are continuing to investigate.
We are actively investigating degraded performance. We will provider further updates as we identify the cause and resolve the issue.
Inngest in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
11
Median duration
1 h 13 min
This incident
About the median
Other Inngest incidents
All incidentsInngest·Investigating System Degradation
This incident has been resolved. Thank you for your patience.
Inngest·Investigating System Degradation
Inngest reported a service degradation with an operational impact. Inngest identified the cause, deployed a fix, and now monitors the system. The incident is resolved and it lasted 127 minutes.
Inngest·Intermittent Degraded Function Execution
The system has been operationally stable for the last 22 hours
Inngest·Degraded function execution
The incident is now resolved and the system is full operational.
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
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.
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.
https://outages.live/feed.xml?providers=inngest/feed subscribe https://outages.live/feed.xml?providers=inngestFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane