This is part of the incident you referenced, which is still open as "External network blocks affecting access to Railway". Access remains affected from some networks that are blocking Railway IP addresses because a third party is sending scanning traffic with forged Railway source addresses. That traffic does not come from our network. We have submitted review requests to security vendors and are working with network operators to restore legitimate access, but we don't have an estimated time yet for every affected network to remove its blocks.

Because the path stops inside CDN77/DataCamp, the block can only be lifted on their side. Your provider can share the incident notice with that transit network so it can review the rule and allow legitimate traffic to 69.46.46.0/24 while still blocking unsolicited scanning traffic. Until then, connecting through a different network or upstream path may give you temporary access.