Inngest Outage History
40 incidents recorded over the last 365 days, 40 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Inngest Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Degraded Function ExecutionThe incident is now resolved and the system is fully operational. | 2h 7m | Resolved |
| Oct 20, 2026 | Intermittent Event API Connectivity IssuesThe incident is now resolved and the system is fully operational. | -56 min | Resolved |
| Oct 11, 2026 | Intermittent Degraded Function ExecutionThe system has been operationally stable for the last 22 hours | 22h 0m | Resolved |
| Oct 10, 2026 | Degraded function executionThe incident is now resolved and the system is full operational. | 1h 53m | Resolved |
| Oct 9, 2026 | Degraded Function ExecutionOne 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… | 1h 55m | Resolved |
| Sep 26, 2026 | Delayed observability of eventsThe delay in events observability is now resolved and the system is fully operational. | 18 min | Resolved |
| Sep 26, 2026 | Delays with function executionThe system is full operational. | 18 min | Resolved |
| Sep 18, 2026 | Degraded Function ExecutionThe incident is now resolved and the system is full operational. | 4h 45m | Resolved |
| Sep 4, 2026 | Degraded Function ExecutionThe incident is now resolved and the system is full operational. | 43 min | Resolved |
| Aug 27, 2026 | Connect Message Routing Delays - for Connect users onlyBetween 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… | -2372 min | Resolved |
| Aug 25, 2026 | Connect Message Routing Delays - for Connect users onlyBetween August 24 at 23:38 UTC and August 25 at 00:08 UTC, a subset of customers using Inngest Connect experienced delayed and failed function runs due to an internal networking issue that disrupted connectivity between… | -227 min | Resolved |
| Aug 20, 2026 | We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.Run history delay has caught up and the incident is now resolved. | 50 min | Resolved |
| Aug 20, 2026 | Delays in Function ExecutionThe incident is now resolved and the system is full operational. | 1h 19m | Resolved |
| Aug 19, 2026 | Delayed function executions for a subset of customersExecution latencies are back to normal across all customers, and the incident is now resolved. | -13 min | Resolved |
| Aug 10, 2026 | Delayed function execution for 15 minutesWe observed temporary function execution delays for a period of 15 minutes as we performed emergency maintenance to manage disk capacity to several nodes. | -36 min | Resolved |
| Jul 23, 2026 | Function processing delaysThe incident is now resolved and the system is full operational. Delays began around 14:03 UTC caused by an issue publishing to a new Kafka topic. Recovery began around 14:40 UTC as the team was able to isolate this… | 1h 6m | Resolved |
| Jul 16, 2026 | Metrics Data DelaysMetrics in the UI are now restored. Users may notice metrics data continue to be unavailable during the time of the incident, from the timeframe 7/16/26 15:45 UTC until approximately 7/16/26 21:07 UTC | 1h 37m | Resolved |
| Jul 16, 2026 | Latency and Execution ErrorsThroughput and latency have recovered and the system should be fully operational again. The core issue is related to the part of the system that persists run state. Some operations experienced and increase in errors… | 1h 11m | Resolved |
| Jul 10, 2026 | Issues Affecting Function Triggering from EventsThe incident is now resolved and the system is full operational. | 74h 0m | Resolved |
| Jul 7, 2026 | Degraded function execution performanceThe incident is now resolved and the system is full operational. | 16h 35m | Resolved |
| Jul 7, 2026 | Function execution down for a small subset of customersThe incident is now resolved and the system is full operational. | -72 min | Resolved |
| Jun 19, 2026 | Support Portal UnavailableThe Support Portal is now available. | 1h 33m | Resolved |
| May 26, 2026 | Downstream provider causing dashboard loading errorsThe incident is now resolved. | 2h 14m | Resolved |
| May 26, 2026 | Issues connecting to data store for events/runs/metrics pagesThe previous incident with the observability database has beens resolved, but there is a separate incident with a downstream provider. | 12h 5m | Resolved |
| May 21, 2026 | Elevated latency in runs and event details lookupsThe incident is now resolved and the system is fully operational. | 6h 38m | Resolved |
| Apr 28, 2026 | Increased function execution latencyPerformance on all shards is back to normal levels. The degradation was caused by a change that aimed to improve concurrency metrics for Inngest accounts. The change, while out for a full 24 hours and fairly benign… | 3h 37m | Resolved |
| Apr 23, 2026 | Degraded performance for REST API (runs/events data)The incident is now resolved and the system is full operational. | 45h 58m | Resolved |
| Apr 15, 2026 | Delays in function run schedulingThe incident is now resolved and the system is full operational. | 11h 5m | Resolved |
| Apr 2, 2026 | Dashboard downThe incident is now resolved and the system is full operational. Related to the Vercel incident, we updated our dashboard to Node 22.x to solve the issue. We continue to monitor Vercel's incident and react… | 42 min | Resolved |
| Mar 31, 2026 | Increased failures with step.fetch, step.ai.inferThe incident is now resolved and the system is full operational. During this incident step.fetch and step.ai.infer were failing due to a bug causing empty request bodies to be returned. The root cause was determined… | 44 min | Resolved |
| Mar 26, 2026 | Function run scheduling delaysThe incident is now resolved and the system is full operational. This was related to an issue caused by the part of the system powering the debounce feature. The internal event backlog is fully caught up and the two… | 1h 3m | Resolved |
| Mar 26, 2026 | Degraded function execution performanceAfter an extended monitoring period, we are resolving this incident. The system is full operational. | 3h 42m | Resolved |
| Mar 10, 2026 | Reduced throughput on function executionThe networking fix has been applied and all systems are operational. We have identified the root cause. Function execution has returned to normal. Any backlogs incurred during the incident will be executed. | 36 min | Resolved |
| Mar 3, 2026 | Function execution delayedThe incident is now resolved and the system is full operational after monitoring. | 17 min | Resolved |
| Feb 26, 2026 | Elevated latency for function executionThe incident is now resolved and the system is full operational. | 53 min | Resolved |
| Feb 19, 2026 | Degraded dashboard availability The incident is now resolved and the system is full operational. | 2h 26m | Resolved |
| Feb 10, 2026 | Delays on some function executionThe incident is now resolved and the system is full operational. | 40 min | Resolved |
| Feb 9, 2026 | Delayed function executionAfter an extended monitoring period, function execution has returned to normal rates across all queue shards. During this issue, only a subset of users were affected on part of our infrastructure. Our infrastructure… | 2h 42m | Resolved |
| Feb 9, 2026 | Delayed function run statusRuns, traces and events data are all caught up from their temporary backlog. The dashboard metrics are all being processed with no backlog. | 53 min | Resolved |
| Feb 3, 2026 | Subset of customers experiencing function execution delaysSystem latency for function execution has returned to normal levels for the affected users. The incident has been resolved. The cause of the incident was due to increased load causing congestion. We applied changes to… | 4h 55m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Inngest incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Inngest Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Inngest acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Inngest outage in this window ran 3d 2h, against a mean recovery of 6h 52m. If you depend on Inngest in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.