a month ago
Our service runs in asia-southeast1 (Singapore). Since Oct 13, 2026 ~18:37 UTC, some deployments get egress IPs from 152.55.188.0/24 (seen: .8, .22, .38, .59, .82). Public geo databases (e.g. ipinfo.io) place this range in San Francisco, US, while your other Singapore egress ranges (208.77.246.0/24, and GCP 34.x/35.x) correctly geolocate to Singapore.
Because of this, APIs that geo-restrict the US (Binance returns HTTP 451 "restricted location") reject all requests from these IPs. Redeploying until we land on a 208.77.246.x or 34.x/35.x IP works around it, but every deploy is a gamble.
Could you either (a) submit a geolocation correction for 152.55.188.0/24 to the major geo-IP providers (MaxMind, ipinfo, IP2Location), or (b) avoid assigning this range to asia-southeast1 services until it geolocates correctly?
Project region: asia-southeast1. Happy to share deployment IDs if useful.
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Thanks for the detailed report. I understand the impact this is having on your deployments. We won’t be coordinating geolocation corrections with third-party providers or excluding this range from Singapore’s egress pool as part of this request.
Custom networking work can only be considered under an Enterprise agreement, with the scope and commitments agreed in advance.
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago