How come some of the Washington and San Jose hops only list one packet latency value... that means the packet didn't get back to me, right? Update: I learned from Stefan at BOSCO that until the undersea cable recently installed in Kenya is carrying Ugandan packet data, Uganda still gets all of its Internet from a satellite connection. At the MTN/AppLab offices in Kampala, there are 2 really huge satellite dishes that, I bet, carry a lot of this traffic. I am not sure how satellite hops work, but if you take a look at the traceroute below, you can see that somewhere around hop 8, 9, and 10 Ugandan Internet traffic goes up into Outer Space... and then back down to Europe!
traceroute to ischool.berkeley.edu (128.32.78.26), 30 hops max, 60 byte packets
1 10.120.1.50 (10.120.1.50) 201.066 ms 297.988 ms 297.934 ms
2 10.120.1.49 (10.120.1.49) 320.850 ms 339.793 ms 380.738 ms
3 10.120.1.17 (10.120.1.17) 397.683 ms 398.659 ms 398.609 ms
4 hd9.n3.ips.mtn.co.ug (193.108.214.217) 398.559 ms 418.486 ms 560.435 ms
5 h131.n2.ips.mtn.co.ug (212.88.97.49) 800.376 ms 818.384 ms 818.326 ms
6 h138.n2.ips.mtn.co.ug (212.88.97.56) 1317.183 ms 677.273 ms 441.658 ms
7 217.194.128.81 (217.194.128.81) 960.553 ms 977.468 ms 998.447 ms
8 hsrp.sky-vision.net (217.194.129.1) 998.384 ms 998.332 ms 998.282 ms
9 gw1.afl.sky-vision.net (217.194.129.20) 998.231 ms 998.164 ms 999.006 ms
10 GW1-FRA-DE.sky-vision.net (217.194.128.34) 1236.933 ms 1217.879 ms 1238.830 ms
11 212.162.25.77 (212.162.25.77) 998.799 ms 999.741 ms 999.583 ms
12 vlan99.csw4.Frankfurt1.Level3.net (4.68.23.254) 758.704 ms 734.263 ms 677.648 ms
13 ae-92-92.ebr2.Frankfurt1.Level3.net (4.69.140.29) 939.653 ms 917.459 ms 939.525 ms
14 ae-42-42.ebr2.Washington1.Level3.net (4.69.137.54) 1018.389 ms ae-43-43.ebr2.Washington1.Level3.net (4.69.137.58) 1018.341 ms 1120.250 ms
15 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 1122.190 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 1139.173 ms ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 1156.096 ms
16 ae-64-64.ebr4.Washington1.Level3.net (4.69.134.177) 1138.043 ms ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 1138.958 ms ae-64-64.ebr4.Washington1.Level3.net (4.69.134.177) 1138.878 ms
17 ae-3-3.ebr1.NewYork1.Level3.net (4.69.132.94) 1136.805 ms 1179.719 ms 1197.540 ms
18 ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 923.630 ms 779.809 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 1158.483 ms
19 ae-94-94.ebr4.NewYork1.Level3.net (4.69.134.125) 1159.412 ms 779.663 ms ae-64-64.ebr4.NewYork1.Level3.net (4.69.134.113) 881.536 ms
20 ae-2.ebr4.SanJose1.Level3.net (4.69.135.185) 959.468 ms 1001.434 ms 978.374 ms
21 ae-64-64.csw1.SanJose1.Level3.net (4.69.134.242) 1020.323 ms ae-84-84.csw3.SanJose1.Level3.net (4.69.134.250) 1037.262 ms 1439.248 ms
22 ae-92-92.ebr2.SanJose1.Level3.net (4.69.134.221) 1061.172 ms ae-62-62.ebr2.SanJose1.Level3.net (4.69.134.209) 1438.196 ms ae-72-72.ebr2.SanJose1.Level3.net (4.69.134.213) 1259.048 ms
23 ae-5-5.car1.Oakland1.Level3.net (4.69.134.37) 1439.013 ms 1438.925 ms 1438.874 ms
24 CORP-FOR-ED.car1.Oakland1.Level3.net (4.71.164.66) 858.660 ms 959.570 ms 856.608 ms
25 inet-ucb--oak-isp.cenic.net (137.164.24.142) 977.508 ms 975.458 ms 998.405 ms
26 g4-1.inr-202-reccev.Berkeley.EDU (128.32.0.50) 956.355 ms 1016.334 ms 1016.283 ms
27 t1-1.inr-211-srb.Berkeley.EDU (128.32.255.43) 1061.191 ms 1057.148 ms 1059.090 ms
28 * * *
29 * * *
30 * * *