Is Inngest down?

Last checked 6m ago
Current status
Inngest is up

No incidents right now.

Get alerts when Inngest breaks →

Free · no credit card

Official status page: https://status.inngest.com · Polled every 5 minutes · 5 components tracked

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 29 incidents in the last 90 days (95.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Inngest reports a new incident — free for 5 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 6,000+ providers
Inngest uptime 95.89% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Increased function execution latency
    Resolved —
    Started Apr 28, 2026, 10:48 PM UTC · Resolved Apr 28, 2026, 10:48 PM UTC
    Function execution
    3 updates · show timeline
    • 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…

  2. Degraded performance for REST API (runs/events data)
    Resolved —
    Started Apr 25, 2026, 06:04 PM UTC · Resolved Apr 25, 2026, 06:04 PM UTC
    1 update · show timeline
    • 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)

  3. Degraded performance for REST API (runs/events data)
    Resolved 1d 21h
    Started Apr 23, 2026, 08:06 PM UTC · Resolved Apr 25, 2026, 06:04 PM UTC

See the full Inngest outage history

26 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 9 incidents
  • Increased function execution latency Resolved
    Started Apr 28, 2026, 10:48 PM UTC · Resolved Apr 28, 2026, 10:48 PM UTC · —
  • Degraded performance for REST API (runs/events data) Resolved
    Started Apr 25, 2026, 06:04 PM UTC · Resolved Apr 25, 2026, 06:04 PM UTC · —
  • Degraded performance for REST API (runs/events data) Resolved
    Started Apr 23, 2026, 08:06 PM UTC · Resolved Apr 25, 2026, 06:04 PM UTC · 1d 21h
  • Delays in function run scheduling Resolved
    Started Apr 15, 2026, 11:21 PM UTC · Resolved Apr 15, 2026, 11:21 PM UTC · —
  • Delays in function run scheduling Resolved
    Started Apr 15, 2026, 12:15 PM UTC · Resolved Apr 15, 2026, 11:21 PM UTC · 11h 5m
  • Dashboard down Resolved
    Started Apr 02, 2026, 05:49 PM UTC · Resolved Apr 02, 2026, 05:49 PM UTC · —
  • Dashboard down Resolved
    Started Apr 02, 2026, 05:07 PM UTC · Resolved Apr 02, 2026, 05:49 PM UTC · 42m
  • Increased failures with step.fetch, step.ai.infer Resolved
    Started Mar 31, 2026, 11:59 AM UTC · Resolved Mar 31, 2026, 11:59 AM UTC · —

See Inngest in your Pingoru dashboard

Monitor Inngest alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Inngest to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Inngest incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Inngest or see every provider at once.

Maintenance calendar

Scheduled Inngest maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Inngest status change, one inbox

Pingoru watches Inngest's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Inngest reports on 5 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Inngest alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Inngest maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Inngest services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Inngest from the same account, with per-user notification preferences for any monitor.

Get notified on Inngest status changes

Pingoru watches Inngest's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Inngest free

Monitor Inngest along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Inngest and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Inngest uptime & incident history

See 90 days of Inngest uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Inngest uptime history

Frequently asked questions

What is Inngest's uptime?
Over the last 90 days, Inngest reported 95.89% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.inngest.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Inngest's uptime history rolling forward in real time.
Has Inngest had outages in 2026?
Yes — Inngest has had 29 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Inngest outage?
The most recent Inngest incident was "Increased function execution latency", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.inngest.com. See the full incident card above for affected components and the update timeline.
How often does Inngest have outages?
Based on the last 90 days, Inngest averages 9.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Inngest's status page?
Inngest's official status page is https://status.inngest.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Inngest down right now?
Inngest is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Inngest reports a change. Current status is based on 5 tracked services.
How does Pingoru know if Inngest is down?
We read https://status.inngest.com directly, using Inngest's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Inngest has an outage?
Create a free Pingoru account and add Inngest as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Inngest's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Inngest incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Inngest issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Inngest status?
We use Inngest's own status page at https://status.inngest.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Inngest components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Inngest's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Inngest free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →