On Mon, Nov 30, 2015 at 06:46:03PM -0700, Doug Royer wrote:
> www.ietf.org was *really slow*,
>
> so I looked up the IP and this is how www.ietf.org is resolving for me:
>
> Hostname: www.ietf.org
> Country: Hong Kong Country Code HK
> Latitude 22.25 Longitude 114.167
> IP Address (IPv6) 2400:cb00:2048:1::6814:155
> (www.ietf.org.cdn.cloudflare-dnssec.net.)
In a world of CDNs with anycast presence, the notional geoIP lookup
is not very informative, traceroute and ping often reveal more
relevant information.
For me:
$ traceroute6 2400:cb00:2048:1::6814:155
...
5 te0-4-0-26.rcr24.jfk01.atlas.cogentco.com 0.785 ms 0.734 ms 0.714 ms
6 be2600.rcr21.ewr02.atlas.cogentco.com 1.563 ms be2601.rcr21.ewr02.atlas.cogentco.com 1.41 ms 1.474 ms
7 2001:550:2:10::5:2 0.959 ms 0.984 ms 0.949 ms
8 2400:cb00:11:1024::c629:ebce 0.884 ms 2400:cb00:11:1024::a29e:3c1a 0.95 ms 2400:cb00:11:1024::6ca2:dae0 0.944 ms
$ ping6 2400:cb00:2048:1::6814:155
16 bytes from 2400:cb00:2048:1::6814:155, icmp_seq=0 hlim=57 time=0.916 ms
16 bytes from 2400:cb00:2048:1::6814:155, icmp_seq=1 hlim=57 time=0.870 ms
16 bytes from 2400:cb00:2048:1::6814:155, icmp_seq=2 hlim=57 time=0.878 ms
16 bytes from 2400:cb00:2048:1::6814:155, icmp_seq=3 hlim=57 time=0.854 ms
...
Which places that anycast server at most ~270 km from NYC, somewhere
in NJ most likely. Your mileage (from Boise Idaho?) may vary.
IPv4 results below:
$ traceroute 104.20.1.85
...
5 te0-4-0-26.rcr24.jfk01.atlas.cogentco.com (154.24.35.193) 0.930 ms
6 be2600.rcr21.ewr02.atlas.cogentco.com (154.54.40.30) 1.513 ms 1.424 ms
7 38.104.44.10 (38.104.44.10) 0.989 ms 1.025 ms 0.978 ms
8 104.20.1.85 (104.20.1.85) 0.980 ms 1.080 ms 0.964 ms
$ ping 104.20.1.85
64 bytes from 104.20.1.85: icmp_seq=0 ttl=57 time=0.973 ms
64 bytes from 104.20.1.85: icmp_seq=1 ttl=57 time=0.988 ms
64 bytes from 104.20.1.85: icmp_seq=2 ttl=57 time=0.992 ms
64 bytes from 104.20.1.85: icmp_seq=3 ttl=57 time=0.961 ms
--
Viktor.