Your help needed: Please ping www.Google.co.za

rpm

Admin
Staff member
Joined
Jul 22, 2003
Messages
66,805
Reaction score
5,057
Location
Johannesburg
Some people said they get local pings for Google...it will be great if you can ping www.Google.co.za and give your results here (please include the network that you use).
 
Pinging google.co.za [64.233.179.104] with 32 bytes of data:

Reply from 64.233.179.104: bytes=32 time=801ms TTL=50
Reply from 64.233.179.104: bytes=32 time=841ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=945ms TTL=50

Ping statistics for 64.233.179.104:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 801ms, Maximum = 945ms, Average = 862ms

Not too good. :erm:

(Mweb 384 uncapped)
 
Internet Solutions

Pinging google.co.za [64.233.179.104] with 32 bytes of data:

Pinging www.l.google.com [64.233.179.104] with 32 bytes of data:
Reply from 64.233.179.104: bytes=32 time=193ms TTL=46
Reply from 64.233.179.104: bytes=32 time=193ms TTL=46
Reply from 64.233.179.104: bytes=32 time=204ms TTL=46
Reply from 64.233.179.104: bytes=32 time=189ms TTL=46

Ping statistics for 64.233.179.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 189ms, Maximum = 204ms, Average = 194ms
 
MWEB Uncapped

Pinging www.l.google.com [209.85.229.147] with 32 bytes of data:
Reply from 209.85.229.147: bytes=32 time=293ms TTL=51
Reply from 209.85.229.147: bytes=32 time=297ms TTL=51
Reply from 209.85.229.147: bytes=32 time=296ms TTL=51
Reply from 209.85.229.147: bytes=32 time=295ms TTL=51

Ping statistics for 209.85.229.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 293ms, Maximum = 297ms, Average = 295ms

Hmmm, how come I get a different server IP address?
 
Last edited:
Local on IS local 30gb purchased @WA.

C:\Users\ms>ping www.google.co.za

Pinging www.l.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=27ms TTL=58
Reply from 196.23.168.147: bytes=32 time=28ms TTL=58
Reply from 196.23.168.147: bytes=32 time=27ms TTL=58
Reply from 196.23.168.147: bytes=32 time=27ms TTL=58

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Still on Intl when using WA cap.

EDIT: Yesterday I could also access google reader on it. Same for youtube. Today no. But google search still works OK on IS local.

EDIT2: Reddit.com is hosted on akamai
 
Last edited:
WA 30GB MyBB special

Pinging www.l.google.com [64.233.179.104] with 32 bytes of data:
Reply from 64.233.179.104: bytes=32 time=357ms TTL=52
Reply from 64.233.179.104: bytes=32 time=357ms TTL=52
Reply from 64.233.179.104: bytes=32 time=358ms TTL=52
Reply from 64.233.179.104: bytes=32 time=358ms TTL=52

Ping statistics for 64.233.179.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 357ms, Maximum = 358ms, Average = 357ms
 
IS Business ADSL
ping www.google.co.za

Pinging www.l.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=570ms TTL=59
Reply from 196.23.168.147: bytes=32 time=22ms TTL=59
Reply from 196.23.168.147: bytes=32 time=20ms TTL=59
Reply from 196.23.168.147: bytes=32 time=56ms TTL=59

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 570ms, Average = 167ms


tracert www.google.co.za

Tracing route to www.l.google.com [196.23.168.147]
over a maximum of 30 hops:

1 ...:)
2 ...:)
3 ...:)
4 ...:)
5 40 ms 46 ms 97 ms csw3-pkl-gi1-2.ip.isnet.net [168.209.1.201]
6 66 ms 18 ms 20 ms za196-23-168-147.cache.googlevideo.com [196.23.168.147]

Trace complete.
 
Last edited:
I have fooled my system to permanently use the local servers for all searching (modify your hosts file)
c:\windows\system32\drivers\etc\hosts >>open with notepad and add the following lines to it, as this will change your DNS lookups to perma use local, Note however that the results will be returned, but if you do not have Int bandwidth some pages will not open
196.23.168.147 www.google.co.za
196.23.168.147 www.google.com

Code:
C:\Users\***>ping www.google.co.za

Pinging www.l.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=31ms TTL=57
Reply from 196.23.168.147: bytes=32 time=28ms TTL=57
Reply from 196.23.168.147: bytes=32 time=30ms TTL=57
Reply from 196.23.168.147: bytes=32 time=28ms TTL=57

Ping statistics for 196.23.168.147:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 31ms, Average = 29ms
 
Last edited:
IS Business DSL:

Pinging www.l.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=108ms TTL=58
Reply from 196.23.168.147: bytes=32 time=90ms TTL=58
Reply from 196.23.168.147: bytes=32 time=92ms TTL=58
Reply from 196.23.168.147: bytes=32 time=40ms TTL=58

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 108ms, Average = 82ms
 
