rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#2744 — FS#6704 — MTL/world

Attached to Project— Network
Incident
Whole Network
CLOSED
100%
Montreal / Newark via Hibernia down
Montreal / Newark via Level3 down
Montreal / Toronto up
Toronto / Newark down

Montreal / London up

Therefore Montreal is accessible via.. London.
We strongly need to finish our own network.

one of the links Newark / Chicago is down too.
Date:  Sunday, 13 May 2012, 01:35AM
Reason for closing:  Done
Comment by OVH - Thursday, 10 May 2012, 00:20AM

A cutoff of the optical fiber in New York.


Comment by OVH - Thursday, 10 May 2012, 00:21AM

16:25 GMT - Field Services has confirmed that excavation crews are on site; however, awaiting clearance to the area from a highway engineer to proceed with excavation required to begin fiber
repair. There is no estimated time for access to the area to perform excavation work. The conduit vendor's restoration crews also remain on standby at the site. The damage to the conduit is
extensive, and there is no estimated time for restoration available at this time.

15:34 GMT - Field Services has confirmed that fiber damage resulted from third party construction being performed to install a new overpass bridge. A steel pole was being set, which damaged
the vendors conduit. This conduit carries multiple carriers fiber. The duct is 18 feet underground, which will require excavation to uncover for repair. The Transport NOC has
requested a second level escalation with the conduit vendor for repair; however, there is no estimated time of arrival for fiber restoration crews.

14:25 GMT - The fiber cut has been isolated in Tuxedo, NY. At this time, restoration crews are awaited onsite. There is no estimated time of arrival available at this time. The Transport NOC has
escalated the issue for repair with the conduit vendor, responsible for repair.

13:51 GMT - The field technician arrived onsite in Suffern, NY and shot the fiber, which indicates a fiber cut 7.7 miles out from the site. The Transport NOC has confirmed that this is Level 3 fiber;
however, the vendor that owns the conduit is responsible for repair. The conduit vendor has been engaged, and they are dispatching restoration crews at this time. There is no estimated time of
arrival for restoration crews. In the meantime, the second Level 3 field technician continues driving the route in an attempt to visibly locate the fiber damage.

13:01 GMT - The Transport NOC has confirmed that the fiber cut is affecting multiple systems / networks. The field technician continues en route to the Suffern, NY site in order to perform fiber
testing to isolate the issue further. Estimated time of arrival to the site is 30 minutes. In the meantime, a second field technician continues to drive the route of the suspected damage in an
attempt to visibly locate any fiber issues.

12:05 GMT - The Transport NOC responded to loss of signal alarms, indicating a fiber cut in the New Paltz, NY area. Unprotected traffic is impacted. The Transport NOC is engaging Field Services to
dispatch to the Saffron, NY site to shoot the fiber to isolate the issue further. There is no estimated time of arrival available at this time.


Comment by OVH - Thursday, 10 May 2012, 07:48AM

Montreal via Level3are back. It flaps via Hibernia.
Toronto via Level3 is not back yet.
Chicago via Telia is back.


Comment by OVH - Thursday, 10 May 2012, 07:48AM

The field technician on site has advised that the splice crew has completed about 36 of the fibers and the Transport NOC confirmed that a large portion of alarms have cleared,
but there are many to go. The field technician gave a tentative ETR of 3 hours for the 120-count fiber, and clarified that crews continue to work on getting part of the
96-count fiber out before they can begin prepping it for splicing.


Comment by OVH - Sunday, 13 May 2012, 01:35AM

it has been fixed. a nice disaster confirms whether the network to USA should be redundant or not.