• Home
  • Announcements
  • Platform Events

2019-06-06 - NYJ004 Network Failure (Resolved)

Written by Marissa Orsini

Updated at April 22nd, 2023

Contact Us

  • The Essentials
    FAQs Forms
  • Announcements
    Carrier Events mFax Events Platform Events Release Notes
  • Billing Administration
    Datagate OneBill
  • Faxing
    mFax - Analog mFax - Digital Native Fax
  • Hardware & Software
    Manual Configuration Provisioning NDP Axis Cisco Fanvil Grandstream Polycom Snom Yealink Mobile Applications Desktop Applications Mobile-X SNAPbuilder TeamMate Connector UC Integrator
  • Hosted Voice
    Auto Attendants Branding Call Queues Call Routing CDRs Conferencing E-911 Features Fraud Integrations Inventory / Phone Numbers Local & Toll Free Porting Onboarding Recommendations SNAP.HD SIP Trunking SMS / MMS Users Voicemail Caller ID
  • Troubleshooting
    VoIPmonitor Firewalls PBX
  • Ray's Stuff
+ More

Table of Contents

Affected Services Event Summary Event Timeline (All times 24-hour format, EST) June 6th, 2019 June 7th, 2019 Root Cause Analysis Future Preventative Action

Event Description: NYJ004 Loss of upstream connectivity

Event Start Time: 2019-06-06 23:24 PM EST

Event End Time: 2019-06-07 04:39 PM EST

RFO Issue Date: 2019-06-07

 

 

Affected Services

None. Connectivity to devices registered to NYJ would've been affected. However, services were already shut down for maintenance.


Event Summary

On June 6th, 2019, at 23:24 EDT, there was a fiber outage reported at the NYJ004 Data Center. This impacted one of the redundant backbone spans providing upstream connectivity to NYJ004. An investigation into the cause of the fiber outage, and restoration of this span, are still underway by the fiber provider. A few hours later at 01:34 EDT, the second event took place at a partner site on the remaining redundant backbone span at the NYJ004 location. This resulted in losing upstream connectivity and isolating the NYJ004 Data Center. At 04:39 EDT INAP Senior Engineers were able to work with field technicians at the partner site to restore connectivity to NYJ004. The root cause of this event is also still under investigation. In summary, these series of events were independent of each other; they are on separate carrier networks, on diverse fiber paths, and are serviced by different fiber providers. The INAP RFO will be updated when both partner's RFO’s are received.


Event Timeline (All times 24-hour format, EST)

June 6th, 2019

  •  Major Incident Fiber outage on Backbone 2. IMPACT Loss of Redundancy

June 7th, 2019

  • 00:16 Fiber provider acknowledges Major Incident and investigating fiber cut.
  • 01:34 Secondary incident occurred, which impacted a diverse carrier of Backbone 1. IMPACT START NYJ004 Isolated
  • 01:45 NOC Management paged.
  • 02:00 Major Incident declared, senior engineers paged, and customers notified.
  • 02:30 INAP Engineers troubleshooting connectivity on Backbone 1.
  • 03:30 Continuing restoration process of Backbone 1.
  • 04:39 Fiber issue restored on Backbone 1 at an INAP partner Data Center. IMPACT END Connectivity restored
  • 05:00 Backbone 2 Fiber outage ongoing. The Fiber provider located the fiber cut and is dispatching additional crews.
  • 08:53 Backbone 2. All fiber crews are at the cut location and are beginning repair work. 
  • 11:27 Backbone 2. Fiber provider reports there are 1200 feet of damaged cable to repair.
  • 14:28 Backbone 2. The Fiber provider has completed laying a new span of fiber and is working on securing it for splicing.

Root Cause Analysis

Two separate and isolated events occurred which severed both redundant backbone spans that provide connectivity to the NYJ004 Data Center.


Future Preventative Action

INAP is doing a site audit and root cause investigation to the outage that occurred at the partner site.

INAP has requested the fiber carrier send a formal RFO on the current fiber cut impacting the redundant link.

INAP is deploying updates to the NYJ004 infrastructure to provide local egress connectivity.

An updated RFO will be sent upon review of the two partners RFO

 

resolved network failure

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • 2019-05-06 - Atlanta Network Failure (Resolved)

Knowledge Base Software powered by Helpjuice

Expand