Railway edge (69.46.46.82) is unreachable from multiple Czech fixed networks
kayapoetcompany
HOBBYOP

3 days 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.

Awaiting User Response$20 Bounty

6 Replies

Railway
BOT

3 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 3 days 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.

kayapoetcompany
HOBBYOP

3 days 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)?


solocommercenl
PROTop 10% Contributor

3 days ago

I am sure this is all related to all the other IP block and connection issue threads from today, even railway.com is not accessible from some providers

I have seen threads where users apps are marked malicious by google safe browsing, Fortinet has blocked multiple edge ip's.

It is a big mess again and Railway should be investigating whats going on and fix it..

image.png

Attachments


tickgetr
HOBBY

3 days ago

Same issue from Belgium: the whole 69.46.46.0/24 range (including railway.com at 69.46.46.46) is unreachable from a Belgian university network on Belnet (AS2611). Home and mobile networks work fine.

Measured on 4 Nov 2026, 09:00-09:40 UTC:

  • DNS resolves correctly.

  • TCP 443 and 80 to addresses in 69.46.46.0/24 time out.

  • TCP 443 to 66.33.22.1 (RLWY-EDGE-01) works from the same network.

  • Traceroute into 69.46.46.0/24:

    5 193.191.2.45 (Belnet)

    7 80.249.208.36 (AMS-IX)

    8 81.20.68.138 (NTT)

    9+ * * * (timeouts)

    The same path to 66.33.22.1 reaches the destination via NTT.

  • RIPEstat: 69.46.46.0/24 is only announced via AS60068 (CDN77), while 66.33.22.0/23 goes via Telia/NTT/Lumen/PCCW. RPKI is valid for both.

  • The same network reached 69.46.46.0/24 normally on 29 Oct.

This looks like the same broken handoff to AS60068 as in this thread and the Hostinger and Brazil threads, so not a local limitation. Could the networking team check the AS60068 path for this range, or also announce it via the same transit as 66.33.22.0/23?


tickgetr

Same issue from Belgium: the whole 69.46.46.0/24 range (including railway.com at 69.46.46.46) is unreachable from a Belgian university network on Belnet (AS2611). Home and mobile networks work fine. Measured on 4 Nov 2026, 09:00-09:40 UTC: - DNS resolves correctly. - TCP 443 and 80 to addresses in 69.46.46.0/24 time out. - TCP 443 to 66.33.22.1 (RLWY-EDGE-01) works from the same network. - Traceroute into 69.46.46.0/24: 5 193.191.2.45 (Belnet) 7 80.249.208.36 (AMS-IX) 8 81.20.68.138 (NTT) 9+ * * * (timeouts) The same path to 66.33.22.1 reaches the destination via NTT. - RIPEstat: 69.46.46.0/24 is only announced via AS60068 (CDN77), while 66.33.22.0/23 goes via Telia/NTT/Lumen/PCCW. RPKI is valid for both. - The same network reached 69.46.46.0/24 normally on 29 Oct. This looks like the same broken handoff to AS60068 as in this thread and the Hostinger and Brazil threads, so not a local limitation. Could the networking team check the AS60068 path for this range, or also announce it via the same transit as 66.33.22.0/23?

solocommercenl
PROTop 10% Contributor

3 days ago

Yes In the Netherlands Railway is not reachable from KPN the largest ISP for now it seems to be limited to KPN business connections

which use Fortiguard (fortinet) and Fortinet has marked multiple Railway IP's as malicious... with no word from Railway support for ours..

I am pretty sure that all these reports and connections isuues that people are having today are related.


3 days ago

I'm sorry users on the Czech fixed networks you described have been unable to reach Railway while mobile connections work. We now have an incident covering external blocks on Railway IPs. Those symptoms are consistent with it.

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 the affected network providers 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 • 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...