I, too, see this problem, you can see why it happens from here: https://github.com/AirVPN/Eddie/blob/master/src/Lib.Core/PingManager.cs
I'm afraid that the whole design is wrong (I hope I am wrong but...). The ping values are biased by buffer bloat, ISP configuration, order of the "parallel" pings, and by how the threads are (not) managed, so it's the whole concept of how "parallel pings" are managed in Eddie that could be flawed. If you make a small list of favorite servers around your location the problem is still there but at least the order of the server is more or less correct. You prevent Eddie to connect to some server at the other end of the world. This option also helps if you set it to 1:
but I can't see it in the GUI. Maybe I miss it, maybe it's another option that's available only in command line mode and not from the GUI (it happens in Eddie ). The documentation discloses an awkward confusion between jobs and threads and maybe this part of code has been written by different persons without a proper overview. I think it should be extensively revised but it's not trivial at all how to solve it from the current code for me, I'm sorry I think I can't help here.