Where does this status come from?

From Inngest's own status page API at https://status.inngest.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Inngest's words.

How can my agent or app check Inngest status?

Fetch https://upbutler.com/status/inngest/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"inngest"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Inngest's?

Add "inngest" to the dependencies of your UpButler workspace. When one of your monitors fails while Inngest has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Inngest down?

Right now

No. Inngest is operational.

No incidents reported.

Read from status.inngest.com 3 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/inngest/status.agent.json

MCP: upstream_status {"service":"inngest"}

Durable functions and event-driven workflows.

What Inngest reports

Operational

Taken as is from Inngest's own status page API. Incident titles and component names below are theirs.

Open status.inngest.com

UpButler's independent probe

There is no keyless endpoint of Inngest that says anything useful, so UpButler does not probe it. To check your own Inngest account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Inngest components

5 operational

Function executionOperational
Event APIOperational
API (REST and GraphQL)Operational
ObservabilityOperational
Inngest DashboardOperational

Inngest incidents, last 90 days

3 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Inngest. A typical one lasted 19 min; the longest 1 h 56 min.

Started (UTC)	Incident	Impact	Lasted
2026-10-09 21:33	Degraded Function Execution	minor	1 h 56 min
2026-09-26 13:39	Delayed observability of events	minor	19 min
2026-09-26 06:01	Delays with function execution	major	18 min

Tell your outage from Inngest's

Declare that your project depends on Inngest. When one of your monitors fails while Inngest has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - inngest

Ask before you retry

curl -s https://upbutler.com/status/inngest/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "inngest",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Inngest down right now?: No. As of 2026-10-10 05:11 UTC, Inngest is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Inngest's own status page API at https://status.inngest.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Inngest's words.
How can my agent or app check Inngest status?: Fetch https://upbutler.com/status/inngest/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"inngest"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Inngest's?: Add "inngest" to the dependencies of your UpButler workspace. When one of your monitors fails while Inngest has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Inngest. Status and incident text belong to Inngest and are read from their public status source; the probe result is UpButler's own measurement.