N8n Cloud: Persistent DNS resolution failure (EAI_AGAIN) on HTTP Request node. 7 consecutive days

Questions
1

Describe the problem/error/question

I’m experiencing a persistent DNS resolution failure on n8n Cloud that is preventing my production workflow from executing.
My workflow makes a GET request to https://api.open-meteo.com/v1/forecast via an HTTP Request node. Every scheduled execution fails with a DNS error. This has been happening every day from 16 June to 22 June (7 consecutive days), all at 08:15.
I have restarted and updated my n8n instance. The issue persists.
The endpoint is a publicly accessible API with no authentication required and is reachable from other platforms. The error indicates a DNS resolution failure on n8n Cloud infrastructure rather than the target server being offline.

What is the error message (if any)?

Error: getaddrinfo EAI_AGAIN api.open-meteo.com
Code: EAI_AGAIN
Message: The DNS server returned an error, perhaps the server is offline
Node: HTTP Request (v4.4)

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.26.8
  • Database (default: SQLite): n8n Cloud
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Main
  • Running n8n via: n8n Cloud
  • Operating system:
2

Hi @Korban Welcome!
I believe that you can enable retry on fail on the HTTP node immediately. This issue is well-known and typically resolves itself within a few hours. However, in your case, it is persistent. To address this, please contact help@n8n.io and provide the following information: the name of your workspace/instance, the affected workflow, the exact execution times (08:15 daily, June 16–22), and the execution IDs of the failed runs. As it is impossible to modify instance-level settings on n8n cloud.

3

Thanks for the quick reply.

I’ve already emailed help@n8n.io with all of those details: workspace name, workflow ID, execution times, and the failed execution IDs.

The HTTP Request node is also already set to retry on fail (3 retries at 5000ms), but the DNS resolution is failing consistently so the retries don’t help in this case. All 3 attempts fail with the same EAI_AGAIN error.

Hopefully the support team can look into what’s going on with the DNS on the Cloud workers.