16 days ago
I'm reporting a possible network routing or connectivity issue affecting Railway.
Railway's website (railway.com) and my Railway-hosted application have stopped loading from networks in Arlington, Texas, despite previously working normally.
Observations:
- My personal laptop connected to Wi-Fi cannot access Railway.
- A separate computer on a wired network experiences the same problem.
status.railway.comand other websites remain accessible.- A computer in another city in Texas, using a different network, can access Railway normally.
Network diagnostics:
- DNS server: (
45.90.30.231) railway.comcorrectly resolves to69.46.46.46.- TCP connection to
69.46.46.46:443fails. Test-NetConnectionreturnsTcpTestSucceeded: False.- Ping times out.
I found two potentially related reports:
- https://station.railway.com/questions/railway-servers-inaccessible-across-regi-41a72291
- https://station.railway.com/questions/custom-domain-fails-tls-handshake-on-the-7063ee18
My issue differs from the second report because the TCP connection itself fails before the TLS handshake.
Could you investigate whether Railway is experiencing routing or connectivity issues affecting 69.46.46.46 from certain networks?
Thank you.
4 Replies
16 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 16 days ago
16 days ago
This seems like an ISP or network configuration/firewall issue.
Unfortunately, if that's the case, Railway isn't able to fix this. Your options would be to reach out to your ISP, check your network configuration, or use a VPN.
If you have a custom domain, you can try using Cloudflare's proxy, though you'd need to migrate to Cloudflare's DNS for that.
0x5b62656e5d
This seems like an ISP or network configuration/firewall issue. Unfortunately, if that's the case, Railway isn't able to fix this. Your options would be to reach out to your ISP, check your network configuration, or use a VPN. If you have a custom domain, you can try using Cloudflare's proxy, though you'd need to migrate to Cloudflare's DNS for that.
16 days ago
This looks like part of the same reachability issue being reported today. The Arlington tests fail on TCP port 443 to 69.46.46.46, the same Railway edge IP reported blocked on KPN in the Netherlands. A Hostinger customer also reported that Hostinger confirmed an outbound firewall block to 69.46.46.0/24 based on abuse reports. And a user on Belgium’s Belnet reported that the entire /24, including railway.com, was unreachable from their university network while home and mobile connections worked. KPN report · Hostinger confirmation · Belnet report
The Arlington timeout alone leaves the cause open, but the same IP and range keep coming up across different networks. Could Railway’s networking team compare the Arlington diagnostics with the other reports and tell us what it finds? Where a provider has confirmed a block, can Railway work directly with that provider to restore access?
16 days ago
Your DNS is fine. 69.46.46.0/24 is Railway's own edge range (ARIN name RLWY-HIKARI-01, announced by AS400940 RAILWAY), and railway.com resolving there is correct. 45.90.30.231 is NextDNS (AS34939), and it is answering correctly. Since the TCP connect itself fails from two machines on the same network, while another Texas network works, the likely cause is the route between your ISP and Railway's edge (or a filter on that path). It is probably not your devices, DNS, or your app. Railway has since acknowledged external network blocks affecting access and says it has found the cause and is working on a fix, so this may clear on its own. The steps below confirm it and give you a workaround in the meantime.
1. Prove it's the path (2 minutes)
- Turn on a phone hotspot or VPN on the same laptop and open railway.com. If it loads, the problem is your network's path.
- If you use the NextDNS app or a router profile, pause it for a minute and test again. That rules out blocking on the client side.
2. Gather evidence (Windows PowerShell)
Test-NetConnection 69.46.46.46 -Port 443 -InformationLevel Detailed
tracert -d 69.46.46.46
pathping -n 69.46.46.46
curl.exe -v https://railway.com -o NULOn macOS/Linux, run mtr -rwzbc 100 -T -P 443 69.46.46.46 (the -T needs sudo). The hop where the trace stops tells you which network is dropping the packets. Railway also offers an official NetDiag tool for macOS and Windows that collects this for support: https://docs.railway.com/networking/troubleshooting/network-diagnostics
3. Escalate
Post the NetDiag report or traceroute here, with your public IP and ISP name, and send the same data to your ISP. If the trace dies inside the ISP or at its upstream handoff, only the ISP or Railway's network team can fix the peering or route. A support ticket with the trace in hand gets resolved much faster.
4. Workaround for your app's users
Put the custom domain behind Cloudflare's proxy (orange cloud). Visitors then connect to Cloudflare, and Cloudflare reaches Railway over its own route. Railway's docs say to set SSL/TLS to Full, not Full (Strict): https://docs.railway.com/networking/troubleshooting/ssl. This doesn't help you reach railway.com itself. For the dashboard, use a hotspot or VPN until the route is fixed.
I used AI to help draft this; the RDAP/ASN data, Railway's incident notice and doc links were checked before posting.
16 days ago
I'm sorry both railway.com and your application have been inaccessible from the Arlington networks you tested. Those TCP failures, alongside successful access from another Texas network, are consistent with the symptoms covered by our external network 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 your network provider 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
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