I pick an IP at random from:
Miner ID: f01414711 IP: 61.10.9.11
Without looking at a GeoIP lookup database, like Maxmind GeoLite2, I can still do a traceroute from multiple locations.
I actually am renting cheap VPS machines in Quebec, Frankfurt and Singapore, so let's use those:
From Quebec:
# traceroute 61.10.9.11
traceroute to 61.10.9.11 (61.10.9.11), 30 hops max, 60 byte packets
1 ipfs-libp2p-tcp.default.svc.cluster.local (15.235.47.12) 0.052 ms 0.012 ms 0.008 ms
2 15.235.44.1 (15.235.44.1) 0.458 ms 0.416 ms 0.396 ms
3 192.168.143.254 (192.168.143.254) 0.379 ms 0.360 ms 0.342 ms
4 10.69.223.190 (10.69.223.190) 0.326 ms 0.310 ms 0.293 ms
5 10.69.223.64 (10.69.223.64) 0.321 ms 0.324 ms 0.507 ms
6 10.69.192.10 (10.69.192.10) 0.491 ms 10.69.192.4 (10.69.192.4) 0.401 ms 10.69.192.6 (10.69.192.6) 0.234 ms
7 10.34.1.50 (10.34.1.50) 0.487 ms 10.34.1.46 (10.34.1.46) 0.561 ms 10.34.1.48 (10.34.1.48) 0.525 ms
8 10.74.8.82 (10.74.8.82) 0.210 ms 10.74.9.92 (10.74.9.92) 0.227 ms 10.74.8.82 (10.74.8.82) 0.190 ms
9 10.95.81.10 (10.95.81.10) 1.204 ms 10.95.81.8 (10.95.81.8) 1.663 ms 4.595 ms
10 * * *
11 10.200.3.1 (10.200.3.1) 4.061 ms 10.200.3.5 (10.200.3.5) 4.024 ms 10.200.3.1 (10.200.3.1) 4.602 ms
12 * * *
13 be2090.ccr22.ymq01.atlas.cogentco.com (154.54.45.117) 4.413 ms 4.287 ms 4.247 ms
14 be3259.ccr31.yyz02.atlas.cogentco.com (154.54.41.205) 8.633 ms be3260.ccr32.yyz02.atlas.cogentco.com (154.54.42.89) 8.503 ms be3259.ccr31.yyz02.atlas.cogentco.com (154.54.41.205) 8.558 ms
15 be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225) 15.521 ms be2994.ccr22.cle04.atlas.cogentco.com (154.54.31.233) 14.855 ms be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225) 15.406 ms
16 be2718.ccr42.ord01.atlas.cogentco.com (154.54.7.129) 26.015 ms 25.929 ms be2717.ccr41.ord01.atlas.cogentco.com (154.54.6.221) 25.840 ms
17 be2832.ccr22.mci01.atlas.cogentco.com (154.54.44.169) 42.634 ms 42.570 ms 35.644 ms
18 be3036.ccr22.den01.atlas.cogentco.com (154.54.31.89) 67.846 ms be3035.ccr21.den01.atlas.cogentco.com (154.54.5.89) 69.843 ms 128.196 ms
19 be2668.ccr22.elp02.atlas.cogentco.com (154.54.87.29) 78.943 ms 81.459 ms be2427.ccr21.elp02.atlas.cogentco.com (154.54.87.21) 81.327 ms
20 be2667.ccr21.elp01.atlas.cogentco.com (154.54.87.26) 81.306 ms 81.225 ms be2669.ccr21.elp01.atlas.cogentco.com (154.54.87.66) 81.163 ms
21 be2929.ccr31.phx01.atlas.cogentco.com (154.54.42.65) 81.124 ms 78.173 ms 78.282 ms
22 be2931.ccr41.lax01.atlas.cogentco.com (154.54.44.86) 78.214 ms 78.111 ms 78.177 ms
23 be2327.ccr21.hkg02.atlas.cogentco.com (154.54.0.6) 226.818 ms 227.709 ms 227.619 ms
24 154.18.9.106 (154.18.9.106) 228.069 ms 228.021 ms 227.993 ms
25 * * *
26 * * *
27 * * *
28 * * *
29 cm61-10-9-11.hkcable.com.hk (61.10.9.11) 229.225 ms 228.970 ms 229.804 ms
From Frankfurt:
# traceroute 61.10.9.11
traceroute to 61.10.9.11 (61.10.9.11), 30 hops max, 60 byte packets
1 ipfs-libp2p-tcp.default.svc.cluster.local (141.95.103.122) 0.060 ms 0.024 ms 0.022 ms
2 141.95.100.1 (141.95.100.1) 0.113 ms 0.075 ms 0.077 ms
3 192.168.143.254 (192.168.143.254) 0.093 ms 0.065 ms 0.094 ms
4 10.13.125.62 (10.13.125.62) 0.275 ms 0.222 ms 0.207 ms
5 10.13.122.214 (10.13.122.214) 0.283 ms 10.13.122.212 (10.13.122.212) 0.231 ms 10.13.122.214 (10.13.122.214) 0.161 ms
6 10.13.127.194 (10.13.127.194) 0.183 ms 10.13.118.28 (10.13.118.28) 0.241 ms 10.13.127.198 (10.13.127.198) 0.233 ms
7 10.17.244.98 (10.17.244.98) 0.645 ms 10.17.244.112 (10.17.244.112) 0.529 ms 10.17.244.108 (10.17.244.108) 0.704 ms
8 10.73.40.62 (10.73.40.62) 0.173 ms 10.73.40.104 (10.73.40.104) 0.174 ms 10.73.40.62 (10.73.40.62) 0.142 ms
9 * 10.73.249.66 (10.73.249.66) 3.972 ms *
10 fra-fr5-sbb1-nc5.de.eu (91.121.215.116) 2.127 ms fra-fr5-sbb2-nc5.de.eu (94.23.122.246) 1.564 ms 2.051 ms
11 10.200.0.13 (10.200.0.13) 2.603 ms 2.650 ms 2.053 ms
12 * * *
13 be2846.ccr42.fra03.atlas.cogentco.com (154.54.37.29) 1.816 ms 2.611 ms 2.607 ms
14 be2800.ccr42.par01.atlas.cogentco.com (154.54.58.238) 11.132 ms 11.098 ms 11.182 ms
15 be2779.ccr31.mrs02.atlas.cogentco.com (154.54.72.110) 21.913 ms 21.880 ms be2780.ccr32.mrs02.atlas.cogentco.com (154.54.72.226) 21.841 ms
16 be2899.ccr21.hkg02.atlas.cogentco.com (154.54.0.42) 244.912 ms 244.870 ms 244.822 ms
17 154.18.9.106 (154.18.9.106) 246.381 ms 259.542 ms 246.503 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 cm61-10-9-11.hkcable.com.hk (61.10.9.11) 247.449 ms 259.859 ms 259.657 ms
From Singapore:
# traceroute 61.10.9.11
traceroute to 61.10.9.11 (61.10.9.11), 30 hops max, 60 byte packets
1 ipfs-libp2p-udp.default.svc.cluster.local (139.99.73.156) 0.041 ms 0.011 ms 0.010 ms
2 139.99.72.1 (139.99.72.1) 0.115 ms 0.073 ms 0.051 ms
3 192.168.143.254 (192.168.143.254) 0.102 ms 0.079 ms 0.062 ms
4 10.29.219.126 (10.29.219.126) 0.247 ms 0.265 ms 0.239 ms
5 10.29.193.128 (10.29.193.128) 0.292 ms 10.29.193.130 (10.29.193.130) 0.243 ms 0.237 ms
6 10.133.3.102 (10.133.3.102) 0.628 ms 10.133.2.106 (10.133.2.106) 0.532 ms 0.685 ms
7 10.75.0.10 (10.75.0.10) 0.203 ms 10.75.0.12 (10.75.0.12) 0.306 ms 0.280 ms
8 10.75.248.4 (10.75.248.4) 0.642 ms 10.75.248.2 (10.75.248.2) 0.766 ms 10.75.248.4 (10.75.248.4) 0.572 ms
9 sin-sg1-sbb1-nc5.sgp.asia (103.5.15.4) 4.244 ms sin-gss1-sbb1-nc5.sgp.asia (103.5.15.16) 2.527 ms sin-sg1-sbb1-nc5.sgp.asia (103.5.15.4) 4.204 ms
10 10.200.0.196 (10.200.0.196) 1.800 ms 0.946 ms 0.951 ms
11 103.203.158.125 (103.203.158.125) 36.559 ms 36.518 ms 36.449 ms
12 * * *
13 * * *
14 * * *
15 cm61-10-9-11.hkcable.com.hk (61.10.9.11) 34.726 ms 35.960 ms 34.587 ms
As you can see, the traceroute from Singapore has the lowest latency. You can also guess from the reverse DNS name of the final route that the destination is in Hong Kong.
A really nice tool is "Rich Traceroute". https://rich-traceroute.io/
Paste in the output from any of the above traces to get a nice version with links to RIPEStat for each hop, which makes it easy to see which networks/locations the packets are traversing.