Free 3 min read
Is n8n Down?
Check live n8n status — AI workflow automation, LLM nodes, agent workflows, self-hosted or n8n.cloud. See recent incidents and set up free email alerts.
n8n — live status
Updated every 5 minutes. Full incident history at prismix.dev/service/n8n-ai.
Quick check: is n8n down right now?
- Prismix: prismix.dev/service/n8n-ai — live status + 30-day uptime + incidents.
- n8n.cloud status:
status.n8n.io— n8n's own status page for the managed cloud offering. - API call:
curl https://prismix.dev/api/v1/statuses | jq '.services[] | select(.id=="n8n-ai")'
Set up free email alerts for n8n
- 1
Sign in
Go to prismix.dev/sign-in — email OTP or GitHub sign-in.
- 2
Star n8n
On prismix.dev/service/n8n-ai, click the ☆ star icon.
- 3
Alerts are live
You'll get an email within minutes of any status change.
Common causes of "n8n not working"
If Prismix shows n8n as "Operational" but you're having issues:
- AI node credential error — n8n's AI nodes (OpenAI, Anthropic, Google Gemini) authenticate via stored credentials in your n8n instance. If a credential was created with an API key that has since been rotated or deleted, the node fails with a 401 at execution time. Navigate to Credentials, find the affected credential, and update the API key.
- OpenAI or Anthropic quota exceeded in workflow — n8n AI workflows can trigger hundreds of LLM calls per execution, rapidly hitting provider rate limits or monthly quotas. The node shows a 429 error and the workflow execution halts. Add a "Wait" node between AI calls or upgrade your LLM provider plan to increase limits.
- Webhook URL not reachable — Workflows triggered by webhooks require n8n's webhook server to be publicly accessible. On self-hosted instances behind a NAT or firewall, webhooks from third-party services silently fail. Verify your
WEBHOOK_URLenvironment variable points to a publicly accessible URL, not localhost. - Execution timeout on long AI chains — n8n has a default execution timeout (configurable via
EXECUTIONS_TIMEOUT). Agentic workflows that chain multiple LLM calls can exceed this limit, causing the execution to terminate mid-run without an error message. Increase the timeout or split the workflow into sub-workflows triggered by Execute Workflow nodes. - Binary data too large for workflow — n8n passes data between nodes in memory. Workflows processing large files (PDFs, images, audio for transcription) can exhaust the node process memory limit. Use the n8n Binary Data filesystem mode instead of memory mode, configured via
N8N_DEFAULT_BINARY_DATA_MODE=filesystem. - Memory exhaustion on self-hosted — Running n8n with many concurrent AI workflow executions on a small VM causes the Node.js process to run out of heap memory and crash. Increase the VM's RAM, set
NODE_OPTIONS=--max-old-space-size=4096in your environment, or enable queue mode to spread executions across multiple worker processes.
🔔
Stop manually checking — get alerts instead
Star n8n on Prismix and get emailed the moment status changes. Free, no credit card.
Monitor related AI automation tools?
Full status dashboard: prismix.dev/status