Hey @vasallius and @redjonzaci—the default region in flyctl prompts is the region that your ISP sends your traffic to, which is determined by whatever your ISP considers the “best” path to the Fly.io network. That “best” path is decided by a fairly complicated process, and while it often leads to the Fly.io region closest to you geographically (or with the best ping times), that’s not always the case.
@vasallius you can visit debug.fly.dev and check the Fly-Region header printed there to verify that you’re being routed to ams. (Amsterdam is a significant Internet hub, so I wouldn’t be surprised to see traffic getting sent there. Here’s another example of that happening.)
If you’re able to provide a traceroute to debug.fly.dev, we can sometimes work with our network providers to try to improve the routing.