Is Inngest down?
Last checked 9m agoNo incidents right now.
Inngest is operational right now. Last checked 9m ago; the most recent incident resolved 10d ago.
Real-time Inngest status, recent outages, and incident history — pulled directly from Inngest's official status page at https://status.inngest.com every 5 minutes. Pingoru tracks 5 Inngest services and has captured 14 incidents in the last 90 days (95.56% uptime). Get email, Slack, Discord, or webhook alerts the moment Inngest reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Function execution
Timeline · 4 updates
- investigating · Sep 04, 2026, 06:26 PM 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 (Degraded performance)
- investigating · Sep 04, 2026, 06:28 PM UTC
Status: Investigating We are actively investigating an issue with execution. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Partial outage)
- monitoring · Sep 04, 2026, 07:09 PM UTC
Status: 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: https://www.inngest.com/docs/platform/replay#how-to-create-a-new-replay Affected components Function execution (Partial outage)
- resolved · Sep 04, 2026, 07:10 PM UTC
Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
Latest: Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
-
-
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.
Latest: 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 …
-
-
Timeline · 1 update
- resolved · Aug 24, 2026, 08:38 PM UTC
Status: Resolved Between 23:38 UTC and 00:08 UTC, internal Connect message routing was degraded, resulting in delays for customers using Connect. Function processing has now been restored.
Latest: Status: Resolved Between 23:38 UTC and 00:08 UTC, internal Connect message routing was degraded, resulting in delays for customers using Connect. Function processing has now been r…
-
- 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)
Latest: Status: Resolved Run history delay has caught up and the incident is now resolved. Affected components Observability (Operational)
-
- 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)
Latest: Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)
-
See the full Inngest outage history
9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Inngest outage history →Or sign up free to get alerts when Inngest breaks · 10 free monitors · No credit card
- Degraded Function Execution ResolvedStarted Sep 04, 2026, 07:10 PM UTC · Resolved Sep 04, 2026, 07:10 PM UTC · —
- Started Aug 26, 2026, 12:31 AM UTC · Resolved Aug 26, 2026, 12:31 AM UTC · —
- Started Aug 24, 2026, 08:38 PM UTC · Resolved Aug 24, 2026, 08:38 PM UTC · —
- Started Aug 20, 2026, 10:35 PM UTC · Resolved Aug 20, 2026, 10:35 PM UTC · —
- Delays in Function Execution ResolvedStarted Aug 20, 2026, 03:04 PM UTC · Resolved Aug 20, 2026, 03:04 PM UTC · —
- Started Aug 19, 2026, 04:41 AM UTC · Resolved Aug 19, 2026, 04:41 AM UTC · —
- Started Aug 10, 2026, 10:30 PM UTC · Resolved Aug 10, 2026, 10:30 PM UTC · —
- Function processing delays ResolvedStarted Jul 23, 2026, 03:24 PM UTC · Resolved Jul 23, 2026, 03:24 PM UTC · —