RSS request Blocked

Questions
1

Describe the problem/error/question

Getting 503 error in RSS Feed node: I have tried with RSS node and HTTP request, but it is blocking both kind of requests;
I am using n8n Pro, is there any way I can get some request routing or IP change or anything so google will not block me, I were blocked even I haven’t send much requests, still in development phase, the gap of each request is 2-3 minutes and I just sends only 4 request at a time.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

{
“errorMessage”: “Status code 503”,
“errorDetails”: {},
“n8nDetails”: {
“nodeName”: “RSS - AI General”,
“nodeType”: “n8n-nodes-base.rssFeedRead”,
“nodeVersion”: 1.2,
“itemIndex”: 0,
“time”: “4/28/2026, 1:11:37 PM”,
“n8nVersion”: “2.17.5 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeOperationError: Status code 503”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/RssFeedRead/RssFeedRead.node.ts:148:12)“,
" at processTicksAndRejections (node:internal/process/task_queues:104:5)”,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1048:9)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1239:11)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1687:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2339:11"
]
}
}

Information on your n8n setup

  • n8n version: 2.17.5
  • Database (default: SQLite): no idea using n8n cloud
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows
3

I believe you have hit a rate limit.

Here is a breakdown of why 503 happens and how it relates to rate limits:

503 Due to Rate Limiting (Server Overload)
When a server receives too many requests at once (exceeding a rate limit), it may become overloaded and return a 503 error to protect itself

How to Fix It

Retry with Exponential Backoff: Wait a few seconds, then try again, increasing the wait time with each failed attempt.

Reduce Rate: Slow down the frequency of your requests.

If all these does not help, the IP is most likely being blocked

5

@peace google news blocks datacenter IPs aggressively, no amount of headers or backoff will fix it on cloud — the 503 isn’t rate limiting, it’s a flat IP block. route it through rss2json which fetches the feed from their own IPs and returns clean JSON:

rss2json free tier gives you 10k requests/day, each item comes back with title, link, pubDate etc in $json.items — the Split Out node breaks them into individual items so you can process each article downstream.