Month: August 2014

Fusion/FlexLink Outage

Today, August 3, starting at 5:20pm, links serving Fusion/FlexLink customers in the Fort Brag and Mendocino areas went down. We are currently investigating the issue and will update as soon as we have more information.

Update: A traffic accident in Mendocino caused a fiber cut that appears to be the root cause of this outage. Still no ETR, but we will update as more information becomes available.

Update: AT&T has found the cable cut and has dispatched to start repairs. They will attempt to pull slack in the cable in order to restore service tonight, however there is no ETR until the extent of the damage has been fully assessed.

Update: A splice team is on site with an ETR of 7:15am

Update: AT&T has encountered trouble while restoring service with a new ETR of 10:45am

Update: AT&T splicers are still working in an effort to restore service, currently no ETR

Update: AT&T has discovered that the affected fiber cable was damaged in more than one place. They are currently working to repair the additional damage.

Update (9:25pm): AT&T has notified us that they are currently working on our fiber spans

Update: (12:52am): AT&T was unable to use existing damaged cable, and has an ETA of 3:00am for 6500ft of new cable so they can begin splicing

Update (9:57am): AT&T has located cable and brought it onto the job site. Latest ETR is 4:00pm

Update (2:53pm): Service appears to be restored, however we have not received confirmation from AT&T that our circuits are stable. We will update again as soon as any additional information is available.

Update (11:26pm): At 11:15pm, connectivity was lost for approximately 10 minutes while finalizing repairs. Redundant circuits have been restored and we do not anticipate any further service interruption. We apologize for this inconvenience and appreciate your patience. – Tomoc and the Sonic Team

-Tomoc

FlexLink Outages – San Francisco

We are currently investigating an outage involving some FlexLink customers in the San Francisco area following last nights code upgrades. We will update this post when we believe we have found the cause and solution to this issue.

– NOC