What happened
On September 21, 2026, n8n reported a bigger problem starting at 09:35 UTC. It lasted about four minutes and was marked resolved at 09:39 UTC. n8n has since confirmed the disruption is over. The window was short, but four minutes is enough for queued runs to stall and for anything time-sensitive to miss its moment.
Who this kind of outage hits and how they usually find out
If you run workflows on n8n, you probably are not watching its status page while you work. Most people are not. So when something goes wrong, the first signal is often a customer asking why their confirmation email never arrived, or a colleague wondering why the report did not show up this morning. That gap, between the moment the tool stopped working and the moment someone told you, is the rough part. It is not your fault. There is just no obvious alarm.
Why this is especially hard without an engineering team
When you are running a business on automation and something goes quiet, there is no error on your screen. No red light. The workflow just does not run, and you find out when the silence causes a problem downstream. An engineer might have logs to check. A solo operator or a small team usually has a customer complaint and a sinking feeling. The work stopped moving and nobody told you until it was already someone else’s problem.
Timeline
- 09:35 UTC – n8n reported a bigger problem.
- 09:39 UTC – n8n marked the issue resolved.
- Total duration – about 4 minutes.
How a watcher catches this before your users do
NoCrash reads n8n’s public status page every minute. The moment n8n flips from working to having trouble on that page, NoCrash sends you a plain-language message. Not a status code, not a raw alert. A sentence you can read and act on, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches them through your API token. If you have an app or a site, you can give NoCrash a URL or drop in a small JS snippet and it will watch that too. So a quiet stall on your own side surfaces the same way.
To be clear about what this is: NoCrash reads what n8n itself reports. It does not find the outage before n8n’s own status page does. What it does is make sure you hear about it in plain English, within a minute of n8n’s own report, instead of hearing about it from a frustrated customer an hour later.
Official source
n8n’s own status page is the authoritative record for this outage. No direct link is available for this event, so check n8n’s status page directly for their account of what happened.