16 days ago
The Railway site + my own site hosted on Railway are not reachable from my office WiFi. Confirmed both are fine on my phone's 5G. Webpass IP 136.24.123.138 can't reach 69.46.46.0/24 since about 10:00–12:00 UTC on Nov 4. 66.33.22.x is reachable, and the path dies after Arelion hop 62.115.203.26.
3 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 is a routing problem between Webpass and Railway, not something on your side. Several networks have been hitting it since Nov 4. Your IP 136.24.123.138 is Webpass (AS19165). Your last responding hop, 62.115.203.26, reverse-resolves to datacamp-ic-392894.ip.twelve99-cust.net, which is Arelion's (AS1299) handoff to DataCamp/CDN77. So traffic from Webpass toward 69.46.46.0/24 goes Arelion → CDN77 and dies there. 66.33.22.0/23 still works because it's a different Railway prefix (both are AS400940) that's apparently routed another way. Your phone's 5G works because the carrier takes a different path.
1. Check whether any 69.46.46.x IPs get through. Run this from the office network:
for ip in 69.46.46.0 69.46.46.5 69.46.46.46 69.46.46.113; do
curl -s -o /dev/null -m 8 -w "$ip %{http_code}\n" \
--resolve yourapp.up.railway.app:443:$ip https://yourapp.up.railway.app/ || echo "$ip timeout"
doneIf one connects, pin your hostname to it in /etc/hosts for now and remove the line once the route is fixed.
2. Workaround for your own site: put a custom domain on it, proxy it through Cloudflare (orange cloud, SSL/TLS Full), and office traffic will reach Railway through Cloudflare instead of the broken path. This only works for HTTP. A TCP proxy record has to stay DNS-only, so it won't help there. For railway.com itself, use 5G or a VPN until the route is fixed.
3. Escalate: send Webpass the output of mtr -T -P 443 -r -c 50 69.46.46.46, your IP, and the start time (Nov 4, ~10:00–12:00 UTC). Ask them to check their route to AS400940 through Arelion/CDN77, and post the same output here so Railway can check their side.
AI disclosure: I used AI to help draft this answer. I checked myself that 136.24.123.138 is Webpass (AS19165), that 62.115.203.26 is Arelion (AS1299) and reverse-resolves to the DataCamp interconnect name above, that 69.46.46.0/24 and 66.33.22.0/23 are both Railway's AS400940, and that railway.com resolves to 69.46.46.46. I could not test the route from a Webpass connection.
16 days ago
Railway's IP's are being marked as malicious in multiple countries by multiple ISP's there are a lot of threads and similar reports
by a lot of users but no response from railway yet. It has been going on for hours now..
16 days ago
I'm sorry your office's Webpass connection can't reach railway.com or your site while 5G works. That network-specific access failure is 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 Webpass 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