Access Kenya looks like they are on transit to fibre. Latencies for traceroute have reduced over the week( and so have the hops, and newskies and Washington.edu are no longer on the route) . the transition period is characterised by many network error( tcp_error). Remember how safaricom slowed down before the big switch.
[root@fintern /]# traceroute yahoo.com
traceroute to yahoo.com (69.147.114.224), 30 hops max, 60 byte packets
 1  192.168.32.1 (192.168.32.1)  5.823 ms  6.106 ms  7.072 ms
 2  10.36.0.1 (10.36.0.1)  14.819 ms  15.119 ms  15.425 ms
 3  ge-02-lfg1.accesskenya.com (196.207.31.33)  101.554 ms  165.317 ms  165.625 ms
 4  TenGE-2-1-BP_EDGE01.accesskenya.com (196.207.31.145)  100.902 ms  164.847 ms  164.439 ms
 5  ge-00-rc_er01.accesskenya.com (196.207.31.7)  79.828 ms  79.440 ms  78.842 ms
 6  * ge-03-lau01.accesskenya.com (196.207.31.94)  679.540 ms  559.587 ms
 7  Vlan310.msfc3.LAU-Laurentides.as6453.net (64.86.88.221)  682.017 ms  682.809 ms  683.600 ms
 8  if-5-0.core1.LAU-Laurentides.as6453.net (64.86.81.65)  663.860 ms  671.517 ms  664.583 ms
 9  if-9-1.mcore4.MTT-Montreal.as6453.net (216.6.115.9)  672.261 ms  652.167 ms  652.953 ms
10  Pos-channel1.mcore3.NYY-NewYork.as6453.net (216.6.81.17)  636.205 ms  638.629 ms  651.239 ms
11  if-13-0-0-722.core3.AEQ-Ashburn.as6453.net (216.6.51.21)  665.167 ms  662.699 ms *
12  ix-14-2.core3.AEQ-Ashburn.as6453.net (63.243.149.110)  725.816 ms *  711.574 ms
13  ae1-p140.msr1.re1.yahoo.com (216.115.108.17)  697.606 ms ae1-p150.msr2.re1.yahoo.com (216.115.108.21)  695.992 ms  662.622 ms
14  * te-9-2.bas-a2.re3.yahoo.com (66.196.112.55)  629.726 ms *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


2009/7/25 Dennis Kioko <dmbuvi@gmail.com>
Yu

[user@localhost ~]$ traceroute yahoo.com
traceroute to yahoo.com (209.191.93.53), 30 hops max, 60 byte packets
 1  10.4.0.2 (10.4.0.2)  905.913 ms  905.842 ms  905.812 ms
 2  10.4.0.1 (10.4.0.1)  939.057 ms  939.030 ms  939.001 ms
 3  10.4.0.36 (10.4.0.36)  940.785 ms  958.649 ms  1018.629 ms
 4  10.4.0.60 (10.4.0.60)  1096.626 ms  1240.597 ms  1277.575 ms
 5  10.4.0.68 (10.4.0.68)  1318.528 ms  1377.491 ms  1437.458 ms
 6   (210.5.199.249)  1519.423 ms  396.782 ms  458.219 ms
 7   (210.5.199.26)  498.702 ms  742.800 ms  820.750 ms
 8   (210.5.199.158)  862.717 ms  899.692 ms  982.659 ms
 9  66-178-102-150.reverse.newskies.net (66.178.102.150)  1762.636 ms  1780.610 ms  1882.575 ms
10  66-178-113-113.reverse.newskies.net (66.178.113.113)  1900.552 ms  1960.518 ms  2020.477 ms
11  66-178-112-97.reverse.newskies.net (66.178.112.97)  2099.493 ms  2200.404 ms  1059.834 ms
12  host-66-133-55-193.wdb.ses-americom.net (66.133.55.193)  1120.773 ms  1240.748 ms  2037.791 ms
13  so-2-0-1.edge6.Washington1.Level3.net (4.79.198.5)  2060.731 ms  2120.709 ms  2161.675 ms
14  vlan79.csw2.Washington1.Level3.net (4.68.17.126)  2217.649 ms  2601.644 ms vlan69.csw1.Washington1.Level3.net (4.68.17.62)  2603.620 ms
15  ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141)  2628.567 ms  2638.543 ms ae-61-61.ebr1.Washington1.Level3.net (4.69.134.129)  2640.491 ms
16  ae-2.ebr3.Atlanta2.Level3.net (4.69.132.85)  2665.473 ms  2667.434 ms  2698.412 ms
17  ae-7.ebr3.Dallas1.Level3.net (4.69.134.21)  2081.949 ms  2140.741 ms  2178.711 ms
18  ae-41-90.car1.Dallas1.Level3.net (4.69.145.195)  1059.814 ms  1095.757 ms ae-11-60.car1.Dallas1.Level3.net (4.69.145.3)  1155.760 ms
19  YAHOO-INC.car1.Dallas1.Level3.net (4.79.180.2)  1178.701 ms  1215.681 ms  1275.648 ms
20  ae2-p130.msr2.mud.yahoo.com (216.115.104.93)  1335.613 ms  1376.590 ms ae1-p120.msr1.mud.yahoo.com (216.115.104.81)  1455.559 ms
21  te-9-1.bas-c1.mud.yahoo.com (68.142.193.9)  1478.534 ms te-8-1.bas-c2.mud.yahoo.com (68.142.193.7)  1538.501 ms te-8-1.bas-c1.mud.yahoo.com (68.142.193.5)  1575.477 ms
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


