What happened
On September 30, 2026, n8n reported a bigger problem starting at 16:19 UTC. The disruption lasted about 27 minutes and was marked resolved at 16:47 UTC. n8n has not published a detailed account beyond confirming it is resolved.
Who this kind of outage hits and how they usually find out
If you run workflows on n8n, a 27-minute gap in the middle of the day can mean orders not processed, leads not routed, notifications not sent. The tool goes quiet and nothing inside it shouts at you. Most operators find out the same way: a customer writes in asking why something did not happen, or they check a spreadsheet later and notice a row that should be there is missing. By then the disruption is over, but the damage to trust is already done.
Why this is especially rough without a technical background
When something breaks in a tool you build on, an engineer can pull logs and see exactly where things stopped. If you are not an engineer, there are no logs to read. The screen looks normal. Your workflow is just sitting there, not running, and nothing tells you why. The first real signal is often an unhappy customer or a missed deadline. That gap, between when the tool stopped working and when you found out, is where the problem lives.
Timeline
- 16:19 UTC - n8n reports a bigger problem begins.
- 16:47 UTC - n8n marks the issue resolved.
- Total duration - about 27 minutes.
How a watcher catches this before your users do
NoCrash reads n8n’s public status page every minute. The moment n8n’s own page flips from working to having trouble, NoCrash sends you a plain-language heads-up, in words you can act on, without you having to go check anything yourself. That does not mean NoCrash knows before n8n does. It means you hear about it within a minute of n8n’s own report, instead of an hour later when a customer asks why their confirmation email never arrived.
NoCrash also watches the things you ship on top of n8n. You can give it a URL for your app or drop in a small JS snippet, and it watches your n8n workflows directly through an API token. So if your own side goes quiet for a reason that has nothing to do with n8n’s status page, that surfaces too. Everything sits in one place, in plain English, not scattered across tabs you have to remember to check.
For the authoritative account of this outage, check n8n’s official status page directly, as no external source link is available for this event.