Is Inngest down?
Last checked 8m agoNo incidents right now.
Inngest is operational right now. Last checked 8m ago; the most recent incident resolved 18d 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 16 incidents in the last 90 days (97.33% 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- 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)
Latest: Status: Resolved The incident is now resolved. Affected components Inngest Dashboard (Operational)
-
- 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)
Latest: 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 …
-
- 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)
Latest: Status: Resolved The incident is now resolved and the system is fully operational. Affected components Inngest Dashboard (Operational) API (REST and GraphQL) (Operational)
-
- 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)
Latest: 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 chan…
-
-
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)
Latest: Status: Resolved The incident is now resolved and the system is full operational. Affected components API (REST and GraphQL) (Operational)
-
See the full Inngest outage history
11 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
- Started May 26, 2026, 11:46 PM UTC · Resolved May 26, 2026, 11:46 PM UTC · —
- Started May 26, 2026, 09:32 PM UTC · Resolved May 26, 2026, 09:32 PM UTC · —
- Started May 21, 2026, 08:20 PM UTC · Resolved May 21, 2026, 08:20 PM UTC · —
- Increased function execution latency ResolvedStarted Apr 28, 2026, 10:48 PM UTC · Resolved Apr 28, 2026, 10:48 PM UTC · —
- Started Apr 25, 2026, 06:04 PM UTC · Resolved Apr 25, 2026, 06:04 PM UTC · —
- Started Apr 23, 2026, 08:06 PM UTC · Resolved Apr 25, 2026, 06:04 PM UTC · 1d 21h
- Delays in function run scheduling ResolvedStarted Apr 15, 2026, 11:21 PM UTC · Resolved Apr 15, 2026, 11:21 PM UTC · —
- Delays in function run scheduling ResolvedStarted Apr 15, 2026, 12:15 PM UTC · Resolved Apr 15, 2026, 11:21 PM UTC · 11h 5m