What happened
On October 20, 2026, n8n had a significant problem starting at 07:16 UTC. It lasted about 38 minutes and was resolved by 07:55 UTC. n8n has since reported the issue as resolved. No detailed cause has been published.
Who this hits and how they usually find out
If your business runs on n8n workflows, an outage like this does not announce itself. There is no pop-up, no email, no red light on your screen. Your automations just stop. The invoices do not go out, the leads do not get routed, the follow-up messages do not send. The first person to notice is often a customer, asking why something did not arrive, or a colleague wondering why a report is missing. By the time that conversation happens, the outage is already over and you are left explaining a gap you did not even know existed.
Why this is especially rough without a technical background
An engineer can pull logs and piece together what stopped and when. A solo operator or a small team usually cannot. There is no error on the screen because the workflow simply did not run. Nothing failed loudly. The work just quietly stopped moving, and the silence looked exactly like everything being fine. That is the hardest kind of problem to catch, because your instinct is to assume things are running until someone tells you otherwise.
Timeline
- 07:16 UTC - n8n starts experiencing a bigger problem.
- 07:55 UTC - n8n reports the issue resolved.
- Total disruption: about 38 minutes.
How a watcher catches this before your users do
NoCrash reads n8n’s public status page every minute. The moment n8n’s own status page flips from working to having trouble, NoCrash sends you a plain-language heads-up, in plain English, sitting next to everything else you build on. You do not have to check anything. You do not have to know what a webhook is.
For an outage like this one, that means you would have known within a minute of n8n’s own public report, not an hour later when a customer asks why their order confirmation never arrived. That gap, between “n8n said something is wrong” and “you found out,” is exactly what gets closed.
NoCrash also watches the things you ship on top of n8n. Your workflows through an API token, and your app through a URL you give it or a small JS snippet. So if something goes quiet on your own side, that surfaces too, separately from whatever the underlying tool is reporting.
To be clear about what this is: NoCrash reads public status pages and watches the specific things listed above. It does not find outages before the tool’s own status page does. It just makes sure you hear about it right away, in words you can act on, without having to go looking.
The authoritative account
n8n has not published an official postmortem link for this event. Check n8n’s status page directly for any updates.