South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
ping -c 10 -i 10 www.google.com
PING www.l.google.com (72.14.203.104) 56(84) bytes of data.
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=1 ttl=51 time=384 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=2 ttl=51 time=878 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=3 ttl=51 time=340 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=4 ttl=51 time=339 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=5 ttl=51 time=340 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=6 ttl=51 time=766 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=7 ttl=51 time=738 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=8 ttl=51 time=341 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=9 ttl=51 time=888 ms
64 bytes from tx-in-f104.google.com (72.14.203.104): icmp_seq=10 ttl=51 time=342 ms
--- www.l.google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 89999ms
rtt min/avg/max/mdev = 339.047/536.029/888.445/234.273 ms
Pinging www.speedtest.net [69.17.117.207] with 32 bytes of data:
Reply from 69.17.117.207: bytes=32 time=353ms TTL=53
Reply from 69.17.117.207: bytes=32 time=353ms TTL=53
Reply from 69.17.117.207: bytes=32 time=352ms TTL=53
Reply from 69.17.117.207: bytes=32 time=352ms TTL=53
Ping statistics for 69.17.117.207:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 352ms, Maximum = 353ms, Average = 352ms
Tracing route to www.speedtest.net [69.17.117.207]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 20 ms 24 ms 16 ms dsl-240-192-01.telkomadsl.co.za [41.240.192.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 22 ms 20 ms 22 ms 196.43.10.130
6 21 ms * 20 ms 196.43.33.5
7 169 ms 168 ms 168 ms hkg-ip-dir-hongkong-pos-4-0-3.telkom-ipnet.co.za [196.43.18.214]
8 180 ms * * if-13-30.icore1.HK2-HongKong.as6453.net [116.0.9
3.25]
9 * 169 ms 169 ms if-11-0-0-31.core3.HK2-HongKong.as6453.net [116.
0.82.17]
10 226 ms 227 ms 225 ms if-5-0-0.core1.TV2-Tokyo.as6453.net [116.0.82.2]
11 352 ms 351 ms 350 ms if-12-0-0.mcore4.PDI-PaloAlto.as6453.net [216.6.
86.25]
12 370 ms 369 ms 369 ms if-1-0-0.core1.S00-Seattle.as6453.net [207.45.19
6.66]
13 367 ms 365 ms 365 ms if-3-0.core2.SEP-Seattle.as6453.net [66.110.64.1
3]
14 353 ms 351 ms 353 ms 66.110.64.10
15 352 ms 352 ms 352 ms 151.ge-1-3-0.sr1.sea5.speakeasy.net [69.17.82.50
]
16 * * 355 ms www.ookla.com [69.17.117.207]
Trace complete.
Anyone else got normal pings on overseas gaming atm, or is it just the calm before another storm?
Nothing has changed, intl browsing very slow on my SAIX account. Very frustrating. Whenever I enter a website address there's 5 seconds where absolutely nothing happens, only thereafter does it resolve the address and start loading it, very slowly too. Changing DNS servers make no difference.
Tomorrow it will be exactly a week that I've had this problem. WA & Telkom says there's nothing wrong on the network. Yeah right.