54 Bigleaf incidents · Cʼhwevrer 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.
Em 21 de outubro Bigleaf Networks e um subconjunto de sites/circuitos de clientes Bigleaf foram impactados por problemas de conectividade devido a uma configuração incorreta com um provedor de pares upstream em nosso NYC PoP. Tempo de impacto: 10/21 - 12:54 EDT às 1:16 EDT De acordo com o provedor de peering upstream, os problemas foram causados por uma má configuração no local de peering e impactou grande parte da conectividade com a instalação de peering NYIIX/Telehouse em NYC, onde muitas redes e conectividade em nuvem convergem. Embora a instância de impacto com este provedor de pares seja significativa, Bigleaf Networks foi capaz de confiar em provedores alternativos e caminhos para contornar essas questões uma vez que eles foram detectados. Um subconjunto de clientes Bigleaf foi impactado por esses eventos durante essas mudanças de roteamento e evitando esse caminho de rede afetado - o que resultou em alguns sites ou circuitos perdendo conectividade por 2-5 minutos durante o tempo de impacto afetado acima. Neste momento, nossa equipe confirmou com o provedor de pesquisa a montante que os problemas foram resolvidos, mas continuamos a monitorar de perto.
Traduzido automaticamente da atualização oficial do incidente.
Em 19, 20 e 22 de outubro, Bigleaf Networks e um subconjunto de sites/circuitos de clientes Bigleaf em nosso NYC PoP foram impactados por problemas de conectividade com uma rede upstream e provedor de backbone devido a uma série de falhas de energia em uma instalação upstream em NYC. Tempos de impacto: 10/19 - 8:32 EDT até 1:14 EDT 10/20 - 4:56 EDT até 1:31 EDT 10/22 - 6:43 EDT às 8:01 EDT De acordo com os provedores a montante que foram impactados, seu datacenter/instalação de rede em NYC perdeu sua rede de energia em 10/19 e tiveram vários outros problemas de gerador de energia / backup após a falha inicial. Embora as instâncias de tempo de inatividade com este provedor sejam significativas, Bigleaf Networks foi capaz de confiar em provedores alternativos e caminhos para percorrer essas questões uma vez que eles foram detectados. Um subconjunto de clientes Bigleaf foi impactado por esses eventos durante essas mudanças de roteamento e evitando este caminho de rede afetado - o que resultou em alguns sites ou circuitos perdendo conectividade por 2-5 minutos durante os tempos afetados de impacto acima. Neste momento, nossa equipe está trabalhando em estreita colaboração com o provedor upstream para garantir que todas as questões relacionadas sejam resolvidas e continuamos a monitorar de perto.
Traduzido automaticamente da atualização oficial do incidente.
Atualmente estamos investigando a conectividade com o Painel de Conexão Bigleaf Cloud. A conectividade da rede não deve ser afetada.
A questão foi identificada e está a ser implementada uma solução.
Foi implementada uma correção e estamos monitorando os resultados.
Este incidente foi resolvido.
Traduzido automaticamente da atualização oficial do 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.
