[113017] in North American Network Operators' Group
Re: Fiber cut on Irish Sea
daemon@ATHENA.MIT.EDU (Ken Gilmour)
Sun Mar 29 11:44:45 2009
In-Reply-To: <416212.45432.qm@web52608.mail.re2.yahoo.com>
Date: Sun, 29 Mar 2009 09:42:42 -0600
From: Ken Gilmour <ken.gilmour@gmail.com>
To: isabeldias1@yahoo.com
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi,
This has been fixed now. I will follow up directly with PE for an RFO.
Thanks for your help on and off list.
Regards,
Ken
2009/3/29 isabel dias <isabeldias1@yahoo.com>:
>
> Are you able to provide historical information on the incident/outgae you have experienced?
>
> Are you able to provide an egress and/or igress traffic coming in and out of your network to make sure your traffic was crossing that transmission path?
>
> I guess you must have visibility of planned work or outage notification if anything happen and you were directly affected- YES/NO?
>
>
>
> --- On Sun, 3/29/09, Ken Gilmour <ken.gilmour@gmail.com> wrote:
>
>> From: Ken Gilmour <ken.gilmour@gmail.com>
>> Subject: Re: Fiber cut on Irish Sea
>> To: isabeldias1@yahoo.com
>> Cc: nanog@nanog.org
>> Date: Sunday, March 29, 2009, 5:04 PM
>> We received the report from Packet Exchange, however they
>> are not the
>> owners of the cable. I assume they just rent spectrum.
>>
>> 2009/3/29 isabel dias <isabeldias1@yahoo.com>:
>> >
>> > affecting whom? and who's network?
>> >
>> >
>> > --- On Sun, 3/29/09, Ken Gilmour
>> <ken.gilmour@gmail.com> wrote:
>> >
>> >> From: Ken Gilmour <ken.gilmour@gmail.com>
>> >> Subject: Fiber cut on Irish Sea
>> >> To: nanog@nanog.org
>> >> Date: Sunday, March 29, 2009, 4:55 PM
>> >> Hi There,
>> >>
>> >> Since we use a vendor of "the vendor" of
>> two
>> >> Irish sea submarine
>> >> cables I am wondering if anyone has first hand
>> information
>> >> on the
>> >> fiber cut this morning? Does anyone have a status
>> update on
>> >> what is
>> >> happening? I am getting some Chinese whispers
>> going on
>> >> here.
>> >>
>> >> Thanks!
>> >>
>> >> Ken
>> >
>> >
>> >
>> >
>
>
>
>
