Network Performance Issues - NYC

Summary

Network Performance Issues - NYC

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 PM 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.

• Started

  Oct 21, 2026 · 10:00 AM

• Resolved

  Oct 21, 2026 · 10:00 AM

• Duration

  < 1m

• Severity

  Minor

• ✓

  Resolved

  Oct 22 · 1:15 PM Bigleaf Networks

  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 PM 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.