2 hours ago
Railway edge (69.46.46.82) is unreachable from multiple Czech fixed networks
since ~12:50 CET today.
Mobile networks in CZ work fine. DNS resolves correctly.
Traceroute dies right after CDN77 / Core-Backbone in Amsterdam:
8 ae5-2074.ams10.core-backbone.com [81.95.2.138]
9 coreb-ams.cdn77.com [169.150.195.66]
10 vl221.ams-eq6-dist-1.cdn77.com [79.127.194.83]
11 * * * (timeouts until hop 30)
Looks like a broken handoff/peering between Core-Backbone (AS33891) / CDN77 (AS60068)
and Railway in Amsterdam. Affects all Railway services incl. railway.com.
2 Replies
2 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 hours ago
2 hours ago
This seems like a regional issue, which Railway wouldn’t be able to fix.
I’d try proxying your service behind Cloudflare (if you’re using a custom domain), or use a VPN to access the site.
0x5b62656e5d
This seems like a regional issue, which Railway wouldn’t be able to fix. I’d try proxying your service behind Cloudflare (if you’re using a custom domain), or use a VPN to access the site.
an hour ago
Thanks. This worked fine from the same networks just a few days ago, so it
looks like a recent routing change rather than a long-standing regional limitation.
The break is right at the handoff from Core-Backbone/CDN77 to Railway
in Amsterdam (hop 10 is the last responding router before Railway's network).
It affects multiple unrelated Czech networks, so Czech users on fixed lines
likely can't reach any Railway-hosted app. Could someone from the Railway
network team check the peering/route with Core-Backbone (AS33891) / CDN77 (AS60068)?