Hi everyone,
I’m hoping someone can help clarify how outbound networking works in Fly.io.
We’re integrating with a third-party service that only accepts connections from a pre-approved source IP address.
Our Fly.io application has a dedicated IPv4 allocated, and we provided that address to the third party for allowlisting. However, requests from our application are still being rejected as if they’re coming from a different source IP.
Before we continue troubleshooting with the third party, we’d like to confirm our understanding of Fly.io’s networking model.
Specifically:
- Does allocating a dedicated IPv4 for an application also mean outbound requests originate from that same IP?
- If not, what is the recommended way to ensure all outbound requests present a single, stable public IP address?
- Is there a separate concept of a dedicated outbound (egress) IP?
- How can we verify the actual public source IP being presented to external services?
- Are there any common configuration issues or networking behaviors that typically cause confusion in IP allowlisting scenarios?
We’re trying to determine whether the issue is on our side or with the third-party allowlist, so any guidance on how Fly.io handles outbound IP addresses would be greatly appreciated.
Thanks in advance!