How can my agent or app check n8n Cloud status?

Fetch https://upbutler.com/status/n8n/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":"n8n"}, on https://upbutler.com/mcp/public.

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

Add "n8n" to the dependencies of your UpButler workspace. When one of your monitors fails while n8n Cloud 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 n8n Cloud down?

n8n Cloud publishes no status we can read

Right now

Unknown. No machine-readable official status; see their status page.

No official machine-readable status

For agents

proceed

Proceed.

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

MCP: upstream_status {"service":"n8n"}

Hosted n8n workflow automation.

What n8n Cloud says

status.n8n.cloud has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.

Their site: status.n8n.cloud

What UpButler measured

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

n8n Cloud incidents, last 90 days

Without a machine-readable source there is no incident history to show. n8n Cloud keeps its own at status.n8n.cloud.

Get alerted when n8n Cloud goes down

n8n Cloud publishes no incidents we can read, so there is nothing to send an alert about. If you depend on it, monitor your own use of it: add a monitor with your key or URL.

Status badge

Show n8n Cloud's current status in a README or an internal wiki. It updates by itself.

[![n8n Cloud status](https://upbutler.com/status/n8n/badge.svg)](https://upbutler.com/status/n8n)

Tell your outage from n8n Cloud's

Declare that your project depends on n8n Cloud. When one of your monitors fails while n8n Cloud 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:
  - n8n

Ask before you retry

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

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "n8n",
  "verdict": "proceed",
  "status": "unknown",
  "reason": "No machine-readable official status; see their status page",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is n8n Cloud down right now?: We cannot tell. status.n8n.cloud has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful. Their own status page is at https://status.n8n.cloud.
Where does this status come from?: status.n8n.cloud has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.
How can my agent or app check n8n Cloud status?: Fetch https://upbutler.com/status/n8n/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":"n8n"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or n8n Cloud's?: Add "n8n" to the dependencies of your UpButler workspace. When one of your monitors fails while n8n Cloud 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.

Also check

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