Hi Railway team,

I'm integrating my Railway‑hosted app with a third‑party financial data provider (Fundata) whose API is IP‑allowlisted — it only accepts requests coming from a fixed public IP that I register with them in advance. To make this work I need to know my service's outbound IP and whether it's stable.

My setup:

Project/service: dwm-kyp (deploys kypmanager.ca, port 3000)

Region: US West (California)

My questions:

What is the current outbound (egress) IPv4 address that my service's requests originate from?

Is that egress IP static/stable, or can it change across deploys, restarts, or infrastructure moves?

If it is not static, does Railway offer a static / dedicated outbound IP option — on my current plan, or via an upgrade (e.g. Pro)? If so, how do I enable it and what does it cost?

If Railway does not provide a static egress IP, what do you recommend for connecting to an IP‑allowlisted third‑party API (e.g. routing outbound traffic through a static‑IP egress proxy)?

The provider's allowlist is IPv4‑only, so an IPv4 answer is what I need. Thanks very much for your help.

Best regards,

Brett