Afrihost 384

Pinging www.l.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=68ms TTL=57
Reply from 196.23.168.147: bytes=32 time=73ms TTL=57
Reply from 196.23.168.147: bytes=32 time=67ms TTL=57
Reply from 196.23.168.147: bytes=32 time=59ms TTL=57

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 73ms, Average = 66ms
 
Thanks for the feedback so far - looks like all IS clients access Google.com/Google.co.za locally while others are still routed internationally.
 
It depends on the DNS server that you're using.

I've forced the following hostnames to the local IP address on my MikroTik RB750:

www.l.google.com
www.google.com
mail.google.com
chatenabled.mail.google.com​

Now I can access Gmail on local cap :D

The 168.210.2.2 (IS DNS server) reports the local Google IP for www.google.co.za!

Our office is running on MWeb Business uncapped and it reported the international IP address, so we overrided the DNS entries on our router at the office too.
 
root@lin-laptop:~$ ping www.google.co.za
PING www.l.google.com (209.85.227.104) 56(84) bytes of data.
64 bytes from wy-in-f104.1e100.net (209.85.227.104): icmp_seq=1 ttl=45 time=491 ms
64 bytes from wy-in-f104.1e100.net (209.85.227.104): icmp_seq=2 ttl=45 time=415 ms
64 bytes from wy-in-f104.1e100.net (209.85.227.104): icmp_seq=3 ttl=45 time=437 ms
64 bytes from wy-in-f104.1e100.net (209.85.227.104): icmp_seq=4 ttl=45 time=461 ms
^C
--- www.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 415.961/451.612/491.370/28.049 ms

SAIX ADSL
 
I see something very strange with some our DNS servers reporting the following:

Code:
;; QUESTION SECTION:
;www.google.co.za.		IN	A

;; ANSWER SECTION:
www.google.co.za.	14201	IN	CNAME	www.google.com.
www.google.com.		307210	IN	CNAME	www.l.google.com.
www.l.google.com.	8	IN	A	64.233.179.104
Note, I left out the DNS server in question on purpose.


Traceroute.
Code:
C:\Users\Tinuva>tracert 64.233.179.104

Tracing route to cpt01s01-in-f104.1e100.net [64.233.179.104]
over a maximum of 30 hops:

  1    12 ms    <1 ms    <1 ms  router.heaven.za.net [10.0.0.1]
  2    10 ms     9 ms     9 ms  dsl-185-100-1.dynamic.wa.co.za [41.185.100.1]
  3    10 ms    10 ms    10 ms  vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
  4    12 ms    11 ms    11 ms  vl32.er.gw.cpt.za.wa.co.za [41.185.0.26]
  5    10 ms    11 ms    10 ms  upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
  6   172 ms   172 ms   171 ms  196.43.9.54
  7   179 ms   179 ms   178 ms  125-126-245-83.packetexchange.net [83.245.126.125]
  8   192 ms   195 ms   184 ms  209.85.252.76
  9   191 ms   201 ms   191 ms  72.14.232.95
 10   331 ms   331 ms   330 ms  64.233.174.41
 11   360 ms   351 ms   359 ms  64.233.174.105
 12   340 ms   340 ms   340 ms  cpt01s01-in-f104.1e100.net [64.233.179.104]

Trace complete.
 
Last edited:
SAIX via wireless link

U:\>ping www.google.co.za

Pinging www.l.google.com [196.23.168.147] with 32 bytes of data:

Reply from 196.23.168.147: bytes=32 time=376ms TTL=57
Reply from 196.23.168.147: bytes=32 time=272ms TTL=57
Reply from 196.23.168.147: bytes=32 time=123ms TTL=57
Reply from 196.23.168.147: bytes=32 time=282ms TTL=57

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 376ms, Average = 263ms

U:\>

Traceroute done :

Code:
U:\>tracert www.google.co.za

Tracing route to www.l.google.com [196.23.168.147]
over a maximum of 30 hops:

  1    24 ms     1 ms    <1 ms  192.168.50.252
  2   128 ms   142 ms   159 ms  196-46-185-144.aboutit.co.za [196.46.185.144]
  3   146 ms   150 ms   172 ms  196-46-186-21.aboutit.co.za [196.46.186.21]
  4   108 ms   196 ms   172 ms  local-firewall.aboutit.co.za [196.46.184.38]
  5   114 ms   156 ms   350 ms  jinx-rba.aboutit.co.za [196.46.184.27]
  6   207 ms   193 ms    88 ms  168.209.87.69
  7   245 ms   140 ms   178 ms  ch11-rba-gi0-1.ip.isnet.net [196.26.0.30]
  8   110 ms   284 ms    77 ms  csw3-pkl-gi1-2.ip.isnet.net [168.209.1.201]
  9   117 ms    86 ms    41 ms  za196-23-168-147.cache.googlevideo.com [196.23.1
68.147]

