Problems detecting nearest servers

[SuperKali]

I've noticed that quite often apt.armbian.com, dl.armbian.com, and occasionally other mirrors do not recognize that I'm geographically close to armbian.atomonetworks.com. Instead, they randomly select servers that are farther away. The issue appears to be entirely random.

For example, when downloading an image from the website, it took me three attempts before the download actually used the closest server.

Here's a test I performed: link.

Do you think this is something we can address?

[tystuyfzand]

It depends on how many servers are actually nearby, the redirector chooses the top 3 servers and then chooses from those for every subsequent request.

Perhaps there's some tuning we can do that adds a reasonable maximum distance from the closest to next closest mirrors to avoid something like this? Or even add CDN-hosted variants to pad local ones in these cases?

Edit: And also an endpoint to list which servers it chose, as well as all server distances to debug issues like this?

[SuperKali]

@tystuyfzand the server is very close, I'm 16 km from the server but I rarely reach it anyway because it always takes a far away server

[SuperKali]

I also analyzed the requests coming from armbian.atomonetworks.com I noticed that there are requests from all over the globe, and as if it chose randomly, the logic is slightly wrong, at most if the closest server is down, it should choose the closest and most available one, I don't know if there is a way to do it also through a check of the latencies between the client and the server or review the selection logic

[tystuyfzand]

Not really a reasonable way to check latencies which is why geo-routing isn't the greatest but it works. I'm saying that it's choosing the top 3 servers, no matter if they're far or close, so it may be taking servers from 2000km away just because of it being the "next closest" in the list.

[SuperKali]

There’s no way to fix it?