[outages] SEA-ME-WE3 undersea cable cut

Wed Jan 16 11:18:21 EST 2013

On 1/15/13 9:23 PM, Constantine A. Murenin wrote:
> On 15 January 2013 18:54, Ben Aitchison <ben at meh.net.nz> wrote:
>> On Tue, Jan 15, 2013 at 06:44:24PM -0800, Constantine A. Murenin wrote:
>>> On 15 January 2013 18:10, Ben Aitchison <ben at meh.net.nz> wrote:
>>>> Japan/Hong Kong.  But from reading about the Singapore Battle.net server for Starcraft 2, it sounded like Australia has a lot of ISP's with bad Asia routing in
>>>> general so may not make much difference.
>>> As if routing between Asia-Pacific and Europe (or even Russia) is any good! :-p
>> It's actually pretty good to Korea, Singapore, Japan, and Hong Kong generally.
>>
>> It's India, Pakistan, China etc that aren't so good.
>>
>> Europe to China is terrible though.  I've got a friend who was asking about remote between UK/China.  And if it's possible to get good routes to there.
>>
>> And I can't find anyone doing good routing to China from Europe.  I'm sure there's meant to be a cable with a good path?
China telecom among other appears at de-cix. it's my experience that 
paths into china on the transit side are deliberately operated at 
capacity. When I worked for a large electronics manufacturing concern we 
had TDM and/or later l3vpn paths into our network in china from europe, 
one through central asia and another via the middle east, both required 
multiple provider handoffs.
>> Ben.
> Do you have a traceroute of any of these good routes?  Are they under
> 200ms or above 300ms?
>
> I've never seen a traceroute between Japan (UTC+9) and either London
> (0/+1), Germany (+1/+2) or Moscow (+4 (formerly +3/+4)) that didn't go
> through usually both NYC (-5/-4) and SJC (-8/-7).
>
> All in the northern hemisphere, timezone-wise Moscow and Japan are
> only 5 hours apart, whereas Moscow and SJC are 12 hours apart right
> now, and SJC and Japan are an extra 7 hours.  5 vs. 19? :-)
>
> Actually, there were a couple of weeks when routing between HE.net in
> FMT and a RETN.net-based connection in MSK was going through Japan one
> way, and it was adding a little extra latency.  As an end-user, that
> was the first and only time ever that I had any remote proof of any
> internet pipes leaving Russia not through Europe!
>
> http://tu.cnst.su/post/13096244490/he-net-pings-between-fremont1-and-moscow-russia
> https://plus.google.com/101080388381040783378/posts/LY6m7edSe5x
>
> But the traceroute below is representative of about the only route
> there is between Europe and Asia:
>
> # traceroute www.allbsd.org
> traceroute to www.allbsd.org (133.31.130.35), 32 hops max, 52 byte packets
>   1  [AS29182] gw.webdc.ru (188.120.247.254)  0.592 ms  0.497 ms  0.416 ms
>   2  [AS29182] xe200-40.webdc.ru (92.63.108.89)  0.422 ms  0.396 ms  0.253 ms
>   3  [AS29470] 46.46.168.173 (46.46.168.173)  0.447 ms  0.561 ms  0.718 ms
>   4  [AS9002] xe000-8.RT.TLX.NYC.US.retn.net (87.245.233.114)  124.381
> ms  124.784 ms  124.506 ms
>   5  [AS4637] NYIIX.IIJ.Net (198.32.160.42)  124.510 ms  124.533 ms  124.506 ms
>   6  [AS14936] sjc002bb01.IIJ.net (206.132.169.206)  209.920 ms
> 209.940 ms  209.929 ms
>   7  [AS14936] sjc002bf02.IIJ.net (206.132.169.249)  209.930 ms
>      [AS14936] sjc002bf00.IIJ.Net (206.132.169.241)  209.967 ms
>      [AS14936] sjc002bf02.IIJ.Net (206.132.169.249)  209.971 ms
>   8  [AS2497] tky001bf00.IIJ.Net (216.98.96.181)  314.845 ms
>      [AS14936] tky009bf01.IIJ.net (206.132.169.122)  312.017 ms
>      [AS2497] tky001bf00.IIJ.Net (216.98.96.185)  314.899 ms
>   9  [AS2497] tky009bb11.IIJ.Net (58.138.80.214)  313.616 ms
>      [AS2497] tky009bb11.IIJ.Net (58.138.80.210)  312.620 ms
>      [AS2497] tky009bb10.IIJ.Net (58.138.80.170)  313.504 ms
> 10  [AS2497] tky009ipgw11.IIJ.Net (58.138.112.158)  312.611 ms
>      [AS2497] tky009ipgw10.IIJ.Net (58.138.112.154)  314.176 ms
>      [AS2497] tky009ipgw10.IIJ.Net (58.138.112.146)  312.732 ms
> 11  [AS2497] tky009ip71.IIJ.Net (58.138.112.110)  312.879 ms
>      [AS2497] tky009ip71.IIJ.Net (58.138.112.102)  313.562 ms
>      [AS2497] tky009ip71.IIJ.Net (58.138.112.110)  313.660 ms
> 12  [AS2497] 210.138.9.166 (210.138.9.166)  322.967 ms  355.891 ms  352.757 ms
> 13  [AS55390] 133.31.14.2 (133.31.14.2)  325.548 ms  320.578 ms  316.472 ms
> 14  [AS55390] vlsi03.si.noda.tus.ac.jp (133.31.130.35)  317.491 ms
> 314.033 ms  315.634 ms
>
> The latency could have been around 130ms if it didn't go through NA.
> Wishful thinking, I know!
>
> Cheers,
> Constantine.
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>