Skip to content
My IP 217.21.78.209 cannot reach the TCP proxy or *.up.railway.app since Nov 4
iboostsocial
OP

17 days ago

My VPS at Hostinger (IP 217.21.78.209, Phoenix) has not been able to reach Railway over TCP since November 4, 2026, between 1:00 and 3:00 a.m. Mexico City time (07:00–09:00 UTC).

The public TCP proxy of my Postgres (service attached) times out from that IP. The previous proxy, which I already recreated, also times out.

An app of mine on *.up.railway.app (69.46.46.16) also times out.

cdn77.com and backboard.railway.com respond fine from the same IP.

From other networks my database works. From Railway, my VPS is reachable on port 22.

A TCP mtr to the proxy reaches railwaycorp-ic-390075.ip.twelve99-cust.net (Arelion/Telia) and there is no reply after that. The mtr output is pasted below.

Could you check whether 217.21.78.209 is blocked or rate-limited by an anti-abuse filter or connection limit, or whether there is a return-path problem toward that block? My production n8n instance cannot write to my database and I am losing leads and payments. This is urgent. Thank you.

Solved

2 Replies

Railway
BOT

17 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 17 days ago



16 days ago

I'm sorry the connection failures from your Hostinger VPS are interrupting n8n writes to Postgres and affecting leads and payments. The proxy and public application timing out from that server while working from other networks are consistent with our external blocking incident.

We've confirmed that a third party is sending scanning traffic using forged Railway source IP addresses. That traffic does not originate from our network. Railway's infrastructure, including our networking, is fully operational. We're in the process of contacting ISPs, security vendors, and abuse database providers to have the resulting false blocks and reputation listings corrected.

It would also help if you could share the incident notice with Hostinger and ask them to allowlist Railway's affected IP ranges for legitimate connections to your services.

Please follow the incident page for further updates. Access from individual networks may remain affected until their blocks are lifted.


Status changed to Awaiting User Response Railway • 16 days ago


Railway
BOT

9 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 9 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...