Hello Railway team,

My Spring Boot backend is deployed on Railway EU West and was previously running without issue.

Since recently, outbound calls from this EU West deployment to Binance public API started failing with HTTP 451, which causes my service to crash during initialization.

The endpoint tested from inside the Railway deployment is:

https://api.binance.com/api/v3/time

Observed behavior:

• Railway EU West deployment → Binance endpoint returns HTTP 451
• Railway Asia deployment → same Binance endpoint returns HTTP 200
• My personal computer in Spain or France → same Binance endpoint returns HTTP 200

The Railway EU West deployment appears to use the following outbound IP:

152.55.184.21

According to IPinfo.io, this IP is geolocated/classified as San Francisco, United States, even though the service itself is deployed in EU West.

Could you confirm whether this IP is indeed the outbound IP used by my Railway EU West service, and whether EU West services can currently route outbound traffic through IPs classified as US-based?

This matters because Binance APIs are restricted from the US, and the HTTP 451 seems consistent with the request being seen as US-originated rather than EU-originated.

I’m trying to understand what Railway-side options exist to keep the service deployed in Europe while ensuring outbound requests also appear as EU-based.

Thanks.