Skip to content
Hostinger blocks Railway IPs 66.33.22.0/24 and 69.46.46.0/24 ("bad reputation") – TCP proxy unreachable from my VPS
jan14kl
OP

16 days ago

My Postgres TCP proxy (reseau.proxy.rlwy.net:20941 → 66.33.22.224) is unreachable

from my VPS at Hostinger (Frankfurt) since 4 Nov 2026, ca. 09:00 CET. Also

69.46.46.23 (my *.up.railway.app domain) is unreachable from there.

Hostinger support confirmed: both IPs are blocked by Hostinger's firewall due to

"bad reputation / possible link to earlier fraudulent activity". They won't unblock

them and told me to contact the provider.

From everywhere else it works (check-host.net TCP check: Frankfurt, Paris,

Vienna, US, Asia all connect; my home network too). So it's only Hostinger's network.

Questions:

  1. Is Railway aware that these shared IP ranges are flagged by Hostinger?
  2. Can I get a TCP proxy on a different / cleaner IP range, or a dedicated IP?
  3. Any recommended workaround for connecting an external n8n host to the DB?

Thanks!

Solved

3 Replies

Railway
BOT

16 days ago

Yes, we're aware. This matches an open incident: a third party is sending scanning traffic with forged Railway source IP addresses, which has led some network providers and security services to block Railway IPs. That traffic does not come from our network, and it is not a sign that your services or Railway infrastructure were compromised. We're working with providers and security vendors to get those blocks removed and reputation listings corrected, but access can stay affected on individual networks until each block is lifted: External network blocks affecting access to Railway.

For now, the most useful step is to send that incident notice to Hostinger and ask them to review their block on Railway IPs. They can allow your legitimate connections and keep their protection against unsolicited scanning. Until the block is lifted, connecting from a different network will give you temporary access.


Status changed to Awaiting User Response Railway • 16 days ago


Railway

Yes, we're aware. This matches an open incident: a third party is sending scanning traffic with forged Railway source IP addresses, which has led some network providers and security services to block Railway IPs. That traffic does not come from our network, and it is not a sign that your services or Railway infrastructure were compromised. We're working with providers and security vendors to get those blocks removed and reputation listings corrected, but access can stay affected on individual networks until each block is lifted: [External network blocks affecting access to Railway](https://status.railway.com/incident/QBCLHG1V). For now, the most useful step is to send that incident notice to Hostinger and ask them to review their block on Railway IPs. They can allow your legitimate connections and keep their protection against unsolicited scanning. Until the block is lifted, connecting from a different network will give you temporary access.

jan14kl
OP

16 days ago

Thanks for confirming. I've sent the incident notice to Hostinger and asked them to

lift the block, but they have not done so yet.

Meanwhile I'm bridging via a tunnel, so this is not urgent for me anymore.

However, I'd like a human at Railway to take a look:

  1. Is there an ETA or any direct contact with Hostinger on your side? Hostinger's

    support said it won't unblock on its own ("bad reputation") and sent me back to

    Railway as the provider.

  2. Could you contact Hostinger (AS47583) directly about the block on

    66.33.22.0/24 and 69.46.46.0/24?

  3. Please keep this thread open until the block is lifted.

Affected service: Postgres, project KI-Firma (TCP proxy reseau.proxy.rlwy.net:20941).

Thanks!


Status changed to Awaiting Railway Response Railway • 16 days ago


16 days ago

Thanks for sharing Hostinger's response and for confirming that your tunnel is keeping the Postgres connection working. We understand you're asking Railway to address the reputation-based blocks affecting both the TCP proxy and public edge. We're taking this up from our side too.

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...