Some systems are experiencing issues.
This page announces planned maintenance work and unexpected disruptions within the nexserv (AS200482) network.
Last updated 2025-11-13 19:42:17
Connectivity within the fabric
Last updated 2025-11-20 12:42:29
Edge network that connects the location to the internet.
Last updated 2025-09-11 16:17:41
Connectivity to Upstream providers (also known as Transit providers, excl. direct peers) that serve direct internet access to the location.
A fix for LACP bundles has been deployed and we are monitoring the results.
We also observed that this change improved the internal connectivity within L2VPNs.
If there are still issues with LACP bundles, please contact us in order to investigate the issue throughouly.
Tonight at 19:30 CEST, we will deploy the planned fix for the ongoing LACP issues.
During this maintenance window, packet loss and brief port outages may occur as links are intentionally brought down and back up.
The rollout will happen in several controlled steps to keep the impact as low as possible. Once completed, all affected uplinks should operate under the updated configuration.
We will provide an update as soon as the maintenance is completed.
Thank you for your patience.
As the issue not only affects LACP bundles but also the internal connectivity within L2VPNs, we have extended the status report to include these too.
Fortunately, we may have identified a possible cause for the non-reachability between nodes in the same L2VPN and have applied a fix for it. We are monitoring the results for this specific case.
For the LACP issue, we are working on building a fix that can be rolled out with little to no impact.
Thank you for your understanding.
The fix is planned to be implemented within the week from 2025-11-24 till 2025-11-30.
After the migration of the old EGH location to CGN1, we observed that traffic is not properly routed towards the designated LACP links under certain circumstances. This may lead to packet loss, degraded speed performance, non-reachability, duplicate traffic, and unstable reachability of members within the same subnet when stretched across multiple leaves.
We have since determined that the issue not only affects LACP bundles but also internal connectivity within L2VPNs. These symptoms can include intermittent unreachability between nodes that are part of the same L2 segment.
Unfortunately, the underlying issue causing these behaviours is complex and cannot be fixed on the fly.
To ensure that customers can reliably reach their systems while we work on a solution, we have decided to shut down all LACP links except for the last remaining one.
In case of planned maintenance during this time on the network infrastructure, we will ensure that the shut down links will be activated beforehand.
Our team is already working on a solution and will provide it as soon as possible.
Thank you for your understanding.
The issue has been fixed and traffic levels have recovered.
After an administrative shutdown of an interface on one of the edge routers, every IP address got configured on every device, causing the traffic to be lost. We are still investigating the root cause for this behaviour and try to reproduce it in our lab.
The issue has been identified to one edge router. We have isolated the affected router and investigate why the traffic was still being forwarded towards the broken router.
We are investigating a routing outage in CGN1. Fabric traffic is not affected, but all connections towards the internet may show packet loss or is being dropped at onr of the edge routers.