54 Bigleaf incidents · février 2022 — official updates, affected components, duration and resolution details.
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.
Le 21 octobre, Bigleaf Networks et un sous-ensemble de sites/circuits clients Bigleaf ont été touchés par des problèmes de connectivité en raison d'une mauvaise configuration avec un fournisseur de services de paris en amont dans notre PoP de New York. Heure de l'impact: 10/21 - 12:54 HAE à 13:16 HAE Par le fournisseur de services de pairs en amont, les problèmes ont été causés par une mauvaise configuration à l'emplacement de services de pairs et ont eu des répercussions sur une grande partie de la connectivité avec l'installation de services de pairs NYIX/Telehouse à New York, où de nombreux réseaux et la connectivité cloud convergent. Bien que le cas d'impact avec ce fournisseur de services de pairs soit important, Bigleaf Networks a pu compter sur d'autres fournisseurs et chemins pour contourner ces problèmes une fois qu'ils ont été détectés. Un sous-ensemble de clients Bigleaf ont été touchés par ces événements au cours de ces changements de routage et d'éviter ce chemin de réseau affecté - ce qui a entraîné la perte de connectivité de certains sites ou circuits pendant 2 à 5 minutes pendant la période d'impact touchée ci-dessus. À l'heure actuelle, notre équipe a confirmé avec le fournisseur de services de pairs en amont que les problèmes avaient été résolus, mais nous continuons de surveiller de près.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Les 19, 20 et 22 octobre, Bigleaf Networks et un sous-ensemble de sites/circuits clients Bigleaf dans notre PoP de NYC ont été touchés par des problèmes de connectivité avec un réseau en amont et un fournisseur de base en raison d'une série de pannes d'électricité dans une installation en amont à NYC. Temps d'impact: 10/19 - 20:32 HAE à 1:14 HAE 10/20 - 16:56 HAE à 1:31 HAE 10/22 - 6:43 HAE à 8:01 HAE Par les fournisseurs en amont qui ont été touchés, leur datacenter/network installation à New York a perdu leur réseau électrique le 10/19 et ont eu plusieurs autres problèmes de générateur d'alimentation / sauvegarde suite à la défaillance initiale. Bien que les temps d'arrêt avec ce fournisseur soient importants, Bigleaf Networks a pu compter sur d'autres fournisseurs et chemins pour contourner ces problèmes une fois qu'ils ont été détectés. Un sous-ensemble de clients Bigleaf ont été touchés par ces événements au cours de ces changements de routage et d'éviter ce chemin de réseau affecté - ce qui a entraîné la perte de connectivité de certains sites ou circuits pendant 2-5 minutes pendant les périodes d'impact touchées ci-dessus. À l'heure actuelle, notre équipe travaille en étroite collaboration avec le fournisseur en amont pour s'assurer que tous les problèmes connexes sont résolus et que nous continuons de surveiller de près.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous examinons actuellement la connectivité au tableau de bord Bigleaf Cloud Connect. La connectivité réseau ne devrait pas être affectée.
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
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.
