-
Notifications
You must be signed in to change notification settings - Fork 18
Description
Longitude and latitude can be a good start for determining a list of test servers but geographical location doesn't always determine the shortest path between two hosts. Route configuration and availability determine most of the shortest path weights.
For instance, I know by running other tests and talking to network techs at various ISPs the most of our local ISPs hit the Internet backbone in Los Angeles. Compared to the distance to San Francisco, Los Angeles is twice the physical distance from my current location (on the southern Oregon coast). However, I consistently get much better ping times and file transfer rates to hosts in Los Angeles than I do in San Francisco.
Using the speedtest-cli (which is a great tool, by the way, and thank you!) I cannot seem to list or test against anything but what the program finds as the physically closest servers. I tried to search for a list of servers and did find some, but the hosts that I have tried are rejected by the program as "unknown". (ERROR: No matched servers: 5031 -- ERROR: No matched servers: 16974 -- etc.)
Is there a way that --list-all could be implemented so that a person could see all available servers worldwide (probably piped to a file for sorting) in order to choose from current hosts? Better yet, the ability to list current hosts by a hard-coded list of regions/states/countries/...?
Thanks for reading this.
Again, thanks for the tool.
Cheers,
-bob