29 minutes ago
Hi team,
I'm using Static Outbound IPs on my backend service (project: Tensortick-Backend, service: tensortick-backend, production environment, domain api.tensortic.com).
I currently have 3 static outbound IPs assigned:
152.55.180.240
162.220.234.242
152.55.180.241
I'm integrating with a broker API (ProStocks) that requires IP whitelisting, and they can only whitelist a maximum of 2 IPs on their end — they've approved 152.55.180.240 and 162.220.234.242, but will not add the third.
Since traffic is load-balanced randomly across all 3 of my assigned IPs, my login requests to this broker fail whenever the 3rd (unapproved) IP is used — which is roughly 1 in 3 attempts.
Is there any way you can either:
Restrict my service's outbound traffic to only use 2 of my 3 assigned IPs, or
Reassign my static IPs to a smaller pool of exactly 2, or
Suggest another approach on your platform to guarantee outbound requests only ever use a fixed, small set of IPs?
This is blocking a production integration for me. Happy to provide any further account details needed.
Thanks!
1 Replies
28 minutes ago
Static Outbound IPs assigns a fixed set of 3 IPs with traffic balanced across all of them, and there is currently no way to restrict outbound traffic to a subset or reduce the number of assigned IPs. That sounds like a feature request! Can you write up a detailed explanation of your use case and the feature? This way other users can upvote your issue and glob onto it.
You can write your feature request and view the roadmap here ---> https://station.railway.com/roadmap
Status changed to Awaiting User Response Railway • 28 minutes ago