4 hours ago
Hello,
Since Nov 4 (morning, UTC+7), our WordPress server (outbound IP 147.79.99.12, Hostinger) can no longer open TCP connections to our Railway services: gaston-backend-production.up.railway.app (69.46.46.116) and lea.verdeko.fr -> 64t2dp1n.up.railway.app (69.46.46.80). curl hangs on "Trying 69.46.46.80:443..." until timeout. The same URLs respond normally from other networks (200 in 0.4 s). Hostinger confirms no outbound restriction on their side.
Is 147.79.99.12 blocked or rate-limited by your edge? Can you lift it?
Thanks.
1 Replies
4 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 4 hours ago
an hour ago
Same issue here since Nov 4 (~13:00 UTC+7). My Node.js app on Hostinger (outbound IP 145.79.9.247) can’t open TCP connections to my Railway Postgres TCP proxy: viaduct.proxy.rlwy.net:22418 (66.33.22.243) and trolley.proxy.rlwy.net:19179 (66.33.22.236) both time out, and railway.com:443 too. From the same server, other hosts on the same ports (portquiz.net 19179/22418/5432/443) connect in ~0.5 s, and backboard.railway.com (Cloudflare) works. Looks like Railway’s edge is dropping traffic from Hostinger IP ranges (145.79.9.247, 147.79.99.12, 62.72.50.156?). Could you lift it? Project: tanwirul-wafa-db.