54 incidente Bigleaf înregistrate începând din februarie 2022, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
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.
Pe 21 octombrie, rețelele Bigleaf și un subset de site-uri/circuite ale clienților Bigleaf au fost afectate de probleme de conectivitate din cauza unei configurații greșite cu un furnizor de peeering în amonte în NYC PoP nostru. Ora impactului: 10/21 - 12:54 PM EDT la 1:16 PM EDT În ceea ce privește furnizorul de peeering din amonte, problemele au fost cauzate de o configurare greșită la locul de peeering și au afectat o mare parte a conectivității cu facilitatea de peeering NYIIX/Telehouse din NYC, unde multe rețele și conectivitatea cloud converg. Deși situația impactului cu acest furnizor de peeering este semnificativă, Bigleaf Networks a fost în măsură să se bazeze pe furnizori alternativi și căi de a călători în jurul acestor probleme odată ce au fost detectate. Un subset de clienți Bigleaf au fost afectate de aceste evenimente în timpul acelor modificări de rutare și evitând această cale de rețea afectată - ceea ce a dus la unele site-uri sau circuite pierde conectivitate timp de 2-5 minute în timpul timpului afectat de impact de mai sus. În acest moment, echipa noastră a confirmat cu furnizorul de peeering din amonte că problemele au fost rezolvate, dar continuăm să monitorizăm îndeaproape.
Traducere automată din actualizarea oficială a incidentului.
Pe 19 octombrie, 20 și 22, Bigleaf Networks și un subset de site-uri/circuite ale clienților Bigleaf din NYC PoP au fost afectate de probleme de conectivitate cu o rețea în amonte și furnizor de coloană vertebrală din cauza unei serii de defecțiuni de energie electrică într-o instalație în amonte din NYC. Timpurile impactului: 10/19 - 8:32 PM EDT la 1:14 AM EDT 10/20 - 4:56 PM EDT la 1:31 AM EDT 10/22 - 6:43 AM EDT la 8:01 AM EDT Pe furnizorii din amonte care au fost afectați, unitatea lor de datecenter/rețea din NYC și-a pierdut rețeaua electrică pe 10/19 și au avut mai multe alte probleme cu generatorul de putere/backup în urma eșecului inițial. Deși cazurile de timp liber cu acest furnizor sunt semnificative, Bigleaf Networks a fost capabil să se bazeze pe furnizori alternativi și căi de a călători în jurul acestor probleme odată ce au fost detectate. Un subset de clienți Bigleaf au fost afectate de aceste evenimente în timpul acelor modificări de rutare și evitând această cale de rețea afectată - ceea ce a dus la unele site-uri sau circuite pierde conectivitate timp de 2-5 minute în timpul acelor momente afectate de impact de mai sus. În acest moment, echipa noastră lucrează îndeaproape cu furnizorul din amonte pentru a se asigura că toate problemele legate sunt rezolvate și continuăm să monitorizăm îndeaproape.
Traducere automată din actualizarea oficială a incidentului.
În prezent investigăm conectivitatea la tabloul de bord Bigleaf Cloud Connect. Conectivitatea la rețea nu ar trebui afectată.
Problema a fost identificată și se pune în aplicare o soluție.
A fost implementată o soluţie şi monitorizăm rezultatele.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
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.
