Störungsverlauf von Bigleaf

1. 21. Oktober 2026 um 18:17 UTCmonitoring

   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.

2. 21. Oktober 2026 um 18:53 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 21. Oktober 2026 um 21:51 UTCresolved

   This incident has been resolved.

1. 22. Oktober 2026 um 20:15 UTCresolved

   Am 21. Oktober waren Bigleaf Networks und eine Teilmenge von Bigleaf-Kundenstandorten / -schaltungen von Verbindungsproblemen betroffen, die auf eine Fehlkonfiguration mit einem Upstream-Peering-Anbieter in unserem NYC-PoP zurückzuführen waren. Zeitpunkt des Aufpralls: 10/21 - 12:54 PM EDT bis 1:16 PM EDT Laut dem Upstream-Peering-Anbieter wurden die Probleme durch eine Fehlkonfiguration am Peering-Standort verursacht und beeinflussten einen Großteil der Konnektivität mit der NYIIX / Telehouse-Peering-Einrichtung in NYC, wo viele Netzwerke und Cloud-Konnektivität konvergieren. Obwohl die Auswirkungen dieses Peering-Anbieters signifikant sind, konnte sich Bigleaf Networks auf alternative Anbieter und Wege verlassen, um diese Probleme zu umgehen, sobald sie erkannt wurden. Eine Teilmenge der Bigleaf-Kunden war von diesen Ereignissen während dieser Routing-Änderungen und der Vermeidung dieses betroffenen Netzwerkpfads betroffen, was dazu führte, dass einige Standorte oder Schaltungen während der betroffenen Zeit des oben genannten Aufpralls für 2-5 Minuten die Konnektivität verloren. Zu diesem Zeitpunkt hat unser Team mit dem Upstream-Peering-Anbieter bestätigt, dass Probleme gelöst wurden, aber wir beobachten weiterhin genau.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Oktober 2026 um 20:12 UTCresolved

   Am 19., 20. und 22. Oktober waren Bigleaf Networks und eine Untergruppe von Bigleaf-Kundenstandorten/-schaltungen in unserem NYC-PoP von Verbindungsproblemen mit einem Upstream-Netzwerk- und Backbone-Anbieter aufgrund einer Reihe von Stromausfällen in einer Upstream-Anlage in NYC betroffen. Aufschlagzeiten: 10/19 - 8:32 PM EDT bis 1:14 AM EDT 10/20 - 4:56 Uhr EDT bis 1:31 Uhr EDT 10/22 - 6:43 Uhr EDT bis 8:01 Uhr EDT Laut den Upstream-Anbietern, die betroffen waren, verlor ihre Rechenzentrums- / Netzwerkeinrichtung in NYC am 10/19 ihr Stromnetz und hatte nach dem anfänglichen Ausfall mehrere andere Probleme mit dem Strom- / Backup-Generator. Obwohl die Ausfallzeiten bei diesem Anbieter signifikant sind, konnte sich Bigleaf Networks auf alternative Anbieter und Pfade verlassen, um diese Probleme zu umgehen, sobald sie erkannt wurden. Eine Teilmenge der Bigleaf-Kunden war von diesen Ereignissen während dieser Routing-Änderungen und der Vermeidung dieses betroffenen Netzwerkpfads betroffen, was dazu führte, dass einige Standorte oder Schaltungen während der oben genannten betroffenen Zeiten für 2-5 Minuten die Konnektivität verloren. Zu diesem Zeitpunkt arbeitet unser Team eng mit dem Upstream-Anbieter zusammen, um sicherzustellen, dass alle damit verbundenen Probleme gelöst werden, und wir überwachen weiterhin genau.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. September 2026 um 13:34 UTCinvestigating

   Wir untersuchen derzeit die Konnektivität mit dem Bigleaf Cloud Connect Dashboard. Die Netzwerkverbindung sollte nicht beeinträchtigt werden.

