54 recorded Bigleaf incidents since February 2022, with official updates, affected components, duration and resolution information.
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.
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 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.
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.
We are currently investigating an issue with Bigleaf Cloud Connect Dashboard reporting on CPE and API functionality. Note: Network traffic and connectivity should not be impacted.
This incident has been resolved.
We are currently investigating network congestion issues that are affecting a subset of customers served out of our NYC gateway cluster. Customer sites may see performance impact over some ISP circuits, causing intermittent packet loss and latency.
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.
We are currently investigating network congestion issues that are impacting a small subset of sites connected to our ATL gateway cluster. To verify if your site is impacted after logging into the Bigleaf Cloud Connect dashboard , follow this link to a filtered list of your accessible sites that are impacted by these issues.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating network congestion issues that are impacting a subset of sites connected to our LAX gateway cluster.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A small subset of customers served out of our Los Angeles PoP may have experienced one minute of service interruption or missing performance metrics between 11:02am and 11:05am PST after an emergency change was made to avoid an upstream provider with congestion issues. We are continuing to monitor network performance after these changes, and all connectivity in this region should be performing as expected.
This incident has been resolved.
We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We will be undergoing emergency maintenance in our Seattle Gateway Cluster. Expected Impact: No network connectivity impact is expected If you’re curious about the types of maintenance that we perform, feel free to check out the Maintenance section of our SLA here: http://www.bigleaf.net/sla . If you have any questions or concerns about this maintenance process, please let us know.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive. Customer and network traffic is unaffected.
We have taken steps to mitigate this issue and are seeing improved response times. We are continuing to monitor the situation.
This incident has been resolved.
We are currently investigating an issue with missing metrics and reporting in the Bigleaf Cloud Connect Dashboard.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We will be undergoing emergency maintenance in our Frankfurt, DE Gateway Cluster. Expected Impact: Customers may experience additional latency during this time, and up to three 10-second packet loss events. If you’re curious about the types of maintenance that we perform, feel free to check out the Maintenance section of our SLA here: http://www.bigleaf.net/sla . If you have any questions or concerns about this maintenance process, please let us know.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating slowness and intermittent responsiveness with our Bigleaf Cloud Connect Dashboard. Network connectivity is not affected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A small subset of customers served out of our Dallas PoP may experience up to two brief periods of packet loss as our team investigates and works to resolve an issue.
This incident has been resolved.
We are currently investigating an issue impacting a small subset of sites in Atlanta where site and circuit status shows incorrect status of 'offline'. Connectivity and traffic should be functioning as normal despite the alerts, but there may be some brief periods of packet loss while resolving the false alerting issues.
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.
We are currently investigating an issue that is preventing any site configuration changes in the Bigleaf Cloud Connect dashboard from applying the updates to deployed Bigleaf Routers. There should be no impact to site connectivity or alerting.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue as ALL Bigleaf alert emails are not being sent from the Bigleaf Cloud Connect dashboard. This includes StatusPage updates.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for further issues and implemented a temporary change while working towards a permanent fix. Current Impact: - To reduce immediate impact, only HIGH or SITE DOWN severity alert emails will be sent as expected. - Alert severity of MEDIUM or LOW will not receive an email alert at this time despite any user configurations. - Any and all alerts are being displayed correctly on the Site and Alerts sections of the Bigleaf Cloud Connect Dashboard.
This incident has been resolved.
