# How to Monitor n8n Uptime

> n8n is a workflow automation tool that lets you connect apps and services with visual, node-based workflows. It can be self-hosted or used via n8n Cloud.

*Source: https://monitoristic.com/monitor/n8n*

---

## Why Monitor n8n?

When you self-host n8n, your workflows are only as reliable as your n8n instance. If the server goes down, every automation stops silently — no errors, no alerts, just workflows that quietly don't run. The tasks you automated to be hands-off become the tasks failing without anyone noticing.

## What to Monitor

- `your-n8n-instance.com` — Your n8n editor/UI URL
- `your-n8n-instance.com/healthz` — n8n's built-in health endpoint
- `your-n8n-instance.com/webhook/your-webhook-path` — A production webhook endpoint your workflows depend on

## What You Should Actually Do

1. Monitor your n8n instance URL and its /healthz endpoint — a running container doesn't mean a running n8n process
2. Monitor a key production webhook endpoint — workflows can fail even when the editor UI loads
3. Configure auto-restart (systemd, Docker restart policy, or your orchestrator) — then monitor to verify it actually recovers
4. Watch for disk-full from execution logs — a common silent n8n failure; set up log pruning and monitor for the symptoms
5. Use an alert channel independent of n8n — don't route your n8n downtime alert through an n8n workflow

## n8n's Official Status Page

n8n publishes real-time status at https://status.n8n.io. Your own monitor complements it by catching connection-level issues, often before the status page updates.

## Takeaway

The entire promise of n8n is automation that runs without you watching it. That's also its biggest risk: when a self-hosted instance goes down, the workflows fail silently and the problems pile up unnoticed. External monitoring is the watchful eye that automation removes — it tells you the moment your automation engine stops, so 'set it and forget it' doesn't become 'set it and never know it broke.'

## Frequently Asked Questions

### How do I monitor a self-hosted n8n instance?

Monitor your n8n instance URL and its built-in /healthz endpoint with an external HTTP monitor. Also monitor a key production webhook endpoint your workflows rely on. This catches process crashes, server reboots, and resource issues that stop your automations.

### Does n8n alert me when it goes down?

No. Self-hosted n8n has no built-in alerting for its own availability. If the process crashes or the server reboots without auto-start, your workflows stop silently. External monitoring is the only way to get notified that n8n itself is down.

### Can I monitor n8n Cloud too?

Yes. Monitor your n8n Cloud instance URL and any production webhook endpoints. While n8n Cloud manages the infrastructure, monitoring confirms your specific workflows and webhooks are reachable — and catches issues before they affect your automations.

### How is this different from status.n8n.io?

n8n's status page covers n8n Cloud platform incidents. It says nothing about your self-hosted instance. Process crashes, disk-full conditions, OOM kills, and reboot failures on your own server are specific to your deployment and only external monitoring will catch them.