undefined | Better HN

0 pointszifnab062y ago0 comments

fwiw - our network folks _should_ have fixed this a few weeks ago. Some of the outbound IPs were incorrectly tagged in some of the geoip databases as being in the US when they were not.

0 comments

therein2y ago

I remember asking about this about half a year ago. Back then I was told since Fly can route these IPs to wherever they want in their infrastructure by making simple configuration changes, the line is blurred anyway but GeoIP providers just take the shortcut and resolve to where the company is registered.

I'll try again if the situation is different now.

zifnab06OP2y ago

Inbound IPs use anycast - the IP we give you routes to the nearest fly region and then hits a wireguard tunnel to get to the correct region.

Outbound IPs are tied to the individual host your machine is running on (which is located in a single region). These are tied to a single region, and in some cases, these were resolving to the wrong region in a few of the GeoIP databases. We hopefully fixed this part.

therein2y ago

Thank you, I will try again today. It would unblock deploying my usecase on Fly.

j / k navigate · click thread line to collapse

0 comments

therein2y ago

I'll try again if the situation is different now.

zifnab06OP2y ago

Inbound IPs use anycast - the IP we give you routes to the nearest fly region and then hits a wireguard tunnel to get to the correct region.

therein2y ago

Thank you, I will try again today. It would unblock deploying my usecase on Fly.

j / k navigate · click thread line to collapse