a month ago
Hi Railway team,
My service was deployed in Southeast Asia (asia-southeast1-eqsg3a) since April without issues. Starting with a redeploy on 2026-10-18 ~01:05 UTC, every outbound request to Binance returns HTTP 451 ("Service unavailable from a restricted location") and to Bybit HTTP 403 ("The Amazon CloudFront distribution is configured to block access from your country"), even on public endpoints. The redeploy at 00:57 UTC the same day, same region and same code, worked fine.
Egress IPs observed in the Singapore region after that: 152.55.188.35 and 152.55.188.43. Both ipinfo.io and ip-api.com geolocate them as San Francisco, US (AS400940 Railway).
Sampling one IP per /24 of AS400940's announced prefixes, the whole 152.55.188.0/22 block shows up as San Francisco, while other Railway ranges geolocate correctly: 208.77.246.0/23 = Singapore (SG); 152.55.184.0/22 = Amsterdam (NL), a block that was also reported as San Francisco ~5 months ago in https://station.railway.com/questions/451-http-error-code-sudainely-appeared-d498fca0 and is correct now; 152.55.176.0/22 and 152.55.180.0/22 = Santa Clara / Ashburn (US).
As a workaround I moved the service to EU West: egress 152.55.184.248 geolocates to NL and both exchanges respond 200 again.
Request: could you publish/correct the geofeed (RFC 8805) for 152.55.188.0/22 so it maps to Singapore, and ask the GeoIP providers (MaxMind, ipinfo, IP2Location) to update it? Also, are Static Outbound IPs in Southeast Asia allocated from 208.77.246.0/23 or from 152.55.188.0/22?
Thanks!
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
This looks like a Railway egress GeoIP-classification issue rather than an application or Binance/Bybit bug.
There is now a very close Railway thread from the same Singapore region (asia-southeast1-eqsg3a) with outbound IPs 152.55.188.42 / 152.55.188.6:
https://station.railway.com/questions/singapore-hosted-services-using-us-geolo-6b81f3d3
Railway staff confirmed there that:
- the Southeast Asia region is physically in Singapore;
- third-party GeoIP databases can classify Railway egress addresses as US even though the workload is in Singapore;
- Railway does not have a supported way to guarantee an outbound IP is geolocated as Singapore by external providers;
- that limitation also applies to Pro Static Outbound IPs, so upgrading specifically to fix Binance/Bybit GeoIP classification is not guaranteed to help.
The public region docs also map asia-southeast1-eqsg3a to Singapore:
https://docs.railway.com/deployments/regions
For the Static Outbound IP question: Railway documents that Pro services receive region-tied static outbound IPv4 addresses, but the assigned addresses are shown per-service after enabling the feature; Railway does not publish a supported shared/static CIDR mapping that would let us conclude that SEA static IPs come specifically from 208.77.246.0/23 rather than 152.55.188.0/22:
https://docs.railway.com/networking/static-outbound-ips
So I would not rely on either prefix as the guaranteed SEA static pool.
Given your evidence (redeploy boundary + two 152.55.188.x addresses + EU West immediately restoring 200 responses), the practical options today appear to be:
- keep the workload/egress in a region whose current IPs are accepted by the exchanges (your EU West workaround);
- use a separately controlled egress/proxy with a known Singapore address if Singapore-origin classification is a hard requirement;
- keep this Railway thread open for Railway/networking to correct or reassign the affected
152.55.188.0/22infrastructure, but there is no documented customer-side setting that fixes the GeoIP record.
I would treat Static Outbound IPs as useful for stability/allowlisting, not as a GeoIP-correction mechanism.
a month ago
AI-use disclosure: I used AI assistance to help research and draft the previous reply, then manually reviewed the claims against Railway’s current docs and the linked Railway staff response before posting.