Re: [Skunkworks] Zain leads the way with unlimited internet

Pinging close to home. PING my.co.ke (62.8.88.72) 56(84) bytes of data. 64 bytes from my.co.ke (62.8.88.72): icmp_seq=1 ttl=56 time=276 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=2 ttl=56 time=417 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=3 ttl=56 time=396 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=4 ttl=56 time=356 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=5 ttl=56 time=577 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=6 ttl=56 time=317 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=7 ttl=56 time=478 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=8 ttl=56 time=323 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=9 ttl=56 time=535 ms 64 bytes from my.co.ke (62.8.88.72): icmp_seq=10 ttl=56 time=460 ms ^C --- my.co.ke ping statistics --- 11 packets transmitted, 10 received, 9% packet loss, time 15130ms rtt min/avg/max/mdev = 276.547/413.885/577.123/93.729 ms Pinging Google PING google.com (74.125.67.100) 56(84) bytes of data. 64 bytes from google.com (74.125.67.100): icmp_seq=1 ttl=50 time=1044 ms 64 bytes from google.com (74.125.67.100): icmp_seq=2 ttl=50 time=1528 ms 64 bytes from google.com (74.125.67.100): icmp_seq=3 ttl=50 time=1206 ms 64 bytes from google.com (74.125.67.100): icmp_seq=4 ttl=50 time=1404 ms 64 bytes from google.com (74.125.67.100): icmp_seq=5 ttl=50 time=904 ms 64 bytes from google.com (74.125.67.100): icmp_seq=6 ttl=50 time=1065 ms 64 bytes from google.com (74.125.67.100): icmp_seq=7 ttl=50 time=789 ms 64 bytes from google.com (74.125.67.100): icmp_seq=8 ttl=50 time=1910 ms 64 bytes from google.com (74.125.67.100): icmp_seq=9 ttl=50 time=1325 ms 64 bytes from google.com (74.125.67.100): icmp_seq=10 ttl=50 time=667 ms ^C --- google.com ping statistics --- 11 packets transmitted, 10 received, 9% packet loss, time 10765ms rtt min/avg/max/mdev = 667.694/1184.652/1910.522/353.476 ms, pipe 2 Pinging Yahoo. PING yahoo.com (209.191.93.53) 56(84) bytes of data. 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=1 ttl=46 time=1352 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=2 ttl=46 time=1372 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=3 ttl=46 time=1822 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=4 ttl=48 time=1939 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=5 ttl=45 time=1499 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=6 ttl=48 time=1937 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=7 ttl=48 time=1159 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=8 ttl=46 time=1377 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=9 ttl=45 time=2723 ms 64 bytes from b1.www.vip.mud.yahoo.com (209.191.93.53): icmp_seq=10 ttl=47 time=1767 ms ^C --- yahoo.com ping statistics --- 12 packets transmitted, 10 received, 16% packet loss, time 12042ms rtt min/avg/max/mdev = 1159.251/1695.115/2723.099/429.465 ms, pipe 3 Trace path Yahoo [root@R2D2 ~]# tracepath yahoo.com 1: 172.20.25.148 (172.20.25.148) 0.279ms pmtu 1500 1: 172.16.5.3 (172.16.5.3) 1738.577ms asymm 2 1: 172.16.5.3 (172.16.5.3) 1295.318ms asymm 2 2: 172.16.5.1 (172.16.5.1) 688.985ms asymm 3 3: 172.16.15.4 (172.16.15.4) 1639.862ms 3: 172.16.15.4 (172.16.15.4) 1096.711ms 4: 172.16.12.2 (172.16.12.2) 1499.938ms asymm 5 4: 172.16.12.2 (172.16.12.2) 761.750ms asymm 5 5: 41.223.57.225 (41.223.57.225) 1277.749ms 5: 41.223.57.225 (41.223.57.225) 677.421ms 6: no reply 7: PO1-2.lon-001-access-2.interoute.net (84.233.134.101) 1685.726ms 7: PO1-2.lon-001-access-2.interoute.net (84.233.134.101) 1105.082ms 8: xe-2-3-0-0.lon-001-score-1-re0.interoute.net (84.233.218.161) 1188.843ms asymm 9 8: xe-2-3-0-0.lon-001-score-1-re0.interoute.net (84.233.218.161) 1766.986ms asymm 9 9: no reply 10: no reply 9: ge-3-3-0.pat1.tc2.yahoo.com (195.66.226.129) 6578.225ms asymm 10 10: ge-2-0-0.pat1.the.yahoo.com (66.196.65.0) 6314.133ms asymm 9 10: ge-2-0-0.pat1.the.yahoo.com (66.196.65.0) 7934.726ms asymm 9 10: ge-2-0-0.pat1.the.yahoo.com (66.196.65.0) 8176.495ms asymm 9 11: so-1-0-0.pat1.nyc.yahoo.com (66.196.65.13) 8091.600ms asymm 17 11: so-1-0-0.pat1.nyc.yahoo.com (66.196.65.13) 7390.635ms asymm 17 12: ge-3-0-0.pat2.nyc.yahoo.com (216.115.111.66) 2005.371ms asymm 16 12: ge-3-0-0.pat2.nyc.yahoo.com (216.115.111.66) 3486.462ms asymm 16 12: ge-3-0-0.pat2.nyc.yahoo.com (216.115.111.66) 2921.408ms asymm 16 13: so-3-0-0.pat1.che.yahoo.com (216.115.101.158) 939.802ms asymm 15 14: as-1.pat1.dnx.yahoo.com (216.115.96.34) 1278.119ms 14: as-1.pat1.dnx.yahoo.com (216.115.96.34) 2909.104ms 15: as-0.pat1.sjc.yahoo.com (216.115.101.149) 1282.702ms asymm 14 16: ae0-p170.msr2.sp1.yahoo.com (216.115.107.81) 2956.876ms asymm 15 17: no reply 18: no reply 19: no reply Continues to 30. Pinging Gmail PING gmail.com (209.85.225.83) 56(84) bytes of data. 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=1 ttl=49 time=736 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=2 ttl=49 time=617 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=3 ttl=49 time=1482 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=4 ttl=49 time=994 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=5 ttl=47 time=2414 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=6 ttl=49 time=1893 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=7 ttl=47 time=916 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=8 ttl=49 time=999 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=9 ttl=49 time=616 ms 64 bytes from iy-in-f83.google.com (209.85.225.83): icmp_seq=10 ttl=47 time=1516 ms ^C --- gmail.com ping statistics --- 18 packets transmitted, 10 received, 44% packet loss, time 17681ms rtt min/avg/max/mdev = 616.277/1218.772/2414.382/564.717 ms, pipe 3 Trace path Gmail [root@R2D2 ~]# tracepath gmail.com 1: 172.20.25.148 (172.20.25.148) 0.287ms pmtu 1500 1: 172.16.5.3 (172.16.5.3) 1259.916ms asymm 2 1: 172.16.5.3 (172.16.5.3) 1502.314ms asymm 2 2: 172.16.5.1 (172.16.5.1) 1019.826ms asymm 3 2: 172.16.5.1 (172.16.5.1) 2077.664ms asymm 3 3: 172.16.15.4 (172.16.15.4) 1400.896ms 3: 172.16.15.4 (172.16.15.4) 1119.680ms 4: 172.16.12.2 (172.16.12.2) 700.832ms asymm 5 5: 41.223.57.225 (41.223.57.225) 674.971ms 6: no reply 7: l3.london.kdn.intersatafrica.com (212.113.15.97) 795.074ms asymm 8 8: ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 2679.806ms 8: ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 2797.668ms 8: ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 2555.414ms 9: ae-2-2.ebr2.Amsterdam1.Level3.net (4.69.132.134) 1571.919ms 9: ae-2-2.ebr2.Amsterdam1.Level3.net (4.69.132.134) 1795.622ms 10: ae-21-52.car1.Amsterdam1.Level3.net (4.69.139.162) 1914.852ms 12: no reply 13: no reply 14: no reply 15: no reply continued to 30. The one advantage Zain has over Saf is once connected (DNS and Network are OK) connection will not get lost midway. Ashford K.