On the morning of July 13, 2026, n8n had a significant disruption. It started at 08:59 UTC and was resolved by 09:18 UTC, about 19 minutes later. n8n has since reported the issue as resolved.
Who this kind of outage hits
If you run automations on n8n, a 19-minute window where things stop working can quietly swallow a batch of runs. The problem is that nothing inside n8n sends you a message saying “your workflows are not running right now.” Most operators find out the wrong way: a customer emails asking why their order confirmation never arrived, or a colleague notices a report that was supposed to land at 9 AM still hasn’t shown up at noon. By then the disruption is over, but the damage, the missed trigger, the stalled queue, the confused customer, is already done.
Why this is especially rough without a technical background
If you are not an engineer, there is no log file to open, no error screen to read. The work just stops moving. Your workflow was supposed to fire and it did not, and from the outside everything looks fine. The first real signal is often an unhappy person on the other end of whatever that workflow was supposed to do. That gap between “something broke” and “I found out” is where the pain lives.
Timeline
- 08:59 UTC - n8n begins experiencing a bigger problem.
- 09:18 UTC - n8n reports the issue resolved.
- Total duration - about 19 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 translates that into plain English and sends you a heads-up. You hear about it within a minute of n8n’s own report, not an hour later when a customer complains.
That matters because the gap between “n8n posted a status update” and “you found out” is usually filled with nothing. Most people are not refreshing a status page at 08:59 on a Monday morning. NoCrash also watches your own side: your specific n8n workflows through an API token, and your app through a URL or a small JS snippet you give it. So if something goes quiet on your end specifically, that surfaces too, sitting next to everything else you build on. It does not replace n8n’s own status page. It just makes sure you actually see what that page says, in words you can act on, before your users do.
For the authoritative account of this outage, check n8n’s official status page directly, as no specific incident link is available for this event.