3 days ago
My service in US East (Virginia) calls a third-party API that now requires an IP/ASN allowlist. Over the last month the third party's logs show my service's outbound requests coming from AS400940 (Railway) for most deploys, but for one deploy (10 Nov 2026) every request came from a Google Cloud address (34.11.113.145, AS396982). Since the 14 Nov redeploy it's back on AS400940.
- Why did that deploy egress via GCP - is part of US East still on GCP, or routed through it?
-
- On Hobby, is there a way to guarantee the service only egresses from Railway's own ASN (e.g. a specific Metal region)?
-
- If not, is Static Outbound IP on Pro the only guarantee?
I need to set the allowlist by 20 NovMy service in US East (Virginia) calls a third-party API that now requires an IP/ASN allowlist. Over the last month the third party's logs show my service's outbound requests coming from AS400940 (Railway) for most deploys, but for one deploy (10 Nov 2026) every request came from a Google Cloud address (34.11.113.145, AS396982). Since the 14 Nov redeploy it's back on AS400940.
Q1) Why did that deploy egress via GCP - is part of US East still on GCP, or routed through it?
Q2) On Hobby, is there a way to guarantee the service only egresses from Railway's own ASN (e.g. a specific Metal region)?
Q3) If not, is Static Outbound IP on Pro the only guarantee?
I need to set the allowlist by 20 Nov, so a quick pointer would help a lot. so a quick pointer would help a lot.
1 Reply
3 days ago
Within a region, workloads can be placed in different zones, and some of those zones may run on Google Cloud capacity, so a single deploy egressing from a GCP address is consistent with how US East operates today. We cannot confirm from the observed IP alone exactly where that particular deploy ran.
On Hobby there is no way to guarantee egress from AS400940 or any fixed ASN. Choosing a Metal region does not pin a service's workload or outbound traffic to Metal, and the outbound IP and provider network can change on any deployment, so allowlisting AS400940, AS396982, or both is not reliable.
Yes, Static Outbound IPs on Pro is the supported way to get stable egress. You enable it in the service's Settings under Networking, redeploy, and allowlist every IPv4 address assigned for the service's region. Those addresses stay stable while the feature is enabled and the service stays in that region, though they are shared rather than dedicated. If the third party only accepts an ASN-based policy and cannot allowlist those IPs, we cannot provide a guaranteed match for it.
Status changed to Awaiting User Response Railway • 3 days ago