Trace complete.

U:\>
 
Last edited:
Afrihost 4mb Uncapped:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>ping google.co.za

Pinging google.co.za [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=21ms TTL=57
Reply from 196.23.168.147: bytes=32 time=21ms TTL=57
Reply from 196.23.168.147: bytes=32 time=21ms TTL=57
Reply from 196.23.168.147: bytes=32 time=21ms TTL=57

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 21ms, Average = 21ms

C:\Users\>tracert www.google.co.za

Tracing route to www.l.google.com [196.23.168.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 9 ms 196-210-132-1-nngy-esr-2.dynamic.isadsl.co.za [196.210.132.1]
3 21 ms 22 ms 21 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
4 20 ms 23 ms 20 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 24 ms 24 ms 22 ms csw3-pkl-gi1-2.ip.isnet.net [168.209.1.201]
6 21 ms 20 ms 20 ms za196-23-168-147.cache.googlevideo.com [196.23.168.147]

Trace complete.
 
Pinging www.l.google.com [64.233.179.104] with 32 bytes of data:

Reply from 64.233.179.104: bytes=32 time=359ms TTL=51
Reply from 64.233.179.104: bytes=32 time=367ms TTL=51
Reply from 64.233.179.104: bytes=32 time=356ms TTL=51
Reply from 64.233.179.104: bytes=32 time=360ms TTL=51

Ping statistics for 64.233.179.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 356ms, Maximum = 367ms, Average = 360ms

- I am with WebAfrica, 30GB Cap 4MB line.
 
Web Africa - the 30 gig special for MyBB members :) - 384 line

C:\Users\Kugaza>ping google.co.za

Pinging google.co.za [66.102.9.106] with 32 bytes of data:
Reply from 66.102.9.106: bytes=32 time=221ms TTL=52
Reply from 66.102.9.106: bytes=32 time=222ms TTL=52
Reply from 66.102.9.106: bytes=32 time=220ms TTL=52
Reply from 66.102.9.106: bytes=32 time=227ms TTL=52

Ping statistics for 66.102.9.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 227ms, Average = 222ms

C:\Users\Kugaza>

C:\Users\Kugaza>tracert google.co.za

Tracing route to google.co.za [66.102.9.103]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 33 ms 32 ms 32 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 36 ms 34 ms 36 ms vl32.er.gw.cpt.za.wa.co.za [41.185.0.26]
5 116 ms 116 ms 116 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.22
6]
6 268 ms 271 ms 272 ms 196.43.9.138
7 211 ms 208 ms 206 ms 221-76-245-83.packetexchange.net [83.245.76.221]

8 239 ms 251 ms 242 ms 209.85.255.175
9 237 ms 239 ms 238 ms 209.85.250.216
10 213 ms 214 ms 235 ms 72.14.232.235
11 221 ms 222 ms 213 ms 64.233.174.14
12 216 ms 217 ms 215 ms lm-in-f103.1e100.net [66.102.9.103]

Trace complete.
 
Last edited:
Telkom (still on int cap)

ping
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\TPex>ping www.google.co.za

Pinging www.l.google.com [209.85.227.106] with 32 bytes of data:
Reply from 209.85.227.106: bytes=32 time=380ms TTL=46
Reply from 209.85.227.106: bytes=32 time=398ms TTL=46
Reply from 209.85.227.106: bytes=32 time=435ms TTL=46
Reply from 209.85.227.106: bytes=32 time=391ms TTL=46

Ping statistics for 209.85.227.106:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 380ms, Maximum = 435ms, Average = 401ms

traceroot
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\TPex>tracert www.google.co.za

Tracing route to www.l.google.com [209.85.227.106]
over a maximum of 30 hops:

  1    21 ms    20 ms    26 ms  dsl-244-64-01.telkomadsl.co.za [41.244.64.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    69 ms    33 ms    31 ms  196.43.10.130
  5    31 ms    31 ms    32 ms  196.43.33.5
  6   313 ms   312 ms   314 ms  ams-ip-dir-globalc-pos-4-0-1.telkom-ipnet.co.za
[196.43.18.38]
  7   358 ms   379 ms   380 ms  125-126-245-83.packetexchange.net [83.245.126.12
5]
  8   399 ms   402 ms   398 ms  209.85.255.175
  9   368 ms     *      395 ms  66.249.95.173
 10   396 ms   399 ms   423 ms  209.85.251.231
 11     *      406 ms     *     209.85.243.101
 12   416 ms   509 ms   414 ms  wy-in-f106.1e100.net [209.85.227.106]

Trace complete.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X