8.8.8.8

MDKza

Senior Member
Joined
May 24, 2012
Messages
785
Reaction score
112
Location
Midstream
Hi all,

I thought these DNS servers were in the US.

Why am i getting local latency?

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=31ms TTL=59
Reply from 8.8.8.8: bytes=32 time=26ms TTL=59
Reply from 8.8.8.8: bytes=32 time=26ms TTL=59
Reply from 8.8.8.8: bytes=32 time=18ms TTL=59

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 31ms, Average = 25ms
 
A tracert ends here google-public-dns-a.google.com [8.8.8.8]
Looks like this is googles DNS.
 
A tracert ends here google-public-dns-a.google.com [8.8.8.8]
Looks like this is googles DNS.
All you had to do was Google it to know it's Google's DNS. Easier than a tracert.
 
Those DNS servers are Google's. They are also cached here for better performance to our region, same applies for YouTube and various other Google services.
 
The 8.8.8.8 service is anycast. This means that there are multiple servers around the world with the same IP address and the Internet routers will (mostly) automatically route to the one that is closest.

The closest instance of 8.8.8.8 to South Africa was in Europe a few weeks ago. It appears that Google has upgraded their South African infrastructure to include a 8.8.8.8 node. I suspect that this has gone live in the last few days but I don't have any data to back that up.
 
The 8.8.8.8 service is anycast. This means that there are multiple servers around the world with the same IP address and the Internet routers will (mostly) automatically route to the one that is closest.

The closest instance of 8.8.8.8 to South Africa was in Europe a few weeks ago. It appears that Google has upgraded their South African infrastructure to include a 8.8.8.8 node. I suspect that this has gone live in the last few days but I don't have any data to back that up.

Yeah, it has. As far as I know it's part of Google's infrastructure in JHB.
 
Noticed it last week. They have setup local nodes and its all about the routing to direct traffic to these new nodes. Awesome of Google making the internet a better place
 
Interesting, i'm sure this was international before

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 101 ms 21 ms 4 ms 154.127.0.0
3 8 ms 9 ms 4 ms 196.46.25.166
4 5 ms 11 ms 5 ms 72.14.239.33
5 5 ms 5 ms 13 ms 8.8.8.8
 
I don't think MTN/Afrihost is aware of this..

>>>>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 10 ms 9 ms 10 ms 105-236-2-65-esr-lo.mtnbusiness.co.za [105.236.2.65]
3 11 ms 10 ms 10 ms 41.181.221.250
4 10 ms 10 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 13 ms 12 ms 11 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
6 193 ms 193 ms 192 ms 41.181.180.10
7 209 ms 208 ms 208 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 193 ms 193 ms 216 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
9 192 ms 192 ms 192 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
10 209 ms 208 ms 208 ms 216.239.47.223
11 193 ms 193 ms 193 ms 216.239.47.159
12 193 ms 192 ms 194 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
 
Noticed it last week. They have setup local nodes and its all about the routing to direct traffic to these new nodes. Awesome of Google making the internet a better place

Traffic sniffing....?
 
Google peers at teraco in jhb. Any ISP can peer with them. Your IPs get flagged as ZA, then if your isp peers with google the Google dns servers will resolve the query to the nearest local node.
 
Traffic sniffing....?

Its not sniffing its just routing. The ISPs update their routing tables accordingly. As per some previous post it seems MTN/AH have not done so yet so traffic on their network destined for 8.8.8.8 is still going overseas.
 
I've opened a support ticket with Afrihost to investigate why it's still routing internationally with them. Would rather switch over to Google DNS if it now has local latency.
 
Just for the fun of things, from different ISP's in alphabetical order (From Durban)

Afrihost:

michael@michael-desktop:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.443 ms 0.621 ms 0.817 ms
2 * * *
3 41.181.221.213 (41.181.221.213) 29.263 ms 31.965 ms 33.622 ms
4 41.181.221.214 (41.181.221.214) 35.117 ms 37.544 ms 39.745 ms
5 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 43.238 ms 45.955 ms 47.913 ms
6 xp-dca-1.za--xp-cr-1.za-a.mtnns.net (196.44.0.155) 256.648 ms rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 259.109 ms 277.680 ms
7 ct-cr-2.za--rb-cr-1.za.mtnns.net (196.44.31.68) 96.961 ms 99.286 ms jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 285.847 ms
8 ls-cr-2.uk--rb-cr-1.za-g.mtnns.net (196.44.31.114) 280.915 ms 283.349 ms tb-cr-1.za--ct-cr-2.za.mtnns.net (196.44.31.135) 109.440 ms
9 ls-cr-2.uk--rb-cr-1.za-g.mtnns.net (196.44.31.114) 288.014 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 297.374 ms 299.815 ms
10 ls-pr-2.uk--ls-cr-1.uk-a.mtn.net (209.212.111.203) 286.439 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 288.766 ms google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 225.796 ms
11 216.239.47.219 (216.239.47.219) 227.077 ms 216.239.47.207 (216.239.47.207) 226.666 ms google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 226.024 ms
12 216.239.47.221 (216.239.47.221) 226.906 ms 216.239.47.53 (216.239.47.53) 225.617 ms 216.239.43.173 (216.239.43.173) 227.161 ms
13 216.239.47.53 (216.239.47.53) 210.126 ms google-public-dns-a.google.com (8.8.8.8) 228.679 ms 209.85.255.167 (209.85.255.167) 212.852 ms
michael@michael-desktop:~$

Cell C:

