[125404] in North American Network Operators' Group
Re: Undersea cable cut?
daemon@ATHENA.MIT.EDU (Chris McDonald)
Wed Apr 14 14:19:04 2010
In-Reply-To: <768FB653686AE54A9B4FB9A1503F03F51C9BFF502A@TENK7MVB.prod.travp.net>
Date: Wed, 14 Apr 2010 14:18:49 -0400
From: Chris McDonald <copraphage@gmail.com>
To: "St. Onge,Adam" <ASTONGE@travelers.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
There's a cut in SWM4
*SMW4 Segment 4.1 cable fault*
Cable shunt fault developed on SMW4 segment 4.1 (Egypt / Alexandria =96
Branching Unit #4A onward France / Marseilles) at 07:15GMT on 14-Apr. 2010.
However the shunt fault has further deteriorated and the cable segment was
down at 10:03GMT. Only four unprotected Singapore =96 London / Frankfurt
STM-4c IP trunks were being affected.
SMW4 NOC updated that there is a shunt fault in segment 4.1 between Egypt =
/
Alexandria and France / Marseilles with cable fault on Fiber Pair #2 at
1886.152 km from Alexandria towards Palermo. The traffic landed at Palermo
onwards to Europe was being affected, while the traffic running between
Alexandria and Marseilles via Fiber Pair #1 is still maintained.
On Wed, Apr 14, 2010 at 2:13 PM, St. Onge,Adam <ASTONGE@travelers.com>wrote=
:
> Seeing a serious uptick in latency to India from North America and am
> hearing reports of an undersea cable cut in the Mediterranean? Has anyone
> else heard something similar?
>
> Thanks,
> Adam
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> This communication, including attachments, is confidential, may be subjec=
t
> to legal privileges, and is intended for the sole use of the addressee. A=
ny
> use, duplication, disclosure or dissemination of this communication, othe=
r
> than by the addressee, is prohibited. If you have received this
> communication in error, please notify the sender immediately and delete o=
r
> destroy this communication and all copies.
>
