Hey, I recently setup a static egress ip (due to external app whitelist). My app is in frankfurt. However the egress was assigned in the US.
This fly.io forum post says its just the IP lookup misrepresenting the region, however this definitely isn’t the case. The website i’m making requests to, region bans the US, and after adding the static egress it started failing (it didn’t in Frankfurt).
Is there anything I can do here? Our app is latency sensitive and adding this static egress adds ~300ms.
Our IP addresses sometimes have incorrect GeoIP data. The IPs themselves are actually located in that region—so your traffic isn’t being routed all the way to the US—but they may appear otherwise due to outdated records. We’re aware of the issue and plan to fix it a some point.
This doesn’t seem right. We hit a german based external API that when using the static IP increased latency by 300ms. Seems like its doing a big re-route.