michael@michael-desktop:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.43.1 (192.168.43.1) 3.048 ms 5.532 ms 5.789 ms
2 * * *
3 41.50.20.1 (41.50.20.1) 255.688 ms 255.938 ms 255.792 ms
4 10.220.231.70 (10.220.231.70) 131.684 ms 146.895 ms 147.038 ms
5 41.50.16.1 (41.50.16.1) 131.239 ms 130.929 ms 138.842 ms
6 41.50.0.3 (41.50.0.3) 139.368 ms 129.679 ms 129.787 ms
7 41.50.1.5 (41.50.1.5) 130.205 ms 125.267 ms 125.000 ms
8 41.48.253.38 (41.48.253.38) 124.665 ms 117.424 ms 116.906 ms
9 google.jb1.napafrica.net (196.46.25.166) 116.214 ms 118.391 ms 118.665 ms
10 72.14.239.53 (72.14.239.53) 114.538 ms 72.14.239.35 (72.14.239.35) 140.314 ms 72.14.239.33 (72.14.239.33) 102.720 ms
11 google-public-dns-a.google.com (8.8.8.8) 114.155 ms 114.019 ms 113.906 ms
michael@michael-desktop:~$

Crystal Web:

michael@michael-desktop:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.458 ms 0.726 ms 0.920 ms
2 * * *
3 196.6.121.197 (196.6.121.197) 31.776 ms 34.794 ms 36.995 ms
4 196.6.121.198 (196.6.121.198) 38.236 ms 41.163 ms 43.375 ms
5 72.14.220.38 (72.14.220.38) 48.611 ms 50.015 ms 52.969 ms
6 72.14.239.35 (72.14.239.35) 54.233 ms 72.14.239.117 (72.14.239.117) 24.972 ms 72.14.239.35 (72.14.239.35) 27.514 ms
7 google-public-dns-a.google.com (8.8.8.8) 29.788 ms 32.686 ms 34.647 ms
michael@michael-desktop:~$

Telkom Mobile

michael@michael-desktop:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 172.17.48.9 (172.17.48.9) 32.325 ms 32.312 ms 32.338 ms
3 * * *
4 192.168.102.2 (192.168.102.2) 152.303 ms 152.290 ms 152.331 ms
5 172.17.48.17 (172.17.48.17) 120.316 ms 120.303 ms 120.313 ms
6 8ta-150-179-01.telkomadsl.co.za (41.150.179.1) 120.374 ms 88.161 ms 88.128 ms
7 ndn-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.7.73) 88.002 ms 95.772 ms 95.793 ms
8 rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za (196.43.52.38) 118.058 ms 118.112 ms 118.099 ms
9 72.14.212.1 (72.14.212.1) 117.922 ms 117.864 ms 86.093 ms
10 72.14.239.53 (72.14.239.53) 86.217 ms 72.14.239.117 (72.14.239.117) 173.856 ms 72.14.239.33 (72.14.239.33) 118.238 ms
11 google-public-dns-a.google.com (8.8.8.8) 118.107 ms 95.939 ms 95.818 ms
michael@michael-desktop:~$

Web Africa:

michael@michael-desktop:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.476 ms 0.601 ms 0.792 ms
2 * * *
3 196.38.74.246 (196.38.74.246) 114.680 ms 118.995 ms 119.970 ms
4 cdsl1-umh-gi0-0-0-3102.ip.isnet.net (196.38.74.245) 121.425 ms 126.067 ms 126.798 ms
5 cdsl1-umh-bd150.ip.isnet.net (196.26.210.192) 129.740 ms 131.208 ms 134.379 ms
6 mi-za-umh-p7-ten-0-0-0-1.ip.isnet.net (168.209.93.203) 137.855 ms mi-za-umh-p8-ten-0-0-1-1.ip.isnet.net (168.209.93.204) 107.473 ms 109.616 ms
7 mi-za-bry-p7-lo0.ip.isnet.net (168.209.255.208) 127.973 ms 128.595 ms 129.575 ms
8 mi-za-bry-p7-lo0.ip.isnet.net (168.209.255.208) 134.538 ms core2a-bry-gi0-0-0.ip.isnet.net (168.209.217.2) 134.056 ms mi-za-bry-p7-lo0.ip.isnet.net (168.209.255.208) 139.938 ms
9 168.209.100.205 (168.209.100.205) 141.643 ms core2a-bry-gi0-0-0.ip.isnet.net (168.209.217.2) 144.101 ms 168.209.100.205 (168.209.100.205) 145.099 ms
10 196.26.0.130 (196.26.0.130) 147.033 ms 168.209.100.205 (168.209.100.205) 151.241 ms core2a-pkl-te1-2.isnet.net (168.209.100.241) 119.039 ms
11 72.14.205.16 (72.14.205.16) 119.284 ms 118.120 ms 121.433 ms
12 72.14.239.33 (72.14.239.33) 122.237 ms 72.14.205.16 (72.14.205.16) 119.414 ms 123.194 ms
13 72.14.239.33 (72.14.239.33) 119.984 ms 72.14.239.35 (72.14.239.35) 119.686 ms 72.14.239.117 (72.14.239.117) 120.952 ms
14 google-public-dns-a.google.com (8.8.8.8) 121.429 ms 122.424 ms 120.418 ms
michael@michael-desktop:~$
 
Discovered this last night when a ping to 8.8.8.8 on WA suddenly gave me a 30ms result instead of the normal 100-200ms. Was quite surprised to see the whole traceroute giving me local pings. Gives a whole new meaning to the world is getting smaller.
 
Top
Sign up to the MyBroadband newsletter
X