-1
When I traceroute
some servers I notice that the path taken is not geographically ideal:
I am in the UK's South-West.
My request goes into London, then annoyingly goes North of London (to Leicester) for 2 hops and returns to London before going to Europe.
How do I get my requests to this address to take a more efficient route?
I realise now that locating IP addresses geographically is not extremely accurate, so in fact the path may not look like this.
However, is there a way I can more directly access servers to try to decrease latency?
The only hop that has significant latency for me is my first one to my ISP's edge router xD – theonlygusti – 2017-04-09T23:55:01.980
Thanks for such an informative and comprehensive answer though, +1 – theonlygusti – 2017-04-09T23:55:26.937
1It's also worth noting that in periods of congestion or poor network optimization the fastest route could also be one that is geographically sub-optimal. If the packet might take 10ms to go the direct route, due to contention and heavy load, but only 7.5ms for the roundabout route then it would be better to take that path. – Mokubai – 2017-04-10T06:38:34.323