Is n8n Down?
Reachable from all 8 checked regions
Average response time: 176ms
Last checked · checks run every 6 hours
Official status page: https://status.n8n.io
n8n uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
21-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What n8n does
n8n is a workflow automation tool that connects APIs and services into automated pipelines, offered both as a cloud service and as software teams run on their own servers. Because workflows usually run unattended on a schedule, an outage tends to be noticed only when something downstream fails to happen rather than when anyone sees an error.
What an outage looks like
The failure is usually silence rather than an error, because scheduled workflows simply do not run. Executions stop being recorded, webhooks that trigger workflows go unanswered so the calling system sees its own failure instead, and the editor can load while execution does not. Self-hosted installations are untouched by a cloud incident, which is the key distinction here.
What to do about it
Check status.n8n.io, which covers n8n.cloud specifically and shows overall uptime across the last 24 hours, 7, 30 and 90 days alongside a calendar view. It offers email subscription for updates. If you host n8n yourself this page says nothing about your instance: check your own server first, because a cloud incident and a self-hosted failure look identical from a workflow that did not fire.
Is it down for everyone, or just you?
If this page says n8n is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.
Related services
n8n outage FAQ
Does an n8n outage affect self-hosted instances?
How do I know whether a scheduled workflow actually ran?
What happens to webhooks during an n8n outage?
How far back does n8n's status page go?
How we measure this
- We request n8n's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where n8n publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when n8n goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.
Start Free Monitoring