Inngest
Infrastructure. Source: Inngest status page.
- Incidents, last 90 days
- 14
- Median duration
- 31m
- p95 duration
- 22h
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 4 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 3 |
| A provider or third-party service this vendor depends on failed | 2 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 2 |
| Network, DNS, routing or connectivity failure | 2 |
| A code release introduced the failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Intermittent Event API Connectivity Issues
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
We've identified intermittent errors affecting the Event API due to connectivity issues with a downstream database provider. We're investigating the issue.
-
monitoring
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
The incident is now resolved and the system is fully operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Intermittent Degraded Function Execution
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are actively investigating an issue with intermittent degraded execution of a subset cron functions. We will provide further updates as we identify the cause and resolve the issue.
-
monitoring
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
The system has been operationally stable for the last 22 hours
Excerpts are shortened. Read the full incident on Inngest's status page.
Degraded function execution
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are actively investigating an issue with function. We will provider further updates as we identify the cause and resolve the issue.
-
monitoring
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
resolved
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Degraded Function Execution
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
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
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
Connectivity with our upstream infrastructure provider has been restored. We’re monitoring function execution to confirm recovery.
-
resolved
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
Excerpts are shortened. Read the full incident on Inngest's status page.
Delayed observability of events
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Events sent to Inngest are being accepted and processed for function execution normally, but are delayed for viewing by API or dashboard.
-
resolved
The delay in events observability is now resolved and the system is fully operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Delays with function execution
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
-
monitoring
We're monitoring the system to ensure the system is fully operational.
-
resolved
The system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Degraded Function Execution
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
-
monitoring
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
identified
Monitoring revealed additional issues, and we're actively working on further fixes to restore normal system operation.
-
monitoring
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
resolved
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Degraded Function Execution
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
-
investigating
We are actively investigating an issue with execution. Users may experience failed runs or delayed scheduling of runs from incoming events. We will provider further updates as we identify the cause and resolve the issue.
-
monitoring
We have identified the cause of the issue and we're monitoring the system as it is currently recovering. If users experienced any failed runs, you are able to replay failed runs in the UI. More info can be found here:
-
resolved
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Connect Message Routing Delays - for Connect users only
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
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...
Excerpts are shortened. Read the full incident on Inngest's status page.
Connect Message Routing Delays - for Connect users only
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
Between 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 Connect services. We reverted the change and restored...
Excerpts are shortened. Read the full incident on Inngest's status page.
We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
monitoring
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
resolved
Run history delay has caught up and the incident is now resolved.
Excerpts are shortened. Read the full incident on Inngest's status page.
Delays in Function Execution
Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
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
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
resolved
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Delayed function executions for a subset of customers
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
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
Execution latencies are back to normal across all customers, and the incident is now resolved.
Excerpts are shortened. Read the full incident on Inngest's status page.
Delayed function execution for 15 minutes
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
We observed temporary function execution delays for a period of 15 minutes as we performed emergency maintenance to manage disk capacity to several nodes.
Excerpts are shortened. Read the full incident on Inngest's status page.
Function processing delays
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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
We have identified the cause of the issue - the team has deployed a fix and is scaling to catch up on function delays.
-
monitoring
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...
-
resolved
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...
Excerpts are shortened. Read the full incident on Inngest's status page.
Metrics Data Delays
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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...
-
monitoring
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
Metrics 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
Excerpts are shortened. Read the full incident on Inngest's status page.
Latency and Execution Errors
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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
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...
-
resolved
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...
Excerpts are shortened. Read the full incident on Inngest's status page.
Issues Affecting Function Triggering from Events
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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...
-
monitoring
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
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
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Degraded function execution performance
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are actively investigating degraded function execution performance. We will provider further updates as we identify the cause and resolve the issue.
-
monitoring
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
resolved
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Function execution down for a small subset of customers
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
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
We’ve recovered the queue shard and it is now operational. We’re continuing to monitor it closely.
-
resolved
The incident is now resolved and the system is full operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Support Portal Unavailable
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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 [hello@inngest.com](mailto:hello@inngest.com).
-
resolved
The Support Portal is now available.
Excerpts are shortened. Read the full incident on Inngest's status page.
Downstream provider causing dashboard loading errors
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
We have identified the cause of the issue and are waiting for the downstream provider to implement their fix
-
monitoring
A fix has been deployed via Clerk and we're monitoring the system to ensure the system is fully operational.
-
resolved
The incident is now resolved.
Excerpts are shortened. Read the full incident on Inngest's status page.
Issues connecting to data store for events/runs/metrics pages
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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
A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
-
resolved
The previous incident with the observability database has beens resolved, but there is a separate incident with a downstream provider.
Excerpts are shortened. Read the full incident on Inngest's status page.
Elevated latency in runs and event details lookups
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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
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...
-
monitoring
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...
-
monitoring
We're monitoring the system to ensure the system is fully operational.
-
resolved
The incident is now resolved and the system is fully operational.
Excerpts are shortened. Read the full incident on Inngest's status page.
Increased function execution latency
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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
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...
-
resolved
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...
Excerpts are shortened. Read the full incident on Inngest's status page.