I am facing a critical issue with my n8n Cloud instance. Suddenly, ALL of my workflows have stopped working and are failing with a DNS resolution error.
Error Message:
“The DNS server returned an error, perhaps the server is offline” (or EAI_AGAIN / getaddrinfo).
Details:
Environment: n8n Cloud (hosted by n8n)
Scope of problem: Every single workflow that makes external HTTP requests, connects to databases, or uses APIs is completely blocked by this DNS error.
Since this is a managed n8n Cloud instance, I don’t have access to server-side Docker or network/DNS settings to fix it myself. It looks like the DNS resolver on the host machine/container network has crashed or is misconfigured.
Could an administrator please check my instance and restart the network stack or the underlying container?
Hi @Sber Welcome!
EAI_AGAIN is a resolver timeout rather than a missing domain, and when it hits every destination at once, the resolver on your instance is the thing failing, not the targets. This forum is community-run, so nobody here can reach into your workspace and restart it.
Force a redeploy yourself first, since that moves the workspace onto a fresh container with a fresh resolver: open https://app.n8n.cloud/manage, select Manage, then Workspace, pick a different version in the n8n version dropdown and select Change version. It restarts in 1 to 2 minutes. Update your version | Deploy | n8n Docs
If the DNS errors come straight back after it boots, email help@n8n.io with your instance URL, two or three failed execution IDs with their timestamps, and the fact that every workflow is affected, not one domain.
Support routes and what to put in the request: Where to Get n8n Help: Forum, Discord, GitHub & Support Channels - n8n Guide
Since you are on a managed service, you must escalate this to the official n8n support team immediately.
Include the following in your ticket:
Subject: CRITICAL: DNS Resolution Failure (EAI_AGAIN) on Cloud Instance
Instance URL:https://newsaccount.app.n8n.cloud
Error Details: Provide the exact error: EAI_AGAIN / getaddrinfo.
Scope: Explicitly state that all workflows making external requests (HTTP, Database, API) are failing, which confirms it is a global networking issue for your instance, not a specific node configuration.
Request: Ask them to check the DNS resolver status for your container/host and potentially restart the instance/network stack.
When you contact them, you can provide this technical summary to speed up their triage:
“The instance is experiencing a total loss of DNS resolution. All outbound requests are failing with EAI_AGAIN. This appears to be a failure of the DNS resolver within the container network or the host’s upstream DNS configuration. Please investigate the networking stack for the instance newsaccount.app.n8n.cloud.”