Is BigLeaf down?

A subset of customers served out of the NYC region may have experienced some packet loss and congestion 12:53PM EDT to 1:16PM EDT to due to an upstream network provider issue. At this time the issues have stabilized while our Network Operations group continues to monitor.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

This incident has been resolved.

On October 21st Bigleaf Networks and a subset of Bigleaf customer sites/circuits were impacted by connectivity issues due to a misconfiguration with an upstream peering provider in our NYC PoP. Time of impact: 10/21 - 12:54 AM EDT to 1:16 PM EDT Per the upstream peering provider, the issues were caused by a misconfiguration at the peering location and impacted much of the connectivity with the NYIIX/Telehouse peering facility in NYC where many networks and cloud connectivity converge. Although the instance of impact with this peering provider is significant, Bigleaf Networks was able to rely on alternative providers and paths to route around these issues once they were detected. A subset of Bigleaf customers were impacted by these events during those routing changes and avoiding this affected network path - which resulted in some sites or circuits losing connectivity for 2-5 minutes during the affected time of impact above. At this time, our team has confirmed with the upstream peering provider that issues have been resolved but we continue to monitor closely.

On October 19th, 20th, and 22nd, Bigleaf Networks and a subset of Bigleaf customer sites/circuits in our NYC PoP were impacted by connectivity issues with an upstream network and backbone provider due a series of power failures at an upstream facility in NYC. Times of impact: 10/19 - 8:32 PM EDT to 1:14 AM EDT 10/20 - 4:56 PM EDT to 1:31 AM EDT 10/22 - 6:43 AM EDT to 8:01 AM EDT Per the upstream providers that were impacted, their datacenter/network facility in NYC lost their powergrid on 10/19 and have had several other power/backup generator issues following the initial failure. Although the instances of downtime with this provider are significant, Bigleaf Networks was able to rely on alternative providers and paths to route around these issues once they were detected. A subset of Bigleaf customers were impacted by these events during those routing changes and avoiding this affected network path - which resulted in some sites or circuits losing connectivity for 2-5 minutes during those affected times of impact above. At this time, our team is working closely with the upstream provider to ensure all related issues are resolved and we continue to monitor closely.

We are currently investigating connectivity to the Bigleaf Cloud Connect Dashboard. Network connectivity should not affected.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.