2009/7/25 Michuki Mwangi <michuki@swiftkenya.com>

Thanks Brian,

A RTT's are still on the higher side so i presume theres alot more fine
tuning that needs to be done.

Also folks will have to seek better transit and peering 19 hops to
google is definitely wanting!.

19 hop despite the reduced latencies doesnt perform any better than
clean satellite connection with less hops as was the case before.

Regards,

Mich

Brian Muita wrote:
>
> mac:~ bmuita$ ping -c 5 google.com
> PING google.com (74.125.45.100): 56 data bytes
> 64 bytes from 74.125.45.100: icmp_seq=0 ttl=47 time=398.569 ms
> 64 bytes from 74.125.45.100: icmp_seq=1 ttl=47 time=388.591 ms
> 64 bytes from 74.125.45.100: icmp_seq=2 ttl=47 time=408.276 ms
> 64 bytes from 74.125.45.100: icmp_seq=3 ttl=47 time=389.094 ms
> 64 bytes from 74.125.45.100: icmp_seq=4 ttl=47 time=407.418 ms
>
> --- google.com ping statistics ---
> 5 packets transmitted, 5 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 388.591/398.390/408.276/8.505 ms
>
> mac:~ bmuita$ traceroute -n google.com
> traceroute: Warning: google.com has multiple addresses; using 74.125.45.100
> traceroute to google.com (74.125.45.100), 64 hops max, 40 byte packets
>  1  172.24.7.2  428.676 ms  320.850 ms  318.431 ms
>  2  172.24.7.2  329.358 ms  340.786 ms  409.166 ms
>  3  196.201.208.61  239.483 ms  100.303 ms  90.018 ms
>  4  172.22.2.49  109.614 ms  100.347 ms  89.498 ms
>  5  196.201.208.60  109.627 ms  99.686 ms  100.117 ms
>  6  195.219.195.109  280.029 ms  269.850 ms  320.200 ms
>  7  195.219.195.90  289.533 ms  289.843 ms  309.662 ms
>  8  4.68.63.105  280.290 ms  279.680 ms  279.904 ms
>  9  4.69.139.97  280.053 ms  619.698 ms  279.957 ms
> 10  4.69.137.74  370.229 ms 4.69.137.66  369.724 ms  349.928 ms
> 11  4.69.132.93  689.928 ms  349.244 ms  389.913 ms
> 12  4.69.134.186  360.203 ms  359.512 ms  359.994 ms
> 13  4.68.17.144  359.986 ms  370.220 ms  369.331 ms
> 14  4.79.22.38  380.145 ms  379.919 ms  379.706 ms
> 15  209.85.241.50  360.029 ms 209.85.240.136  359.798 ms  359.896 ms
> 16  66.249.95.149  409.890 ms  379.939 ms  389.819 ms
> 17  72.14.232.215  369.968 ms 72.14.232.213  379.829 ms  379.997 ms
> 18  209.85.253.133  389.709 ms 209.85.253.145  370.224 ms  439.710 ms
> 19  74.125.45.100  379.835 ms  389.693 ms  370.568 ms
>
> bmuita@teddybear:~$ traceroute -n 196.201.208.27
> traceroute to 196.201.208.27 (196.201.208.27), 30 hops max, 40 byte packets
>  1  89.16.172.1  4.497 ms  0.541 ms  0.490 ms
>  2  89.16.188.2  0.695 ms  0.822 ms  0.662 ms
>  3  89.16.160.34  0.765 ms  0.674 ms  0.669 ms
>  4  80.68.80.73  7.847 ms  7.695 ms  7.849 ms
>  5  195.219.83.17  18.700 ms  18.311 ms  17.452 ms
>  6  195.219.83.2  7.993 ms 195.219.195.89  7.935 ms 195.219.195.37  7.906 ms
>  7  195.219.195.118  198.398 ms  188.140 ms  190.075 ms
>  8  196.201.208.27  187.640 ms  188.436 ms  187.089 ms
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Skunkworks mailing list
> Skunkworks@lists.my.co.ke
> http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
> Other services @ http://my.co.ke
> Other lists
> -------------
> Announce: http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks-announce
> Science:  http://lists.my.co.ke/cgi-bin/mailman/listinfo/science
> kazi:     http://lists.my.co.ke/cgi-bin/mailman/admin/kazi/general
_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
Other services @ http://my.co.ke
Other lists
-------------
Announce: http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks-announce
Science:  http://lists.my.co.ke/cgi-bin/mailman/listinfo/science
kazi:     http://lists.my.co.ke/cgi-bin/mailman/admin/kazi/general



--
with Regards:
Owning an iphone in Kenya is a bargain. Find out how at my blog:.
http://gramware.blogspot.com






--
with Regards:
Find out how you can own your own TFT T.V. at a fraction of the cost on my blog:
http://gramware.blogspot.com