Any particular reason why MTN-UG would be getting (some of) its transit through Jo'burg (hops 10 and later are the most interesting):
[ti...@nms ~]$ traceroute www.mtn.co.ug traceroute to www.mtn.co.ug (212.88.97.22), 64 hops max, 52 byte packets 1 gi-2-0-11.edge-gw-1-kul-pip.my.globaltransit.net (124.158.236.61) 0.387 ms 0.214 ms 0.197 ms 2 gi-0-1.pp-gw-1-kul-pip.my.globaltransit.net (61.11.210.184) 0.972 ms 0.515 ms 0.509 ms 3 gi-0-3-22.internet-solutions-gw.pp-gw-1-kul-pip.my.globaltransit.net (124.158.239.6) 0.461 ms 0.361 ms 0.352 ms 4 mi-za-cpt-br1-gi0-3-108.ip.isnet.net (168.209.28.42) 130.328 ms 130.156 ms 130.192 ms 5 css2-ctn-gi1-0-108.ip.isnet.net (168.209.28.41) 130.615 ms 130.476 ms 130.930 ms 6 core2a-ctn-gi0-2.ip.isnet.net (168.209.6.6) 130.772 ms 131.713 ms 131.244 ms 7 core6a-rba-gi1-0-4-306.ip.isnet.net (168.209.100.77) 131.397 ms 132.035 ms 131.557 ms 8 168.209.1.170 (168.209.1.170) 131.241 ms 134.363 ms 181.161 ms 9 mtnns.jinx.net.za (198.32.142.18) 133.578 ms 133.280 ms 131.554 ms 10 rb-lpd-1--jinx-lpa-1-a.mtnns.net (196.44.0.81) 691.287 ms 667.645 ms 668.142 ms 11 jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 668.826 ms 668.562 ms 666.954 ms 12 jh-cr-1.za--jh-cr-2.za-a.mtnns.net (196.44.31.254) 666.983 ms 669.821 ms 671.026 ms 13 mba-cr-1.ug--jh-cr-2.za.mtnns.net (196.44.31.205) 667.107 ms 715.175 ms 666.799 ms 14 mba-pr-1--mba-cr-1-a.ug.mtnns.net (209.212.127.5) 669.232 ms 666.228 ms 666.174 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * ^C [ti...@nms ~]$ Wouldn't that be a longer path, even when compared against satellite? Cheers, Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
