15 days ago
Hello, your shared edge IP 69.46.46.46 (also used by railway.com) was listed on DroneBL on 2026-11-03 17:08 GMT (incident 11637944, class 13 “Automated dictionary attacks”, “brute force attack on honeypot”; https://dronebl.org/lookup?ip=69.46.46.46). Since then, some ISPs that consume this blocklist block the IP, so our service and railway.com itself are unreachable from those networks (ERR_TIMED_OUT). Could you please request delisting from DroneBL and check the source of the traffic? Thank you, Radek
1 Reply
15 days ago
We're sorry for the trouble. This is the External network blocks affecting access to Railway incident, which affects the dashboard on railway.com and public networking in every region. A third party is sending scanning traffic with forged Railway source IP addresses. That traffic does not come from our network, and some network providers and security services have blocked Railway IPs because of it.
We have sent review requests to security vendors and are working with network operators to get the blocks lifted. We don't have an estimated time yet for every affected network to remove its block. In the meantime, you or your users can ask the affected network administrator or ISP to review its rules for Railway IPs and share the incident notice with them. Using another network may work as a temporary way in. Follow updates at the incident page.
Status changed to Awaiting User Response Railway • 15 days ago
8 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 • 8 days ago