On Tuesday 27 April 2010 02:43:09 am McTim wrote: > Access Kenya sent out a warning that it was happening in > the Med. In any case, SEACOM has redundant connectivity > via Mumbai, that is how I am getting to Europe: > > Tracing route to ripe.net [193.0.6.139] > over a maximum of 30 hops: > > 1 3 ms 3 ms 3 ms 192.168.1.1 > 2 41 ms 44 ms 59 ms > 41.206.46.10.accesskenya.com [41.206.46.10] 3 46 ms > 49 ms 49 ms ge-1-0-0-bp_core01.accesskenya.com > [196.207.31.33] > 4 47 ms 43 ms 44 ms > TenGE-2-1-BP_EDGE01.accesskenya.com [196.207.31.145] > 5 111 ms 109 ms 109 ms > if-4-1-1.core1.MLV-Mumbai.as6453.net [209.58.105.141] > 6 138 ms 149 ms 139 ms > if-4-0-1.core2.CFO-Chennai.as6453.net [116.0.84.9] > 7 167 ms 174 ms 179 ms > if-12-0-0.core2.S9R-Singapore.as6453.net [116.0.84.50] > 8 * 261 ms 257 ms > if-14-0-0-954.core1.TV2-Tokyo.as6453.net [209.58.96.98] > 9 377 ms 374 ms 369 ms > if-12-0-0.mcore4.PDI-PaloAlto.as6453.net [216.6.86.25] > 10 415 ms 420 ms 409 ms > if-0-0-0-1711.core3.NTO-NewYork.as6453.net [216.6.86.34] > 11 * 701 ms 654 ms > if-7-0-0.core2.AD1-Amsterdam.as6453.net [80.231.81.45] > 12 562 ms 559 ms 569 ms
That's a (not so) pretty long path, mate. This underscores the need for EASSy. But more importantly, that operators will buy capacity on at least 2 of the systems (although both SEACOM and TEAMS routing via the east doesn't help anyone). SEACOM should have been able to bring up their western route by now. Things take time, I guess. 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/ All Archives can be found at http://www.mail-archive.com/[email protected]/ 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. ---------------------------------------
