54 Bigleaf incidents · februar 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.
21. oktober blev Bigleaf Networks og en delmængde af Bigleaf kundesider / kredsløb påvirket af problemer med forbindelse på grund af en forkert konfiguration med en opstrøms peering udbyder i vores NYC PoP. Anslagstidspunkt: 10 / 21 - 12: 54 Per opstrøms peering udbyder, problemerne var forårsaget af en forkert konfiguration på peering placering og påvirket meget af forbindelsen med NYIIX / Telehouse peering facilitet i NYC, hvor mange netværk og cloud-forbindelse konvergere. Selv om virkningen med denne peering udbyder er betydelig, Bigleaf Networks var i stand til at stole på alternative udbydere og stier til at gå rundt om disse spørgsmål, når de blev opdaget. En delmængde af Bigleaf kunder blev påvirket af disse begivenheder i løbet af disse routing ændringer og undgå denne berørte netværkssti - hvilket resulterede i nogle steder eller kredsløb miste forbindelse i 2- 5 minutter i den berørte tid af virkningen ovenfor. På nuværende tidspunkt har vores team bekræftet med opstrøms peering udbyder, at spørgsmål er blevet løst, men vi fortsætter med at overvåge tæt.
Automatisk oversat fra den officielle hændelsesopdatering.
Den 19. oktober, 20. og 22. oktober, Bigleaf Networks og en delmængde af Bigleaf kundesteder / kredsløb i vores NYC PoP blev påvirket af forbindelse problemer med en opstrøms netværk og rygrad udbyder skyldes en række strømsvigt på en opstrøms facilitet i NYC. Anslagstider 10 / 19 - 8: 32 PM ET to 1: 14 AM ET 10 / 20 - 4: 56 PM ET to 1: 31 AM ET 10 / 22 - 6: 43 Per opstrøms udbydere, der blev påvirket, deres datacenter / netværk facilitet i NYC mistede deres powergrid på 10 / 19 og har haft flere andre power / backup generator problemer efter den første fiasko. Selv om de tilfælde af nedetid med denne udbyder er betydelige, Bigleaf Networks var i stand til at stole på alternative udbydere og veje til at gå rundt om disse spørgsmål, når de blev opdaget. En delmængde af Bigleaf kunder blev påvirket af disse begivenheder i løbet af disse routing ændringer og undgå denne berørte netværkssti - hvilket resulterede i nogle steder eller kredsløb miste forbindelse i 2- 5 minutter i de berørte tider af virkning ovenfor. På nuværende tidspunkt arbejder vores team tæt sammen med opstrømsudbyderen for at sikre, at alle relaterede spørgsmål løses, og vi fortsætter med at overvåge nøje.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undersøger i øjeblikket forbindelsen til Bigleaf Cloud Connect Dashboard. Netværksforbindelser bør ikke påvirkes.
Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.
Et fix er blevet gennemført, og vi overvåger resultaterne.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
