n8n Status: How to Check If n8n Is Down Right Now (2026)
Updated June 2026 · 6 min read · By API Status Check
Quick Answer: Check n8n Status Now
n8n is a powerful open-source workflow automation platform used by developers, ops teams, and agencies. Unlike fully-managed tools like Zapier, n8n comes in two forms: n8n Cloud (managed SaaS) and self-hosted (run on your own server). Diagnosing n8n issues requires knowing which deployment you're on — the troubleshooting paths are completely different.
n8n Cloud vs Self-Hosted: Which Are You Running?
- • URL ends in
.app.n8n.cloud - • Managed by n8n GmbH — no server to maintain
- • Check status.n8n.io for outages
- • Automatic updates and backups
- • Your own domain or IP:5678
- • You control the server — you own the outage
- • No central status page — check your server
- • Updates are manual
Understanding n8n Cloud's Status Page (status.n8n.io)
n8n Cloud operates status.n8n.io — its official status page. The editor and execution engine are architecturally separate, which means you can sometimes see your workflows in the editor while executions silently fail.
Cloud Editor
The n8n workflow builder UI. If this is down, you can't create or edit workflows. Usually served from a CDN so tends to be more resilient than the execution engine.
Execution Engine
The backend that actually runs your workflows — triggered by schedules, webhooks, and manual runs. If this is degraded, workflows may queue, execute late, or fail silently.
Webhooks
Incoming webhook triggers. n8n Cloud assigns webhook URLs to each instance. If the webhook layer is degraded, external services (Stripe, GitHub, etc.) can't trigger your workflows.
API
The n8n REST API used to trigger workflows programmatically, list executions, and manage credentials. API degradation affects CI/CD integrations and custom workflow triggers.
Queue / Worker System
For accounts using queue mode (higher-tier Cloud plans), workers process jobs asynchronously. Queue degradation causes execution backlogs even when the editor appears healthy.
Credential Storage
Where n8n securely stores OAuth tokens and API keys for connected services. Credential issues cause node authentication failures across all workflows using that credential.
Diagnosing Self-Hosted n8n Issues
Self-hosted n8n has no central status page — when it's down, you own the investigation. Here's the diagnostic checklist:
Self-Hosted n8n Diagnostic Commands
# 1. Check if n8n process is running
systemctl status n8n
# or if using pm2:
pm2 status
# 2. Check n8n logs for errors
journalctl -u n8n -n 50 --no-pager
# or Docker:
docker logs n8n --tail 50
# 3. Check disk space (full disk stops execution)
df -h
# 4. Test n8n is reachable locally
curl -f http://localhost:5678/healthz
# 5. Test webhook URL from outside
curl -X POST https://your-n8n.example.com/webhook/test
Common Self-Hosted n8n Failure Causes
- 🔴 Full disk: n8n writes execution logs to SQLite/Postgres. When the disk fills, executions halt with no obvious error in the editor.
- 🔴 Expired OAuth tokens: Google, Slack, and other OAuth credentials expire. Re-authenticate in Settings → Credentials.
- 🔴 WEBHOOK_URL mismatch: If your
WEBHOOK_URLenv var doesn't match your public URL, incoming webhooks silently fail. - 🔴 Node.js version: After updates, n8n may require a newer Node.js version. Check
node --versionvs n8n's requirements. - 🔴 Database corruption: SQLite databases can corrupt during crashes. Back up regularly and consider migrating to Postgres for production.
Monitor your n8n instance with external uptime checks
If you run self-hosted n8n, Better Stack can monitor your instance from outside your network and alert you the moment it goes down — before you notice missed workflow executions. Free plan available.
Try Better Stack Free →What n8n Status Colors Mean (Cloud)
Common n8n Issues and What They Mean
"Workflows not executing on schedule"For n8n Cloud: check the Execution Engine component on status.n8n.io. For self-hosted: verify the n8n process is running, check cron-style triggers in Settings → Trigger Nodes, and confirm the instance timezone is set correctly (N8N_DEFAULT_TIMEZONE env var)."Webhook trigger not firing"For Cloud: check status.n8n.io Webhooks component. For self-hosted: verify your WEBHOOK_URL env var matches the externally reachable URL, check that port 5678 is open (or your reverse proxy is configured correctly), and test the URL with curl from an external machine."Node authentication error / 401 Unauthorized"OAuth tokens have expired or API keys were rotated. Go to Credentials in n8n and re-authenticate or update the key. This is not a platform outage — it's a credential expiry. Set up credential rotation reminders to avoid this during critical workflow windows."Execution stuck in "running" state"n8n Cloud: the execution engine may be degraded — check status.n8n.io. Self-hosted: n8n may have crashed mid-execution. Restart the n8n process. Stale executions typically need manual resolution from Settings → Executions → mark as failed."Editor loads but "Save" button does nothing"The n8n backend API is not responding. For Cloud: check status.n8n.io API component. For self-hosted: check if the n8n process is running and check logs for database errors (especially SQLite lock errors)."n8n Cloud upgrade broke my workflow"n8n auto-updates Cloud instances. If a workflow breaks after an update, check n8n's changelog at docs.n8n.io/release-notes/ for breaking changes in that version. Node parameter names occasionally change between major versions.Frequently Asked Questions
Where is the official n8n status page?
n8n Cloud's official status page is status.n8n.io. It covers n8n Cloud infrastructure only — not self-hosted instances. For self-hosted n8n, there is no central status page. You monitor your own server.
How do I check if my self-hosted n8n is running?
Run 'systemctl status n8n' or 'pm2 status' to check the process. Then run 'curl -f http://localhost:5678/healthz' to verify n8n is responding. If the healthz endpoint returns 200, n8n is up. Also run 'df -h' to check disk space — a full disk silently stops n8n executions.
Will failed n8n executions retry automatically?
n8n Cloud and self-hosted n8n do not automatically retry failed executions by default. You can add retry logic inside workflows using Error Trigger nodes or configure retry settings on individual nodes. Webhook payloads from external services (Stripe, GitHub, etc.) are typically retried by the sending service — check their retry policies.
How is n8n different from Zapier for outage purposes?
Zapier is fully managed SaaS — you rely entirely on Zapier's infrastructure. n8n Cloud is similar. Self-hosted n8n means you own both the uptime and the troubleshooting. Self-hosted offers maximum control and no platform dependency but requires operational knowledge to keep running reliably.
How do I get alerts when n8n Cloud goes down?
Subscribe to updates at status.n8n.io for email notifications during Cloud incidents. For self-hosted, use an external uptime monitor like Better Stack or API Status Check to ping your n8n healthz endpoint from outside your network and alert you when it goes down.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time n8n goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for n8n + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial