Inngest Outage History
Inngest is up right nowPingoru has recorded 66 incidents for Inngest: 66 in the last 12 months and 14 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 7 | 61 of 720 (9%) |
| May 2026 | 3 | 21 of 744 (3%) |
| June 2026 | 1 | 2 of 720 (0%) |
| July 2026 | 6 | 99 of 744 (13%) |
| August 2026 | 6 | 5 of 744 (1%) |
| September 2026 | 4 | 6 of 720 (1%) |
| October 2026 | 4 | 27 of 583 (5%) |
Incidents, newest first
Minor October 20, 2026 Intermittent Event API Connectivity Issues 13m Event API
Started Oct 20, 2026, 01:07 PM UTC· resolved Oct 20, 2026, 01:20 PM UTC
- identified Oct 20, 2026, 01:07 PM UTC
We've identified intermittent errors affecting the Event API due to connectivity issues with a downstream database provider. We're investigating the issue.
- monitoring Oct 20, 2026, 01:12 PM UTC
The connectivity issues with our downstream database provider have subsided, and the Event API is operating normally again. We're continuing to monitor the service while investigating the root cause.
- resolved Oct 20, 2026, 01:20 PM UTC
The incident is now resolved and the system is fully operational.
Minor October 11, 2026 Intermittent Degraded Function Execution 22h Function execution
Started Oct 11, 2026, 04:26 AM UTC· resolved Oct 12, 2026, 02:26 AM UTC
- investigating Oct 11, 2026, 04:26 AM UTC
We are actively investigating an issue with intermittent degraded function. We will provider further updates as we identify the cause and resolve the issue.
- monitoring Oct 11, 2026, 05:30 AM UTC
Our new database connection poolers ran out of capacity today. We are rerouting traffic through multiple poolers that caused some latency spikes and delayed runs. We'll keep monitoring the system for any anomalies.
- resolved Oct 12, 2026, 02:26 AM UTC
The system has been operationally stable for the last 22 hours
Minor October 10, 2026 Degraded function execution 1h 53m Function execution
Started Oct 10, 2026, 03:45 PM UTC· resolved Oct 10, 2026, 05:38 PM UTC
- investigating Oct 10, 2026, 03:45 PM UTC
We are actively investigating an issue with function. We will provider further updates as we identify the cause and resolve the issue.
- monitoring Oct 10, 2026, 04:53 PM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
- resolved Oct 10, 2026, 05:38 PM UTC
The incident is now resolved and the system is full operational.
Minor October 9, 2026 Degraded Function Execution 2h 23m Function execution
Started Oct 09, 2026, 09:06 PM UTC· resolved Oct 09, 2026, 11:29 PM UTC
- investigating Oct 09, 2026, 09:06 PM UTC
We are actively investigating a network connectivity issue affecting function execution. We will provider further updates as we identify the cause and resolve the issue.
- investigating Oct 09, 2026, 09:51 PM UTC
We’re actively investigating a network connectivity issue with an upstream infrastructure provider that is affecting function execution. We will provider further updates as we identify the cause and resolve the issue
- monitoring Oct 09, 2026, 09:56 PM UTC
Connectivity with our upstream infrastructure provider has been restored. We’re monitoring function execution to confirm recovery.
- resolved Oct 09, 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
Minor September 26, 2026 Delayed observability of events 18m Observability
Started Sep 26, 2026, 01:39 PM UTC· resolved Sep 26, 2026, 01:58 PM UTC
- identified Sep 26, 2026, 01:39 PM UTC
Events sent to Inngest are being accepted and processed for function execution normally, but are delayed for viewing by API or dashboard.
- resolved Sep 26, 2026, 01:58 PM UTC
The delay in events observability is now resolved and the system is fully operational.
Minor September 26, 2026 Delays with function execution 18m Function execution
Started Sep 26, 2026, 06:01 AM UTC· resolved Sep 26, 2026, 06:20 AM UTC
- investigating Sep 26, 2026, 06:01 AM UTC
We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
- monitoring Sep 26, 2026, 06:10 AM UTC
We're monitoring the system to ensure the system is fully operational.
- resolved Sep 26, 2026, 06:20 AM UTC
The system is full operational.
Minor August 26, 2026 Connect Message Routing Delays - for Connect users only –
Started Aug 26, 2026, 12:31 AM UTC· resolved Aug 26, 2026, 12:31 AM UTC
- resolved 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 buffers worker responses, stalled internal API calls delayed acknowledgements and subsequent replies. In some cases, request forwarding failed even after a buffered response had been received. We fixed the root cause, improved Connect’s failure handling, and enhanced our internal observability so we can detect and respond more quickly to similar problems in the future. Affected customers should review failed Connect runs during the incident window and replay them after confirming that doing so is safe and idempotent.
Minor August 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. 50m Observability
Started Aug 20, 2026, 09:44 PM UTC· resolved Aug 20, 2026, 10:35 PM UTC
- monitoring Aug 20, 2026, 09:44 PM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
- resolved Aug 20, 2026, 10:35 PM UTC
Run history delay has caught up and the incident is now resolved.
Minor August 20, 2026 Delays in Function Execution 2h 4m Function execution
Started Aug 20, 2026, 01:00 PM UTC· resolved Aug 20, 2026, 03:04 PM UTC
- identified Aug 20, 2026, 01:00 PM UTC
We are actively investigating an issue with delays with function execution. We have a fix that has been released and are monitoring the system.
- monitoring Aug 20, 2026, 01:47 PM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
- resolved Aug 20, 2026, 03:04 PM UTC
The incident is now resolved and the system is full operational.
Minor August 19, 2026 Delayed function executions for a subset of customers 2h 31m Function execution
Started Aug 19, 2026, 02:10 AM UTC· resolved Aug 19, 2026, 04:41 AM UTC
- identified Aug 19, 2026, 02:10 AM UTC
We’re investigating execution slowness affecting a subset of customers, where steps may be delayed by a few seconds to a couple of minutes in the worst cases, caused by elevated memory usage on one of our shards.
- resolved Aug 19, 2026, 04:41 AM UTC
Execution latencies are back to normal across all customers, and the incident is now resolved.
Minor August 10, 2026 Delayed function execution for 15 minutes – Event API, Inngest Dashboard, Function execution, Observability
Started Aug 10, 2026, 10:30 PM UTC· resolved Aug 10, 2026, 10:30 PM UTC
- resolved Aug 10, 2026, 10:30 PM UTC
We observed temporary function execution delays for a period of 15 minutes as we performed emergency maintenance to manage disk capacity to several nodes.
Minor July 23, 2026 Function processing delays 1h 6m Function execution
Started Jul 23, 2026, 02:17 PM UTC· resolved Jul 23, 2026, 03:24 PM UTC
- investigating Jul 23, 2026, 02:17 PM UTC
We are actively investigating an issue with function execution that is leading to delays starting function runs after events are received. We will provider further updates as we identify the cause and resolve the issue.
- identified Jul 23, 2026, 02:41 PM UTC
We have identified the cause of the issue - the team has deployed a fix and is scaling to catch up on function delays.
- monitoring Jul 23, 2026, 03:06 PM UTC
New function execution has resumed and nearly caught up from the incurred backlog. Wait for event and cancel on handlers are still in a backlog and are catching up with processing. No events were dropped during this issue, all functions will be executed, but with delays. The root cause has been confirmd and changes are underway to prevent reoccurrence.
- resolved Jul 23, 2026, 03:24 PM UTC
The 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 topic. The consuming services which schedules new function runs was scaled out and began to consume the backlog. No events were dropped during this incident, all functions were scheduled, but with delays during this time window. No action is needed for manual recovery.
Minor July 16, 2026 Metrics Data Delays 1h 37m Inngest Dashboard, Observability
Started Jul 16, 2026, 05:52 PM UTC· resolved Jul 16, 2026, 07:29 PM UTC
- investigating Jul 16, 2026, 05:52 PM UTC
We are actively investigating an issue with our metrics service. Metrics displayed in the Inngest UI may not be up to date, but core platform functionality is unaffected and function execution is operating normally. We will provide further updates as we identify the cause and resolve the issue.
- monitoring Jul 16, 2026, 06:15 PM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational. We confirmed all executions were functioning as expected, so this only impacts the metrics on the dashboard.
- resolved Jul 16, 2026, 07:29 PM UTC
Metrics in the UI are now restored. Users may notice metrics data continue to be unavailable during the time of the incident.
Minor July 16, 2026 Latency and Execution Errors 3h 12m Function execution
Started Jul 16, 2026, 09:45 AM UTC· resolved Jul 16, 2026, 12:57 PM UTC
- investigating Jul 16, 2026, 09:45 AM UTC
We are actively investigating an issue with latency and execution errors. We will provider further updates as we identify the cause and resolve the issue.
- monitoring Jul 16, 2026, 12:35 PM UTC
We identified issues in the system and have deployed changes to mitigate the issues. Throughput has increased across the system. We continue to monitor latency as well as we expect it to reduce with the throughput increases. We are continuing to investigate for any additional issues that may have occurred.
- resolved Jul 16, 2026, 12:57 PM UTC
Throughput 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 and retries, causing a backlog in some parts of the system and some failed operations like checkpoints or signals. We are continuing a thorough post-mortem investigation to prevent reoccurrance.
Minor July 10, 2026 Issues Affecting Function Triggering from Events 3d 3h Function execution
Started Jul 10, 2026, 03:50 PM UTC· resolved Jul 13, 2026, 07:44 PM UTC
- investigating Jul 10, 2026, 03:50 PM UTC
We are investigating a partial outage affecting function triggering from incoming events. Some events may experience delays before triggering functions, or functions may not trigger as expected. Our team is actively investigating and will provide updates as more information becomes available.
- monitoring Jul 10, 2026, 05:41 PM UTC
We've made updates to the system, and function throughput is continuing to improve for users affected. The backlog is actively being processed, and we're closely monitoring recovery to ensure processing returns to normal.
- monitoring Jul 10, 2026, 06:23 PM UTC
We are continuing monitoring the system. Users affected by this incident may need to replay impacted events to ensure their associated functions are executed.
- resolved Jul 13, 2026, 07:44 PM UTC
The incident is now resolved and the system is full operational.
Minor July 7, 2026 Degraded function execution performance 16h 35m Function execution
Started Jul 07, 2026, 11:03 PM UTC· resolved Jul 08, 2026, 03:38 PM UTC
- investigating Jul 07, 2026, 11:03 PM UTC
We are actively investigating degraded function execution performance. We will provider further updates as we identify the cause and resolve the issue.
- monitoring Jul 08, 2026, 12:05 AM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
- resolved Jul 08, 2026, 03:38 PM UTC
The incident is now resolved and the system is full operational.
Minor July 7, 2026 Function execution down for a small subset of customers 29m Event API, Inngest Dashboard, Function execution, Observability
Started Jul 07, 2026, 06:16 AM UTC· resolved Jul 07, 2026, 06:45 AM UTC
- identified Jul 07, 2026, 06:16 AM UTC
We’ve identified that one of the queue shards is down and are currently working to recover it. Only a subset of customers is affected.
- monitoring Jul 07, 2026, 06:33 AM UTC
We’ve recovered the queue shard and it is now operational. We’re continuing to monitor it closely.
- resolved Jul 07, 2026, 06:45 AM UTC
The incident is now resolved and the system is full operational.
Minor June 19, 2026 Support Portal Unavailable 1h 33m Inngest Dashboard
Started Jun 19, 2026, 11:34 AM UTC· resolved Jun 19, 2026, 01:07 PM UTC
- investigating Jun 19, 2026, 11:34 AM UTC
We are currently investigating an issue causing the Inngest support portal to be unavailable. Our team is working on a fix, and in the meantime, any support questions can be emailed directly to [email protected]: mailto:[email protected].
- resolved Jun 19, 2026, 01:07 PM UTC
The Support Portal is now available.
Minor May 26, 2026 Downstream provider causing dashboard loading errors 2h 14m Inngest Dashboard
Started May 26, 2026, 09:31 PM UTC· resolved May 26, 2026, 11:46 PM UTC
- identified May 26, 2026, 09:31 PM UTC
We have identified the cause of the issue and are waiting for the downstream provider to implement their fix
- monitoring May 26, 2026, 10:07 PM UTC
A fix has been deployed via Clerk and we're monitoring the system to ensure the system is fully operational.
- resolved May 26, 2026, 11:46 PM UTC
The incident is now resolved.
Minor May 26, 2026 Issues connecting to data store for events/runs/metrics pages 12h 5m Inngest Dashboard
Started May 26, 2026, 09:26 AM UTC· resolved May 26, 2026, 09:32 PM UTC
- investigating May 26, 2026, 09:26 AM UTC
We are actively investigating an issue with our backing database for several of our dashboard pages. REST API and Function execution are not currently impacted.
- monitoring May 26, 2026, 10:51 AM UTC
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
- resolved May 26, 2026, 09:32 PM UTC
The previous incident with the observability database has beens resolved, but there is a separate incident with a downstream provider.
Minor May 21, 2026 Elevated latency in runs and event details lookups 6h 38m Inngest Dashboard
Started May 21, 2026, 01:42 PM UTC· resolved May 21, 2026, 08:20 PM UTC
- investigating May 21, 2026, 01:42 PM UTC
We are actively investigating elevated latency with the backing data store powering runs and event lookups for the dashboard at https://app.inngest.com/. We will provider further updates as we identify the cause and resolve the issue.
- investigating May 21, 2026, 02:21 PM UTC
We are actively investigating elevated latency with the backing data store powering runs and event lookups for the dashboard at https://app.inngest.com/ "https://app.inngest.com/.": https://app.inngest.com/. as well as our REST APIs. We will provider further updates as we identify the cause and resolve the issue.
- monitoring May 21, 2026, 07:40 PM UTC
A failover event in our data store provider changed the query plan behavior for some queries negatively and we had to adjust those plans to restore performance. Runs and event detail lookups are again performing normally. We're monitoring the system to ensure the system is fully operational.
- monitoring May 21, 2026, 07:59 PM UTC
We're monitoring the system to ensure the system is fully operational.
- resolved May 21, 2026, 08:20 PM UTC
The incident is now resolved and the system is fully operational.
Minor April 28, 2026 Increased function execution latency 3h 37m Function execution
Started Apr 28, 2026, 07:11 PM UTC· resolved Apr 28, 2026, 10:48 PM UTC
- investigating Apr 28, 2026, 07:11 PM UTC
We are actively investigating increased function execution latency on a subset of customer shards starting around 5pm UTC. We will provider further updates as we identify the cause and resolve the issue.
- monitoring Apr 28, 2026, 10:27 PM UTC
Function execution latency has returned to normal for affected customers. Some customer shards were affected and we've pinpointed the cause of a slow degradation that compounded over time. We are working on adding new monitoring to catch performance regressions in this part of the system more quickly.
- resolved Apr 28, 2026, 10:48 PM UTC
Performance 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, began to compound and produced slowness for some queue shards within our system earlier today. We have reverted that change and are working to understand the performance impact of this change.
Minor April 23, 2026 Degraded performance for REST API (runs/events data) 1d 21h
Started Apr 23, 2026, 08:06 PM UTC· resolved Apr 25, 2026, 06:04 PM UTC
- identified Apr 23, 2026, 08:06 PM UTC
We are currently experiencing degraded performance affecting a subset of users utilizing our REST API for retrieving runs and events data. Responses may be delayed or temporarily return incomplete data, with recent updates not appearing immediately. We have identified the cause of the issue. We're actively working on implementing a fix to resume normal operation of the REST API. Function execution is not affected and is working as expected.
- monitoring Apr 25, 2026, 01:54 AM UTC
We have fixed the issue affecting a subset of users utilizing our REST API for retrieving runs and events data for recent updates and are monitoring for issues with availability of historical data over the REST API.
- resolved Apr 25, 2026, 06:04 PM UTC
The incident is now resolved and the system is full operational.
Minor April 15, 2026 Delays in function run scheduling 11h 5m Function execution, Observability
Started Apr 15, 2026, 12:15 PM UTC· resolved Apr 15, 2026, 11:21 PM UTC
- investigating Apr 15, 2026, 12:15 PM UTC
We are actively investigating delays with function run scheduling for a subset of customers. We will provide further updates as we identify the cause and resolve the issue.
- identified Apr 15, 2026, 02:23 PM UTC
We have scaled up several resources across the system and to handle a large increase in scale within the system. Services are scaled up and we have also added new function state shards, but rollout of those new shards can take up to ~30m. We are also working on networking improvements to improve efficiency of the system with this significantly higher load.
- identified Apr 15, 2026, 02:49 PM UTC
We're deploying an in-memory optimization within the the part of the system the schedules new function runs. This optimization will alleviate pressure on underlying systems and increase throughput. The change will be rolled out momentarily. We're also working in parallel on a system change to create a dedicated service for processing for event batching which is the cause of the overall backlog on the system.
- identified Apr 15, 2026, 03:34 PM UTC
Changes have increase throughput, but not yet to typical levels. We are actively testing the new system change to decouple batch processing before enabling it for all accounts.
- identified Apr 15, 2026, 03:55 PM UTC
There is an increase in throughput since 15:37 UTC (~15 min ago). We are continuing to apply changes and prepare a larger change to decouple parts of the system. Event observability: Events may be delayed when appearing in the dashboard as the database ingestion for these events is also related to this part of the system that handles function scheduling. Events continue to be ingested and the Event API remains unaffected.
- identified Apr 15, 2026, 05:03 PM UTC
The system is consuming the event backlog as fast as possible, with an ETA of ~10-15 minutes until function scheduling is caught up. After function scheduling is caught up, function execution in your account may still be limited by your account concurrency or a given function's own flow control settings (concurrency, rate limit, etc.). We will continue to share more updates as soon as we can.
- identified Apr 15, 2026, 05:42 PM UTC
Function scheduled delays should be caught up. With events processed and new runs scheduled, your system my still see backlogs based on your function's flow control (e.g. concurrency) config and your account's concurrency. We still see backlogs in processing step.waitForEvent, step.invoke and cancelOn event expressions. We are continuing to work on this. We also are continuing our rollout of isolated batch processing as previously mentioned to further isolate parts of our system. EDIT - This was edited to include step.invoke as well for completeness.
- identified Apr 15, 2026, 06:36 PM UTC
Function execution scheduling and processing throughput is at normal levels. Async "pause" operations (step.waitForEvent, step.invoke, cancelOn) are severely backlogged which may cause delays in any of these operations from completing. This may cause issues with your function execution if you rely on them. The team is working on fixes and clear this backlog and fix the key issues. We do not yet have an ETA on resolving this specific issue.
- monitoring Apr 15, 2026, 08:03 PM UTC
The function run backlog for functions has been resolved as of 11:10AM PT. Batched functions and `step.waitForEvent` may face delays as the backlog continues to process.
- monitoring Apr 15, 2026, 09:34 PM UTC
Async "pause" operations (step.waitForEvent, step.invoke, cancelOn) should be running again at typical throughput. Event batching still has an backlog that we are actively working through. Status: • Function scheduling - Running as expected • Function execution - Running as expected, no queue backlogs • Async "pause" opts (waitForEvent, invoke, cancelOn) - Running as expected • Event batching - Significant backlog
- resolved Apr 15, 2026, 11:21 PM UTC
The incident is now resolved and the system is full operational.
Minor April 2, 2026 Dashboard down 42m Inngest Dashboard
Started Apr 02, 2026, 05:07 PM UTC· resolved Apr 02, 2026, 05:49 PM UTC
- identified Apr 02, 2026, 05:07 PM UTC
The Inngest dashboard is down due to an issue with our downstream provider. Vercel. We are working quickly to bring this back up
- identified Apr 02, 2026, 05:13 PM UTC
We area pushing a hotfix to the dashboard as recommended by Vercel's incident report. The rest of the Inngest system, function execution, API, etc. all remain functional.
- monitoring Apr 02, 2026, 05:15 PM UTC
A fix has been deployed and the dashboard is back online. We will continue to monitor the Vercel status page for any changes to the incident itself.
- resolved Apr 02, 2026, 05:49 PM UTC
The 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 accordingly. https://www.vercel-status.com/incidents/5r9bp5y8rql2