12 days ago
Hi Railway team,
We're on the Pro plan and need the static outbound (egress) IPs for one of our services — a payment partner is enforcing an IP allowlist on their API with a hard block starting June 29, so we must give them our fixed egress IPs.
Service details:
Workspace: pavelsolntsev111's Projects
Project: kartli (14d2136d-290a-49f4-9bb0-6add5ea62962)
Environment: production (3c0b27e1-b98b-43e4-b7a3-a80bc9b2c2a6)
Service: app-git (c0702280-e0a9-446d-b29e-b25a7564093c)
Current observed egress IP: 54.215.16.125
Could you please:
Confirm whether Static Outbound IPs is enabled for this service (we've toggled it in Settings → Networking and redeployed) — or enable it if needed.
Provide the full list of static outbound IPv4 addresses assigned to this service (all of them, for its region) so we can submit them to our partner.
Confirm these IPs are stable and only change if we move the service to another region.
Confirm that all outbound traffic from this service egresses via these IPs, with no fallback to a shared pool.
Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 12 days ago
12 days ago
You can enable static outbound IPs in your service settings in the networking section. And yes, the IPs are static and will only change if you deploy in a different region.