2. 11. September 2026 um 14:22 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 11. September 2026 um 14:52 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 11. September 2026 um 16:31 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Juli 2026 um 16:55 UTCinvestigating

   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.

2. 8. Juli 2026 um 18:11 UTCresolved

   This incident has been resolved.

1. 18. Juni 2026 um 14:39 UTCinvestigating

   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.

2. 18. Juni 2026 um 15:00 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 18. Juni 2026 um 17:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 18. Juni 2026 um 18:46 UTCresolved

   This incident has been resolved.

1. 30. April 2026 um 17:53 UTCinvestigating

   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.

2. 30. April 2026 um 19:30 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 30. April 2026 um 20:00 UTCresolved

   This incident has been resolved.

1. 20. Februar 2026 um 19:00 UTCinvestigating

   We are currently investigating network congestion issues that are impacting a subset of sites connected to our LAX gateway cluster.

2. 20. Februar 2026 um 19:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 20. Februar 2026 um 21:30 UTCresolved

   This incident has been resolved.

1. 4. Dezember 2025 um 19:31 UTCmonitoring

   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.

2. 4. Dezember 2025 um 23:08 UTCresolved

   This incident has been resolved.

1. 2. Oktober 2025 um 19:54 UTCinvestigating

   We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive.

2. 2. Oktober 2025 um 20:12 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2. Oktober 2025 um 21:57 UTCresolved

   This incident has been resolved.

1. 26. September 2025 um 17:01 UTCinvestigating

   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.

2. 26. September 2025 um 18:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26. September 2025 um 20:30 UTCresolved

   This incident has been resolved.

1. 18. September 2025 um 16:19 UTCinvestigating

   We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive. Customer and network traffic is unaffected.

2. 18. September 2025 um 16:53 UTCmonitoring

   We have taken steps to mitigate this issue and are seeing improved response times. We are continuing to monitor the situation.

3. 18. September 2025 um 17:28 UTCresolved

   This incident has been resolved.

1. 12. September 2025 um 12:41 UTCinvestigating

   We are currently investigating an issue with missing metrics and reporting in the Bigleaf Cloud Connect Dashboard.

2. 12. September 2025 um 13:59 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 12. September 2025 um 14:30 UTCresolved

   This incident has been resolved.

1. 11. September 2025 um 20:07 UTCinvestigating

   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.

2. 11. September 2025 um 20:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 11. September 2025 um 21:41 UTCresolved

   This incident has been resolved.

1. 22. August 2025 um 17:31 UTCinvestigating

   We are currently investigating slowness and intermittent responsiveness with our Bigleaf Cloud Connect Dashboard. Network connectivity is not affected.

2. 22. August 2025 um 17:43 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 22. August 2025 um 18:39 UTCresolved

   This incident has been resolved.

1. 8. August 2025 um 17:58 UTCinvestigating

   We are currently investigating this issue.

2. 8. August 2025 um 18:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 8. August 2025 um 18:34 UTCresolved

   This incident has been resolved.

1. 23. Juli 2025 um 15:14 UTCmonitoring

   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.

2. 23. Juli 2025 um 16:09 UTCresolved

   This incident has been resolved.

1. 7. Juli 2025 um 18:00 UTCinvestigating

   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.

2. 7. Juli 2025 um 18:17 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 7. Juli 2025 um 18:32 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 7. Juli 2025 um 19:15 UTCresolved

   This incident has been resolved.

1. 2. Juli 2025 um 22:19 UTCinvestigating

   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.

2. 2. Juli 2025 um 23:00 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2. Juli 2025 um 23:30 UTCresolved

   This incident has been resolved.

1. 20. Juni 2025 um 19:50 UTCinvestigating

   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.

2. 20. Juni 2025 um 20:12 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 20. Juni 2025 um 20:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 20. Juni 2025 um 22:24 UTCmonitoring

   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.

5. 24. Juni 2025 um 21:42 UTCresolved

   This incident has been resolved.