Inngest Outage History

Inngest is up right now

Pingoru has recorded 66 incidents for Inngest: 66 in the last 12 months and 14 in the last 90 days.

Source: status.inngest.com

66incidents recorded

66last 12 months

14last 90 days

6 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Inngest in April 2026, so earlier months are not shown. Hover a bar for its value.

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 590 (4%)

Incidents, newest first

Minor March 31, 2026 Increased failures with step.fetch, step.ai.infer 44m

Started Mar 31, 2026, 11:14 AM UTC· resolved Mar 31, 2026, 11:59 AM UTC

investigating Mar 31, 2026, 11:14 AM UTC

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.
monitoring Mar 31, 2026, 11:45 AM UTC

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.
resolved Mar 31, 2026, 11:59 AM UTC

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.

Read the full incident report →

Minor March 26, 2026 Function run scheduling delays 1h 3m Function execution

Started Mar 26, 2026, 10:42 PM UTC· resolved Mar 26, 2026, 11:45 PM UTC

investigating Mar 26, 2026, 10:42 PM UTC

We are actively investigating delays with function run scheduling. We will provider further updates as we identify the cause and resolve the issue.
identified Mar 26, 2026, 10:58 PM UTC

We have identified the cause of the issue affecting a core system queue. We are rolling our a mitigation now and preparing follow up changes.
identified Mar 26, 2026, 11:15 PM UTC

We have deployed an additional hot fix. The earlier change rolled out have addressed the core issue and the system is now processing the backlog. The backlog is decreasing. We will provide another update as we have an estimate on time to recovery.
monitoring Mar 26, 2026, 11:35 PM UTC

The mitigations have fixed the issue and the event backlog is now caught up. We continue to monitor and evaluate other short and long term mitigations to add.
resolved Mar 26, 2026, 11:45 PM UTC

The 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 mitigations deployed have addressed the issue. The team is preparing a post-mortem to ensure this issue does not reoccur.

Read the full incident report →

Minor March 10, 2026 Reduced throughput on function execution 36m Function execution

Started Mar 10, 2026, 01:54 AM UTC· resolved Mar 10, 2026, 02:31 AM UTC

monitoring Mar 10, 2026, 01:54 AM UTC

We are actively investigating an issue with reduced throughput for function execution. The system experienced a short reduction and has recovered. We continue investigation while monitoring the system.
investigating Mar 10, 2026, 02:03 AM UTC

We are experiencing networking issues preventing function execution workers from working. We are in contact with our infrastructure provider as we work on active mitigations.
identified Mar 10, 2026, 02:23 AM UTC

We have identified the cause of the issue with networking. We are quickly working to fix the issue.
resolved Mar 10, 2026, 02:31 AM UTC

The 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.

Read the full incident report →

Minor March 3, 2026 Function execution delayed 17m Function execution

Started Mar 03, 2026, 11:27 PM UTC· resolved Mar 03, 2026, 11:44 PM UTC

investigating Mar 03, 2026, 11:27 PM UTC

We are actively investigating an issue with function execution affecting all accounts. We will provider further updates as we identify the cause and resolve the issue.
monitoring Mar 03, 2026, 11:33 PM UTC

We identified the issue and fixed the issue with the backlog. Function execution delay is caught up. We continue to monitor the system.
resolved Mar 03, 2026, 11:44 PM UTC

The incident is now resolved and the system is full operational after monitoring.

Read the full incident report →

Minor February 26, 2026 Elevated latency for function execution 53m Function execution

Started Feb 26, 2026, 01:14 AM UTC· resolved Feb 26, 2026, 02:07 AM UTC

investigating Feb 26, 2026, 01:14 AM UTC

We are actively investigating an issue with elevated latency for function execution for some queue shards. We will provider further updates as we identify the cause and resolve the issue.
identified Feb 26, 2026, 01:35 AM UTC

We have identified the issue with some problem servers groups that reached saturation. These servers have been isolated and removed from the usage pool. The system is stable now as we bring additional capacity online for redundancy and overhead.
monitoring Feb 26, 2026, 02:06 AM UTC

The new servers have been brought online to increase capacity and we are monitoring as they are introduced into our usage pool. Function execution on all shards is performing as expected, but we are continuing to monitor this closely throughout the coming hours.
resolved Feb 26, 2026, 02:07 AM UTC

The incident is now resolved and the system is full operational.

Read the full incident report →

Minor February 19, 2026 Degraded dashboard availability 2h 26m Inngest Dashboard

Started Feb 19, 2026, 04:21 PM UTC· resolved Feb 19, 2026, 06:47 PM UTC

investigating Feb 19, 2026, 04:21 PM UTC

We are actively investigating an issue with our app at https://app.inngest.com. This is caused by downtime in an upstream provider. We will provider further updates as we identify the cause and resolve the issue.
monitoring Feb 19, 2026, 05:21 PM UTC

Availability issues with our upstream auth provider are decreasing. We are monitoring the system and will close out the incident if auth remains available.
resolved Feb 19, 2026, 06:47 PM UTC

The incident is now resolved and the system is full operational.

Read the full incident report →

Major February 19, 2026 Degraded dashboard availability 2h 26m

Started Feb 19, 2026, 04:21 PM UTC· resolved Feb 19, 2026, 06:47 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 10, 2026 Delays on some function execution 40m Function execution

Started Feb 10, 2026, 03:16 PM UTC· resolved Feb 10, 2026, 03:57 PM UTC

identified Feb 10, 2026, 03:16 PM UTC

We have identified the cause of the issue. We're actively working on implementing a fix to resume normal operation of the system. Our internal networking teams are improving the scalability of NAT64 as we scale our services.
resolved Feb 10, 2026, 03:57 PM UTC

The incident is now resolved and the system is full operational.

Read the full incident report →

Minor February 9, 2026 Delayed function execution 7h 19m Function execution

Started Feb 09, 2026, 03:31 PM UTC· resolved Feb 09, 2026, 10:50 PM UTC

investigating Feb 09, 2026, 03:31 PM UTC

We are actively investigating delayed function execution.
monitoring Feb 09, 2026, 03:52 PM UTC

We scaled up the infrastructure served the affected subset of customers, which will begin to reduce latency to normal levels.
resolved Feb 09, 2026, 06:13 PM UTC

The incident is now resolved and the system is full operational.
identified Feb 09, 2026, 09:39 PM UTC

Function execution delays have returned for a subset of users. As we mitigated issues from earlier, some queue related slowness has returned affecting a subset of users running on certain shards.
resolved Feb 09, 2026, 10:50 PM UTC

After 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 team is in the midst of rolling out additional system capacity going forward.

Read the full incident report →

Minor February 9, 2026 Delayed function run status 53m Observability

Started Feb 09, 2026, 06:58 AM UTC· resolved Feb 09, 2026, 07:51 AM UTC

monitoring Feb 09, 2026, 06:58 AM UTC

Run status and traces are currently delayed. The system has been scaled and is catching up. Function execution is unaffected.
monitoring Feb 09, 2026, 07:26 AM UTC

The run trace and event history ingestion pipeline is nearly caught up. We further increased the capacity here to catch up on the backlog cause by very high load.
resolved Feb 09, 2026, 07:51 AM UTC

Runs, traces and events data are all caught up from their temporary backlog. The dashboard metrics are all being processed with no backlog.