11 hours ago
Our production PostgreSQL TCP proxy has been unreachable from two separate Hostinger VPS instances since November 4, 2026.
The Railway PostgreSQL service and public TCP proxy show healthy status. TCP connections from both VPS instances time out, but the same endpoint was previously accessible from a different network.
Hostinger is investigating possible routing or filtering issues.
Could a Railway network engineer check whether connections from Hostinger networks are reaching Railway's edge proxy, and whether any filtering or routing issues are affecting the connection?
We have TCP packet captures and MTR reports available to share privately.
This is affecting production sales tracking. Please advise how to escalate this through a private support channel.
2 Replies
11 hours ago
We're sorry for the trouble. This lines up with an ongoing incident, External network blocks affecting access to Railway, which started on November 4 and affects public networking across our regions. A third party has been sending scanning traffic with forged Railway source IPs, and as a result some network providers and security services are blocking Railway IP addresses, so connections from those networks time out before reaching us.
We have contacted network operators, security vendors and abuse database providers to get these blocks removed, and access remains affected from some networks while we are still monitoring. Since Hostinger is already investigating, share the incident notice with them so they can review any blocks on Railway IP addresses and allow legitimate traffic. Connecting from another network may restore access in the meantime.
Status changed to Awaiting User Response Railway • about 11 hours ago
2 hours ago
Installing WARP on the VPS and changing the hostname in the credentials to the WARP IP address solved the problem for me.
Status changed to Awaiting Railway Response Railway • about 2 hours ago