Send Outages mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages digest..."
Today's Topics:
1. Re: SEA-ME-WE3 undersea cable cut (Ben Aitchison)
2. Re: Power Outage/Fiber Splice In Hawaii? (Owen DeLong)
3. Re: SEA-ME-WE3 undersea cable cut (Ben Aitchison)
4. Re: SEA-ME-WE3 undersea cable cut (Nicolas Hyvernat)
5. Re: SEA-ME-WE3 undersea cable cut (Martin Hepworth)
----------------------------------------------------------------------
Message: 1
Date: Wed, 16 Jan 2013 15:54:51 +1300
From: Ben Aitchison <[email protected]>
To: "Constantine A. Murenin" <[email protected]>
Cc: [email protected]
Subject: Re: [outages] SEA-ME-WE3 undersea cable cut
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Tue, Jan 15, 2013 at 06:44:24PM -0800, Constantine A. Murenin wrote:
> On 15 January 2013 18:10, Ben Aitchison <[email protected]> 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?
Ben.
------------------------------
Message: 2
Date: Tue, 15 Jan 2013 20:34:07 -1000
From: Owen DeLong <[email protected]>
To: "Hamm, Jack" <[email protected]>
Cc: "Roberts, Brent" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [outages] Power Outage/Fiber Splice In Hawaii?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
<joking>Internet 2 and APAN are having a joint meeting in Honolulu. Naturally,
it wouldn't be a big meeting of techs without a fiber cut to go with it.
</joking>
Owen
Sent from my iPad
On Jan 15, 2013, at 1:35 PM, "Hamm, Jack" <[email protected]> wrote:
> I'm seeing degraded paths to Hawaii on our big board.
>
> -Jack
>
> On Jan 15, 2013, at 1:20 PM, Roberts, Brent wrote:
>
>> Looks like there is either a rather Large Power outage or Fiber Cut In
>> Hawaii at the moment. I personally have multiple circuits down and Random
>> packet loss to Different Carriers on the Islands. Anyone else seeing
>> anything similar?
>>
>>
>> B.
>>
>>
>>
>>
>> Disclaimer:
>> This e-mail has been sent by Epicor, formerly Progressive Solutions Inc. or
>> one of its affiliates ("Epicor"). The contents of this e-mail and any
>> attachments are intended for the named addressee only and may be
>> confidential. Unless you are the named addressee or are authorized to
>> receive the e-mail of the named addressee you may not disclose, use or copy
>> the contents of the e-mail. If you received this e-mail in error, please
>> contact the sender immediately and then delete the e-mail. Epicor does not
>> accept responsibility for this message and any views or opinions contained
>> in this e-mail are solely those of the author unless expressly stated
>> otherwise.
>>
>> _______________________________________________
>> Outages mailing list
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/outages
>
> _______________________________________________
> Outages mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/outages
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages/attachments/20130115/c4a80afa/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 16 Jan 2013 20:05:05 +1300
From: Ben Aitchison <[email protected]>
To: "Constantine A. Murenin" <[email protected]>
Cc: [email protected]
Subject: Re: [outages] SEA-ME-WE3 undersea cable cut
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Tue, Jan 15, 2013 at 09:23:58PM -0800, Constantine A. Murenin wrote:
> On 15 January 2013 18:54, Ben Aitchison <[email protected]> wrote:
> > On Tue, Jan 15, 2013 at 06:44:24PM -0800, Constantine A. Murenin wrote:
> >> On 15 January 2013 18:10, Ben Aitchison <[email protected]> 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?
> >
> > Ben.
>
> Do you have a traceroute of any of these good routes? Are they under
> 200ms or above 300ms?
>From NZ to that destination getting pings of under 165 to 180 msec to Tokyo,
>but then it skyrockets up ..
right now it seems to not be able to get to that host at all.
It was acting strange from NL/UK too.. but more like 250 to tokyo.
> 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
Curious. Russia may be even worse. I must admit I don't know a lot about
Europe
routing. What I did find earlier was that India from UK wasn't too bad, using
the
looking glass server of vr.org which has lots of locations.
> 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!
Hmm, I'll try it on that vr.org looking glass ffrom India.
traceroute to 133.31.130.35 (133.31.130.35), 30 hops max, 40 byte packets
1 103.6.87.10 1.019 ms 1.255 ms 1.644 ms
2 103.6.87.1 1.441 ms 1.650 ms 1.856 ms
3 180.179.33.245 0.974 ms 1.228 ms 1.218 ms
4 180.179.37.93 0.659 ms 0.907 ms 0.895 ms
5 59.163.105.170 2.683 ms 2.765 ms 2.964 ms
6 180.87.37.1 2.935 ms 2.435 ms 2.447 ms
7 180.87.37.14 34.182 ms 180.87.15.69 63.690 ms 35.216 ms
8 180.87.12.1 35.111 ms 180.87.12.53 34.114 ms 180.87.12.1 57.007 ms
9 180.87.12.110 115.935 ms 115.183 ms 109.193 ms
10 180.87.181.18 120.020 ms 119.115 ms 119.052 ms
11 116.0.90.18 105.569 ms 117.331 ms 109.726 ms
12 58.138.82.5 123.795 ms 58.138.82.17 124.054 ms 58.138.82.5 124.505 ms
13 58.138.80.214 109.070 ms 58.138.80.182 119.714 ms 58.138.80.190 119.177
ms
14 58.138.112.150 158.523 ms 163.192 ms 58.138.112.146 133.983 ms
15 58.138.112.110 164.073 ms 112.243 ms 58.138.112.102 158.377 ms
16 210.138.9.166 669.234 ms 669.036 ms 676.342 ms
17 133.31.14.2 662.272 ms 686.980 ms 683.806 ms
18 133.31.130.35 671.550 ms 672.716 ms 666.090 ms
hmm.. .
so doing the go up at the end thing. Curiously my mtr I'd left running to Japan
went a bit lower. i wonder if that is congestion due to the cable break.
if I trace to www.iij.ad.jp it's a bit better
traceroute to 210.130.137.80 (210.130.137.80), 30 hops max, 40 byte packets
1 103.6.87.10 3.242 ms 3.212 ms 3.219 ms
2 103.6.87.1 3.207 ms 5.543 ms 8.288 ms
3 180.179.33.245 3.141 ms 3.131 ms 3.121 ms
4 180.179.37.93 3.082 ms 3.073 ms 3.061 ms
5 124.124.62.162 8.293 ms 8.296 ms 8.317 ms
6 115.255.236.2 9.327 ms 3.651 ms 3.832 ms
7 * * *
8 62.216.128.73 124.387 ms 124.388 ms 124.376 ms
9 85.95.26.125 125.702 ms 123.936 ms 123.928 ms
10 85.95.26.90 121.167 ms 85.95.26.206 118.956 ms 85.95.26.90 122.680 ms
11 85.95.26.118 123.698 ms 123.188 ms 122.328 ms
12 210.173.176.233 163.003 ms 123.431 ms 124.528 ms
13 58.138.80.105 113.266 ms 58.138.80.113 129.583 ms 58.138.80.109 118.138
ms
14 58.138.82.234 113.473 ms 58.138.80.242 123.230 ms 58.138.82.226 132.090
ms
15 58.138.104.30 132.103 ms 130.376 ms 129.648 ms
16 210.130.137.80 121.525 ms 119.889 ms 121.886 ms
and from NZ it's 165 msec.
then you still need good connectivity to that host in india though.. best i can
do is
trace back to the gateway you were using.
traceroute to 188.120.247.254 (188.120.247.254), 30 hops max, 40 byte packets
1 103.6.87.10 1.046 ms 1.099 ms 1.453 ms
2 103.6.87.1 1.915 ms 1.994 ms 2.532 ms
3 180.179.33.245 1.062 ms 1.361 ms 1.356 ms
4 180.179.37.89 0.834 ms 0.836 ms 0.825 ms
5 59.163.105.162 2.411 ms 2.403 ms 2.394 ms
6 * * *
7 180.87.39.25 28.356 ms 28.308 ms 28.721 ms
8 80.231.130.5 154.868 ms 180.87.38.1 141.104 ms 80.231.130.5 158.024 ms
9 80.231.217.17 145.271 ms 165.504 ms 80.231.130.2 151.032 ms
10 80.231.217.6 142.950 ms 142.813 ms 142.367 ms
11 80.231.154.17 144.586 ms 80.231.154.70 141.904 ms 80.231.153.122 162.620
ms
12 80.231.153.54 144.136 ms 195.219.50.2 150.734 ms 195.219.50.42 153.955 ms
13 195.219.156.134 152.922 ms 154.504 ms 152.204 ms
14 195.219.148.42 170.707 ms 177.783 ms 195.219.148.90 177.228 ms
15 81.211.5.146 220.522 ms * *
16 81.211.5.146 209.135 ms * 81.211.5.146 209.194 ms
17 213.219.206.18 203.389 ms 200.132 ms 81.211.5.146 213.684 ms
18 * 213.219.206.18 205.904 ms *
19 * * *
And yeah it's way too high, and oesn't seem to even get to there.
There may be better routes through Pakistan, as I seem to remember that they use
both Asia routes and Europe routes.
Best I can seem to find is Japan <-> India of 125 to 132 msec, India <-> Uk of
161 msec.
And the route from UK to Japan was like 278 to 285 going via new york/los
angeles.
That said the Japan traffic to India was going via Singapore, there may be a
more direct
path. And I don't know if 161 is good for India <-> UK.
There's meant to be some new cable between Japan and Europe through Russia,
which may help
things.
http://arstechnica.com/business/2012/03/europe-moving-60-ms-closer-to-japan-with-new-undersea-cables/
Ben.
------------------------------
Message: 4
Date: Wed, 16 Jan 2013 11:50:43 +0100
From: Nicolas Hyvernat <[email protected]>
To: [email protected]
Subject: Re: [outages] SEA-ME-WE3 undersea cable cut
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Wed, Jan 16, 2013 at 08:05:05PM +1300, Ben Aitchison wrote:
> Curious. Russia may be even worse. I must admit I don't know a lot about
> Europe
> routing. What I did find earlier was that India from UK wasn't too bad,
> using the
> looking glass server of vr.org which has lots of locations.
Between Mumbai (India) and Marseille (France), you have SMW4, TGN-EA,
SEACOM, etc... => about 100ms.
Note: Marseille is at about 21ms of London via Paris.
> Best I can seem to find is Japan <-> India of 125 to 132 msec, India <-> Uk
> of 161 msec.
>
> And the route from UK to Japan was like 278 to 285 going via new york/los
> angeles.
>
> That said the Japan traffic to India was going via Singapore, there may be a
> more direct
> path. And I don't know if 161 is good for India <-> UK.
So far, from UK/France, with cables I've seen in use, you go East via
India to reach: Singapore, Hong-Kong.
But then, to reach Japan, you go West, via North America.
You can take a look at: http://www.submarinecablemap.com/
--
Nicolas Hyvernat
------------------------------
Message: 5
Date: Wed, 16 Jan 2013 12:14:42 +0000
From: Martin Hepworth <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [outages] SEA-ME-WE3 undersea cable cut
Message-ID:
<cagdkor+jonoidy+x-sftbxbo6zfxkf48jyst4xrfvtxzrqe...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Uk to singapore and Oz go west from uk across both Atlantic and Pacific.
Routes to Oz vary across pacific day on day eithe via japan/singapore or
southerncross cable to nz first
Martin
On Wednesday, 16 January 2013, Nicolas Hyvernat wrote:
> On Wed, Jan 16, 2013 at 08:05:05PM +1300, Ben Aitchison wrote:
> > Curious. Russia may be even worse. I must admit I don't know a lot
> about Europe
> > routing. What I did find earlier was that India from UK wasn't too bad,
> using the
> > looking glass server of vr.org which has lots of locations.
>
> Between Mumbai (India) and Marseille (France), you have SMW4, TGN-EA,
> SEACOM, etc... => about 100ms.
> Note: Marseille is at about 21ms of London via Paris.
>
> > Best I can seem to find is Japan <-> India of 125 to 132 msec, India <->
> Uk of 161 msec.
> >
> > And the route from UK to Japan was like 278 to 285 going via new
> york/los angeles.
> >
> > That said the Japan traffic to India was going via Singapore, there may
> be a more direct
> > path. And I don't know if 161 is good for India <-> UK.
>
> So far, from UK/France, with cables I've seen in use, you go East via
> India to reach: Singapore, Hong-Kong.
> But then, to reach Japan, you go West, via North America.
>
> You can take a look at: http://www.submarinecablemap.com/
>
> --
> Nicolas Hyvernat
> _______________________________________________
> Outages mailing list
> [email protected] <javascript:;>
> https://puck.nether.net/mailman/listinfo/outages
>
--
--
Martin Hepworth, CISSP
Oxford, UK
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages/attachments/20130116/ca92452d/attachment.html>
------------------------------
_______________________________________________
Outages mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages
End of Outages Digest, Vol 56, Issue 12
***************************************
