Is Inngest down?

Last checked 1m ago
Current status
Inngest is up

No incidents right now.

Inngest is operational right now. Last checked 1m 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 status.inngest.com every 5 minutes. Pingoru tracks 5 Inngest services and has captured 14 incidents in the last 90 days (96.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Inngest reports a new incident, free for 3 monitors, no credit card.

Users who monitor Inngest also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 8,000+ providers
Inngest uptime 96.44% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 13m
    Started Oct 20, 2026, 01:07 PM UTC · Resolved Oct 20, 2026, 01:20 PM UTC
    Event API
    Timeline · 3 updates
    • identified · Oct 20, 2026, 01:07 PM UTC

      Status: Identified We've identified intermittent errors affecting the Event API due to connectivity issues with a downstream database provider. We're investigating the issue. Affected components Event API (Degraded performance) API (REST and GraphQL) (Degraded performance)

    • monitoring · Oct 20, 2026, 01:12 PM UTC

      Status: Monitoring The connectivity issues with our downstream database provider have subsided, and the Event API is operating normally again. We're continuing to monitor the service while investigating the root cause. Affected components Event API (Operational) API (REST and GraphQL) (Operational)

    • resolved · Oct 20, 2026, 01:20 PM UTC

      Status: Resolved The incident is now resolved and the system is fully operational. Affected components Event API (Operational) API (REST and GraphQL) (Operational)

    Latest: Status: Resolved The incident is now resolved and the system is fully operational. Affected components Event API (Operational) API (REST and GraphQL) (Operational)

  2. Resolved 22h
    Started Oct 11, 2026, 04:26 AM UTC · Resolved Oct 12, 2026, 02:26 AM UTC
    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)

    Latest: Status: Resolved The system has been operationally stable for the last 22 hours Affected components Function execution (Operational)

  3. Resolved 1h 53m
    Started Oct 10, 2026, 03:45 PM UTC · Resolved Oct 10, 2026, 05:38 PM UTC
    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)

    Latest: Status: Resolved The incident is now resolved and the system is full operational. Affected components Function execution (Operational)

  4. Resolved 2h 23m
    Started Oct 09, 2026, 09:06 PM UTC · Resolved Oct 09, 2026, 11:29 PM UTC
    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)

    Latest: 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 perfor…

  5. Resolved 18m
    Started Sep 26, 2026, 01:39 PM UTC · Resolved Sep 26, 2026, 01:58 PM UTC
    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)

    Latest: Status: Resolved The delay in events observability is now resolved and the system is fully operational. Affected components Observability (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

Incident record

Since April 2026 · incident.io · 5 components checked every 5 minutes
66incidents recorded
66last 12 months
14last 90 days
6 hourstypical duration, 12 months

The longest incident in the last year, Issues Affecting Function Triggering from Events on July 10, 2026, ran for 3 days.

Most affected components, last 12 months

  • Function execution24
  • Inngest Dashboard9
  • Observability7
  • Event API4

Latest incidents

  • Intermittent Event API Connectivity Issues October 20, 2026 · 13 minutes · degraded service

    Status: Identified We've identified intermittent errors affecting the Event API due to connectivity issues with a downstream database provider. We're…

  • Intermittent Degraded Function Execution October 11, 2026 · 22 hours · degraded service

    Status: Investigating We are actively investigating an issue with intermittent degraded function. We will provider further updates as we identify the cause and…

  • Degraded function execution October 10, 2026 · 113 minutes · degraded service

    Status: Investigating We are actively investigating an issue with function. We will provider further updates as we identify the cause and resolve the issue.…

Outage history

Past 90 days · 14 incidents View full outage history →