54 Bigleaf incidents · febbraio 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.
Il 21 ottobre Bigleaf Networks e un sottoinsieme dei siti/circuiti dei clienti Bigleaf sono stati colpiti da problemi di connettività a causa di una cattiva configurazione con un provider di peering a monte nel nostro NYC PoP. Tempo di impatto: 10/21 - 12:54 PM EDT a 1:16 PM EDT Per il provider di peering a monte, i problemi sono stati causati da una cattiva configurazione nella posizione di peering e hanno colpito gran parte della connettività con la struttura di peering NYIIX/Telehouse a New York, dove molte reti e connettività cloud convergono. Anche se l'istanza di impatto con questo peering provider è significativa, Bigleaf Networks è stato in grado di fare affidamento su fornitori alternativi e percorsi di percorso intorno a questi problemi una volta che sono stati rilevati. Un sottoinsieme di clienti Bigleaf è stato influenzato da questi eventi durante quei cambiamenti di routing ed evitando questo percorso di rete interessato - che ha portato alcuni siti o circuiti che perdono la connettività per 2-5 minuti durante il tempo di impatto sopra interessato. In questo momento, il nostro team ha confermato con il provider di peering a monte che i problemi sono stati risolti, ma continuiamo a monitorare da vicino.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Il 19 ottobre, 20 e 22 ottobre, Bigleaf Networks e un sottoinsieme di siti/circuiti di clienti Bigleaf nel nostro NYC PoP sono stati colpiti da problemi di connettività con un provider di rete a monte e backbone a causa di una serie di guasti di potenza in una struttura a monte a New York. Tempi di impatto: 10/19 - 8:32 PM EDT a 1:14 10/20 - 16:56 PM EDT a 1:31 AM EDT 10/22 - 6:43 AM EDT a 8:01 AM EDT Per i fornitori a monte che hanno avuto un impatto, il loro datacenter/network di New York ha perso la loro powergrid il 10/19 e hanno avuto diversi altri problemi di generatore di potenza/backup dopo il fallimento iniziale. Anche se le istanze di downtime con questo fornitore sono significative, Bigleaf Networks è stato in grado di fare affidamento su fornitori alternativi e percorsi di percorso intorno a questi problemi una volta che sono stati rilevati. Un sottoinsieme di clienti Bigleaf è stato influenzato da questi eventi durante quei cambiamenti di routing ed evitando questo percorso di rete interessato - che ha portato a alcuni siti o circuiti che perdono la connettività per 2-5 minuti durante quei tempi di impatto sopra colpiti. In questo momento, il nostro team sta lavorando a stretto contatto con il fornitore a monte per garantire che tutti i problemi correlati siano risolti e continuiamo a monitorare da vicino.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo attualmente indagando la connettività al Bigleaf Cloud Connect Dashboard. La connettività di rete non deve essere influenzata.
Il problema è stato identificato e si sta attuando una correzione.
Una soluzione è stata implementata e stiamo monitorando i risultati.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.
