- Detected by Pingoru
- Oct 11, 2026, 04:26 AM UTC
- Resolved
- Oct 12, 2026, 02:26 AM UTC
- Duration
- 22h
Affected: Function execution
Timeline · 3 updates
-
investigating Oct 11, 2026, 04:26 AM UTC
Status: Investigating We are actively investigating an issue with intermittent degraded function. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Degraded performance)
-
monitoring Oct 11, 2026, 05:30 AM UTC
Status: 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. Affected components Function execution (Degraded performance)
-
resolved Oct 12, 2026, 02:26 AM UTC
Status: Resolved The system has been operationally stable for the last 22 hours Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Oct 10, 2026, 03:45 PM UTC
- Resolved
- Oct 10, 2026, 05:38 PM UTC
- Duration
- 1h 53m
Affected: Function execution
Timeline · 3 updates
-
investigating Oct 10, 2026, 03:45 PM UTC
Status: Investigating We are actively investigating an issue with function. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Degraded performance)
-
monitoring Oct 10, 2026, 04:53 PM UTC
Status: Monitoring A fix has been deployed and we're monitoring the system to ensure the system is fully operational. Affected components Function execution (Degraded performance)
-
resolved Oct 10, 2026, 05:38 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2026, 09:06 PM UTC
- Resolved
- Oct 09, 2026, 11:29 PM UTC
- Duration
- 2h 23m
Affected: Function execution
Timeline · 4 updates
-
investigating Oct 09, 2026, 09:06 PM UTC
Status: 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. Affected components Function execution (Degraded performance)
-
investigating Oct 09, 2026, 09:51 PM UTC
Status: 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 Affected components Function execution (Degraded performance)
-
monitoring Oct 09, 2026, 09:56 PM UTC
Status: Monitoring Connectivity with our upstream infrastructure provider has been restored. We’re monitoring function execution to confirm recovery. Affected components Function execution (Degraded performance)
-
resolved Oct 09, 2026, 11:29 PM UTC
Status: 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 Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 26, 2026, 01:39 PM UTC
- Resolved
- Sep 26, 2026, 01:58 PM UTC
- Duration
- 18m
Affected: Observability
Timeline · 2 updates
-
identified Sep 26, 2026, 01:39 PM UTC
Status: Identified Events sent to Inngest are being accepted and processed for function execution normally, but are delayed for viewing by API or dashboard. Affected components Observability (Degraded performance)
-
resolved Sep 26, 2026, 01:58 PM UTC
Status: Resolved The delay in events observability is now resolved and the system is fully operational. Affected components Observability (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 26, 2026, 06:01 AM UTC
- Resolved
- Sep 26, 2026, 06:20 AM UTC
- Duration
- 18m
Affected: Function execution
Timeline · 3 updates
-
investigating Sep 26, 2026, 06:01 AM UTC
Status: Investigating We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Partial outage)
-
monitoring Sep 26, 2026, 06:10 AM UTC
Status: Monitoring We're monitoring the system to ensure the system is fully operational. Affected components Function execution (Partial outage)
-
resolved Sep 26, 2026, 06:20 AM UTC
Status: Resolved The system is full operational. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 12:31 AM UTC
- Resolved
- Aug 26, 2026, 12:31 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 26, 2026, 12:31 AM UTC
Status: 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 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.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 09:44 PM UTC
- Resolved
- Aug 20, 2026, 10:35 PM UTC
- Duration
- 50m
Affected: Observability
Timeline · 2 updates
-
monitoring Aug 20, 2026, 09:44 PM UTC
Status: Monitoring A fix has been deployed and we're monitoring the system to ensure the system is fully operational. Affected components Observability (Degraded performance)
-
resolved Aug 20, 2026, 10:35 PM UTC
Status: Resolved Run history delay has caught up and the incident is now resolved. Affected components Observability (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 01:00 PM UTC
- Resolved
- Aug 20, 2026, 03:04 PM UTC
- Duration
- 2h 4m
Affected: Function execution
Timeline · 3 updates
-
identified Aug 20, 2026, 01:00 PM UTC
Status: 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. Affected components Function execution (Degraded performance)
-
monitoring Aug 20, 2026, 01:47 PM UTC
Status: Monitoring A fix has been deployed and we're monitoring the system to ensure the system is fully operational. Affected components Function execution (Degraded performance)
-
resolved Aug 20, 2026, 03:04 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2026, 02:10 AM UTC
- Resolved
- Aug 19, 2026, 04:41 AM UTC
- Duration
- 2h 31m
Affected: Function execution
Timeline · 2 updates
-
identified Aug 19, 2026, 02:10 AM UTC
Status: 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. Affected components Function execution (Degraded performance)
-
resolved Aug 19, 2026, 04:41 AM UTC
Status: Resolved Execution latencies are back to normal across all customers, and the incident is now resolved. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2026, 10:30 PM UTC
- Resolved
- Aug 10, 2026, 10:30 PM UTC
- Duration
- —
Affected: Event APIInngest DashboardFunction executionObservability
Timeline · 1 update
-
resolved Aug 10, 2026, 10:30 PM UTC
Status: 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. Affected components API (REST and GraphQL) (Operational) Observability (Operational) Event API (Operational) Inngest Dashboard (Operational) Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 02:17 PM UTC
- Resolved
- Jul 23, 2026, 03:24 PM UTC
- Duration
- 1h 6m
Affected: Function execution
Timeline · 4 updates
-
investigating Jul 23, 2026, 02:17 PM UTC
Status: 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. Affected components Function execution (Partial outage)
-
identified Jul 23, 2026, 02:41 PM UTC
Status: Identified We have identified the cause of the issue - the team has deployed a fix and is scaling to catch up on function delays. Affected components Function execution (Partial outage)
-
monitoring Jul 23, 2026, 03:06 PM UTC
Status: 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 root cause has been confirmd and changes are underway to prevent reoccurrence. Affected components Function execution (Degraded performance)
-
resolved Jul 23, 2026, 03:24 PM UTC
Status: 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 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. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 05:52 PM UTC
- Resolved
- Jul 16, 2026, 07:29 PM UTC
- Duration
- 1h 37m
Affected: Inngest DashboardObservability
Timeline · 3 updates
-
investigating Jul 16, 2026, 05:52 PM UTC
Status: 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 resolve the issue. Affected components Observability (Partial outage)
-
monitoring Jul 16, 2026, 06:15 PM UTC
Status: 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. Affected components Inngest Dashboard (Degraded performance) Observability (Partial outage)
-
resolved Jul 16, 2026, 07:29 PM UTC
Status: Resolved Metrics in the UI are now restored. Users may notice metrics data continue to be unavailable during the time of the incident. Affected components Observability (Operational) Inngest Dashboard (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 09:45 AM UTC
- Resolved
- Jul 16, 2026, 12:57 PM UTC
- Duration
- 3h 12m
Affected: Function execution
Timeline · 3 updates
-
investigating Jul 16, 2026, 09:45 AM UTC
Status: 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. Affected components Function execution (Degraded performance)
-
monitoring Jul 16, 2026, 12:35 PM UTC
Status: 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 issues that may have occurred. Affected components Function execution (Degraded performance)
-
resolved Jul 16, 2026, 12:57 PM UTC
Status: 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 some failed operations like checkpoints or signals. We are continuing a thorough post-mortem investigation to prevent reoccurrance. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 03:50 PM UTC
- Resolved
- Jul 13, 2026, 07:44 PM UTC
- Duration
- 3d 3h
Affected: Function execution
Timeline · 4 updates
-
investigating Jul 10, 2026, 03:50 PM UTC
Status: 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 becomes available. Affected components Function execution (Partial outage)
-
monitoring Jul 10, 2026, 05:41 PM UTC
Status: 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. Affected components Function execution (Operational)
-
monitoring Jul 10, 2026, 06:23 PM UTC
Status: 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. Affected components Function execution (Operational)
-
resolved Jul 13, 2026, 07:44 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 11:03 PM UTC
- Resolved
- Jul 08, 2026, 03:38 PM UTC
- Duration
- 16h 35m
Affected: Function execution
Timeline · 3 updates
-
investigating Jul 07, 2026, 11:03 PM UTC
Status: Investigating We are actively investigating degraded function execution performance. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Partial outage)
-
monitoring Jul 08, 2026, 12:05 AM UTC
Status: Monitoring A fix has been deployed and we're monitoring the system to ensure the system is fully operational. Affected components Function execution (Partial outage)
-
resolved Jul 08, 2026, 03:38 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 06:16 AM UTC
- Resolved
- Jul 07, 2026, 06:45 AM UTC
- Duration
- 29m
Affected: Event APIInngest DashboardFunction executionObservability
Timeline · 3 updates
-
identified Jul 07, 2026, 06:16 AM UTC
Status: 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. Affected components Function execution (Partial outage) API (REST and GraphQL) (Operational) Observability (Operational) Event API (Operational) Inngest Dashboard (Operational)
-
monitoring Jul 07, 2026, 06:33 AM UTC
Status: Monitoring We’ve recovered the queue shard and it is now operational. We’re continuing to monitor it closely. Affected components Inngest Dashboard (Operational) Function execution (Operational) API (REST and GraphQL) (Operational) Observability (Operational) Event API (Operational)
-
resolved Jul 07, 2026, 06:45 AM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Event API (Operational) Inngest Dashboard (Operational) Function execution (Operational) API (REST and GraphQL) (Operational) Observability (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 11:34 AM UTC
- Resolved
- Jun 19, 2026, 01:07 PM UTC
- Duration
- 1h 33m
Affected: Inngest Dashboard
Timeline · 2 updates
-
investigating Jun 19, 2026, 11:34 AM UTC
Status: 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 [email protected]: mailto:[email protected]. Affected components Inngest Dashboard (Partial outage)
-
resolved Jun 19, 2026, 01:07 PM UTC
Status: Resolved The Support Portal is now available. Affected components Inngest Dashboard (Operational)
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 09:31 PM UTC
- Resolved
- May 26, 2026, 11:46 PM UTC
- Duration
- 2h 14m
Affected: Inngest Dashboard
Timeline · 3 updates
-
identified May 26, 2026, 09:31 PM UTC
Status: Identified We have identified the cause of the issue and are waiting for the downstream provider to implement their fix Affected components Inngest Dashboard (Partial outage)
-
monitoring May 26, 2026, 10:07 PM UTC
Status: Monitoring A fix has been deployed via Clerk and we're monitoring the system to ensure the system is fully operational. Affected components Inngest Dashboard (Operational)
-
resolved May 26, 2026, 11:46 PM UTC
Status: Resolved The incident is now resolved. Affected components Inngest Dashboard (Operational)
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 09:26 AM UTC
- Resolved
- May 26, 2026, 09:32 PM UTC
- Duration
- 12h 5m
Affected: Inngest Dashboard
Timeline · 3 updates
-
investigating May 26, 2026, 09:26 AM UTC
Status: 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. Affected components Inngest Dashboard (Partial outage)
-
monitoring May 26, 2026, 10:51 AM UTC
Status: Monitoring A fix has been deployed and we're monitoring the system to ensure the system is fully operational. Affected components Inngest Dashboard (Partial outage)
-
resolved May 26, 2026, 09:32 PM UTC
Status: Resolved The previous incident with the observability database has beens resolved, but there is a separate incident with a downstream provider. Affected components Inngest Dashboard (Operational)
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 01:42 PM UTC
- Resolved
- May 21, 2026, 08:20 PM UTC
- Duration
- 6h 38m
Affected: Inngest Dashboard
Timeline · 5 updates
-
investigating May 21, 2026, 01:42 PM UTC
Status: 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. Affected components Inngest Dashboard (Degraded performance)
-
investigating May 21, 2026, 02:21 PM UTC
Status: 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 identify the cause and resolve the issue. Affected components API (REST and GraphQL) (Degraded performance) Inngest Dashboard (Degraded performance)
-
monitoring May 21, 2026, 07:40 PM UTC
Status: 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 operational. Affected components Inngest Dashboard (Degraded performance) API (REST and GraphQL) (Degraded performance)
-
monitoring May 21, 2026, 07:59 PM UTC
Status: Monitoring We're monitoring the system to ensure the system is fully operational. Affected components Inngest Dashboard (Operational) API (REST and GraphQL) (Operational)
-
resolved May 21, 2026, 08:20 PM UTC
Status: Resolved The incident is now resolved and the system is fully operational. Affected components Inngest Dashboard (Operational) API (REST and GraphQL) (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 07:11 PM UTC
- Resolved
- Apr 28, 2026, 10:48 PM UTC
- Duration
- 3h 37m
Affected: Function execution
Timeline · 3 updates
-
investigating Apr 28, 2026, 07:11 PM UTC
Status: 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. Affected components Function execution (Degraded performance)
-
monitoring Apr 28, 2026, 10:27 PM UTC
Status: 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 the system more quickly. Affected components Function execution (Operational)
-
resolved Apr 28, 2026, 10:48 PM UTC
Status: 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 within our system earlier today. We have reverted that change and are working to understand the performance impact of this change. Affected components Function execution (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 08:06 PM UTC
- Resolved
- Apr 25, 2026, 06:04 PM UTC
- Duration
- 1d 21h
Timeline · 3 updates
-
identified Apr 23, 2026, 08:06 PM UTC
Status: Identified 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. Affected components API (REST and GraphQL) (Degraded performance)
-
monitoring Apr 25, 2026, 01:54 AM UTC
Status: Monitoring 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. Affected components API (REST and GraphQL) (Degraded performance)
-
resolved Apr 25, 2026, 06:04 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components API (REST and GraphQL) (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 12:15 PM UTC
- Resolved
- Apr 15, 2026, 11:21 PM UTC
- Duration
- 11h 5m
Affected: Function executionObservability
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 05:07 PM UTC
- Resolved
- Apr 02, 2026, 05:49 PM UTC
- Duration
- 42m
Affected: Inngest Dashboard
Timeline · 4 updates
-
identified Apr 02, 2026, 05:07 PM UTC
Status: Identified The Inngest dashboard is down due to an issue with our downstream provider. Vercel. We are working quickly to bring this back up Affected components Inngest Dashboard (Full outage)
-
identified Apr 02, 2026, 05:13 PM UTC
Status: Identified 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. Affected components Inngest Dashboard (Full outage)
-
monitoring Apr 02, 2026, 05:15 PM UTC
Status: Monitoring 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. Affected components Inngest Dashboard (Operational)
-
resolved Apr 02, 2026, 05:49 PM UTC
Status: Resolved 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 Affected components Inngest Dashboard (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 11:14 AM UTC
- Resolved
- Mar 31, 2026, 11:59 AM UTC
- Duration
- 44m
Timeline · 3 updates
-
investigating Mar 31, 2026, 11:14 AM UTC
Status: Investigating We are actively investigating an issue with proxied requests via step.fetch or step.ai.infer. We will provider further updates as we identify the cause and resolve the issue. If you are not using these features your system should remain unaffected. Affected components API (REST and GraphQL) (Partial outage)
-
monitoring Mar 31, 2026, 11:45 AM UTC
Status: Monitoring A fix has been deployed for step.fetch and step.ai.infer and we're monitoring the system to ensure the system is fully operational. We continue to investigate the root cause. Affected components API (REST and GraphQL) (Operational)
-
resolved Mar 31, 2026, 11:59 AM UTC
Status: Resolved The 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, the system was rolled back and a fix will be rolled out today. Affected components API (REST and GraphQL) (Operational)
Read the full incident report →
