Is n8n down or not working?

What happened to n8n, why did the service go down and not work? Here you can see who else is having the same problem with n8n, as well as possible solutions. According to our statistics, the following most often do not work: Login, Server Connection, Website.

Current status: No failures

At the moment, according to our data, n8n is working fine, but single failures are possible. If n8n does not work for you, then report your problem and write a comment.
Add comment

n8n outage reports in the last 24 hours

User reports by hour (UTC), last 24 hours

Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0

Total weight in 24 hours: 0 Busiest hour: 23:00 UTC (weight 0)

How this score compares

Current 24-hour weight is 0. Warnings start at 20, Failed at 50. Median services on this language today is 0.

Other services in this category

Official links

  • Facebook: https://www.facebook.com/108289464093301
  • Twitter: http://www.twitter.com/n8n_io

Facts

Official website n8n.io
Started 2019
Country Germany

About n8n

n8n is a low-code automation tool and open-source software, first released in 2019. It was founded by Jan Oberhauser and is based in Berlin, Germany. The project's website is https://n8n.io, and it is also known as n8n.io and nodemation.
n8n is a low-code automation tool used to connect apps, scripts, and services into workflows. When it stops working, the usual suspects are failed logins, nodes that cannot reach external APIs, or the web editor not loading. This status page tracks reported problems across those areas. If your workflows suddenly stall or a connection breaks, check here first before digging through logs on your own instance.
n8n lets you build automation workflows with a visual editor and a bit of code where needed. You link triggers to actions, passing data between apps and services. Many teams run it on their own server, others use the hosted cloud version. Common issues fall into a few groups. Login problems can lock you out of the editor or an API key can expire. Server connection faults appear when n8n cannot reach an external service, so a node fails mid-run and the workflow stops. The website or editor itself may load slowly or refuse to respond. If something breaks, start on your side. Confirm your credentials and API keys are still valid. Check whether the failing node is the problem or the workflow as a whole. Self-hosted users should verify their instance is running and has network access. If all of that looks fine, the fault may sit with n8n or an upstream service.

Questions

Is n8n down right now?

According to reports on this page, n8n looks fine for most people. Isolated failures still happen — report yours if you are stuck.

When was the last mass outage?

We do not have a recorded mass outage for n8n yet.

Why does my workflow fail partway through?

Most partial failures come from a node that cannot reach an external service, or from credentials that have expired. Open the failed execution, check which node errored, and confirm your API keys and connection settings are still valid.

What is the difference between the cloud version and self-hosting?

The cloud version is maintained by n8n and runs on their infrastructure, so platform-side issues show up on this status page. A self-hosted instance runs on your own server, so availability depends on your setup, and only login or connection problems tied to n8n itself would appear here.

n8n - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.