15 days ago
Hi,
We run production services on Railway in the US West region, and they make outbound HTTPS calls to a third-party API. That API now requires an IP allowlist, so we need to know whether our outbound traffic will consistently come from Railway's own network.
Could someone confirm:
- Is outbound traffic from services in US West expected to stay within Railway's own network?
- Can outbound traffic move to other providers' networks, such as AWS, without notice?
- Is there a way to pin outbound traffic to Railway's network, or to get static outbound IPs on the Hobby plan?
Thanks,
Alan
1 Reply
15 days ago
Without Static Outbound IPs, we don't guarantee which addresses your outbound traffic uses, so it isn't a reliable basis for an IP allowlist. The supported option for allowlisting is Static Outbound IPs, which gives a service permanent outbound IPv4 addresses for its region. That feature is only available on the Pro plan, and there isn't a way to pin outbound addresses on Hobby.
On Pro, you turn it on with the Enable Static IPs toggle in the Networking section of the service's settings, then redeploy. The assigned addresses stay the same unless you move the service to another region. They may be shared with other customers, and they can't be used for inbound traffic.
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