How do I know if n8n is down?

For n8n Cloud, check status.n8n.io for real-time incident updates. For self-hosted n8n, the issue is almost always your own server, database connection, or Docker container rather than n8n itself, since there is no shared cloud infrastructure to go down.

Why do my n8n workflows stop running?

Common causes: an expired credential on a connected node (e.g. an API key), a workflow trigger (webhook or schedule) misfiring, database connection issues on self-hosted instances, or an upstream service the workflow depends on being down itself.

Is n8n Cloud down different from my self-hosted instance being down?

Yes — n8n Cloud outages are tracked centrally at status.n8n.io and affect all Cloud users simultaneously. Self-hosted n8n runs on your own infrastructure, so an outage there is local to your server, database, or Docker setup and won't appear on n8n's status page.

What should I do when n8n workflows fail?

Check the execution log for the specific failed node and error message first — n8n surfaces this clearly in the UI. If it's a credential error, refresh the API key. If it's a connection timeout to an external service, check whether that service itself is down.

Can I monitor n8n uptime automatically?

Yes. API Status Check monitors n8n Cloud status continuously and can alert your team via Slack, email, or PagerDuty. For self-hosted instances, pair this with your own server/uptime monitoring for full coverage.

Is n8n Down? How to Check n8n Cloud & Self-Hosted Status (2026)

n8n powers business-critical automations for thousands of teams — so when a workflow silently stops running, it can take a while to notice, and even longer to figure out whether the problem is n8n Cloud, your self-hosted instance, or an upstream service your workflow depends on.

This guide walks through exactly how to determine is n8n down, or is it a config issue on your end?

How to Check if n8n is Down (Fastest Methods)

1. Check the Official n8n Status Page

n8n maintains a live status page at status.n8n.io covering n8n Cloud infrastructure. If you're on Cloud and see an incident here, it's confirmed on n8n's side, not yours.

2. Read the Execution Log

n8n shows a detailed execution log for every workflow run, including the exact node and error that caused a failure. This is almost always faster than guessing — a 401 on a node means a credential problem, not an n8n outage.

3. Check Self-Hosted Infrastructure Directly

If you self-host, there's no shared cloud status to check — the problem is on your server. Check your Docker container logs, database connection (Postgres/SQLite), and available disk space first.

4. Use API Status Check for Automated Monitoring

For n8n Cloud, API Status Check monitors status continuously and sends instant alerts via Slack, email, or PagerDuty.

📡

Recommended

Monitor Your Automation Stack

Don't let a broken n8n workflow go unnoticed. Get professional monitoring and instant alerts with Better Stack.

Try Better Stack Free →

Why Do n8n Workflows Stop Running?

Expired Credentials: An OAuth token or API key on a connected node expires, causing every run to fail at that node.
Trigger Misconfiguration: A webhook trigger URL changes or a schedule trigger's cron expression stops matching expected timing.
Self-Hosted Infra Issues: Database connection drops, disk space fills up, or the Docker container restarts unexpectedly.
Upstream Service Outages: If a workflow calls Slack, Google Sheets, or another API that's down, the workflow fails even though n8n itself is fine.
n8n Cloud Platform Incidents: Rare, but check status.n8n.io to rule this out first if you're on Cloud.

🔐

Recommended

Secure Your n8n Credentials

n8n workflows connect to dozens of services with stored credentials. Keep them locked down with a password manager built for teams.

Try 1Password Free →

n8n Troubleshooting Checklist

Step 1: Check the Execution Log

Identify the exact node and error message that failed.
401/403 errors mean expired credentials, not a platform outage.

Step 2: Check n8n Cloud Status (If Applicable)

Visit status.n8n.io to rule out a platform-wide incident before digging further.

Step 3: Check Self-Hosted Server Health

Review Docker logs, database connectivity, and disk space if you self-host — these cause the vast majority of self-hosted "outages."

Step 4: Test the Upstream Service Directly

If a specific node fails, test that third-party service (Slack, Sheets, etc.) directly to confirm whether the problem is actually upstream.

Conclusion: Keep Your Automations Running

Most n8n disruptions come down to credentials, self-hosted infrastructure, or an upstream service — not n8n Cloud itself. Check the execution log first, and you'll usually have your answer in under a minute.

Get n8n Outage Alerts in Seconds

Set up automated monitoring for n8n Cloud and your other automation tools. Get Slack or email alerts instantly.

Start Your Free Trial →

Is n8n Down? How to Check n8n Cloud & Self-Hosted Status in 2026