Inngest incident

Subset of customers experiencing function execution delays

Minor Resolved View vendor source →
Started
Feb 03, 2026, 11:36 PM UTC
Resolved
Feb 03, 2026, 11:36 PM UTC
Duration
Detected by Pingoru
Feb 03, 2026, 11:36 PM UTC

Affected components

Function execution

Update timeline

  1. investigating Feb 03, 2026, 04:41 PM UTC

    Status: Investigating We are actively investigating an issue with one of our queue shards experiencing higher than usual delays with function execution. We will provider further updates as we identify the cause and resolve the issue. Affected components Function execution (Degraded performance)

  2. investigating Feb 03, 2026, 08:40 PM UTC

    Status: Investigating We're working to mitigate the slowness by re-allocating workloads across our queue shards. Additionally, we're provisioning more capacity for workloads to alleviate pressure on the system queues. Affected components Function execution (Degraded performance)

  3. investigating Feb 03, 2026, 09:41 PM UTC

    Status: Investigating We have made a configuration change in the system to unlock additional throughput in an attempt to reduce the bottleneck. System throughput is increasing in some affected part of the system. Affected components Function execution (Degraded performance)

  4. monitoring Feb 03, 2026, 10:54 PM UTC

    Status: Monitoring The configuration change made earlier has increased throughput and reduce latency for affected users. The impact of this change takes up to an hour to roll out. Our internal metrics are seeing p75 and p90s return to normal levels with some anomalies in p95 and p99 execution latency, but generally closer to normal. We continue to monitor and investigate long term mitigations. Affected components Function execution (Degraded performance)

  5. resolved Feb 03, 2026, 11:36 PM UTC

    Status: Resolved System latency for function execution has returned to normal levels for the affected users. The incident has been resolved. The cause of the incident was due to increased load causing congestion. We applied changes to the system to reduce congestion, resulting in increasing throughput. We also re-distributed some affected users in an effort to mitigate impact. Our team's planned to roll out new infrastructure in the coming weeks and is accelerating that plan to aim to roll it out later this week to increase overall capacity. Affected components Function execution (Operational)

Looking to track Inngest downtime and outages?

Pingoru polls Inngest's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Inngest reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Inngest alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Inngest for free

5 free monitors · No credit card required