What happened
On September 30, 2026, n8n reported a bigger problem starting at 16:53 UTC. It lasted about two minutes and was marked resolved at 16:55 UTC. n8n has not published a detailed account beyond confirming the issue is resolved.
Who this kind of outage hits and how they usually find out
If you run workflows on n8n, a short outage like this can be invisible until something downstream goes wrong. A form submission does not trigger a follow-up email. A customer record does not get created. An invoice does not go out. You find out not because n8n told you, but because a customer writes in asking why nothing happened. By then the window has passed, the moment is awkward, and you are piecing together what broke from memory. That is the shape of most automation outages: quiet on your end, loud on the customer’s end.
Why this is especially rough without a technical background
There is no error on your screen. There is no log to open. The workflow just did not run, and nothing told you that. If you are not an engineer, you do not have a place to look. You might not even know something went wrong until a task that should have taken minutes has been sitting untouched for hours. The first signal is often an unhappy person on the other end of whatever your workflow was supposed to do. Two minutes sounds short, but if a time-sensitive trigger fired in that window, the work simply did not happen.
Timeline
- 16:53 UTC, September 30, 2026 - n8n reports a bigger problem begins.
- 16:55 UTC, September 30, 2026 - n8n marks the issue resolved.
- Total duration - about 2 minutes.
How a watcher catches this before your users do
n8n publishes a public status page. NoCrash reads that page every minute. The moment n8n flips from working to having trouble, NoCrash sends you a plain-language message saying something is wrong, in words you can act on without being an engineer. You do not have to go looking. It sits next to everything else you build on, so you are not checking five different status pages yourself.
NoCrash also watches the things you ship. If you have n8n workflows connected through an API token, NoCrash watches those too, so a quiet stall on your own side surfaces alongside any platform-level trouble. Same goes for your app, through a URL or a small JS snippet you add once.
The honest limit: NoCrash reads n8n’s own public status page. It catches the trouble within a minute of n8n’s own report. It does not find the outage before n8n does. But it means you hear about it in plain English, right away, instead of from a frustrated customer.
No official source link is available for this outage at the time of writing. Check n8n’s status page directly for the authoritative account.