LUMASERV Outage History

This incident has been resolved.

We have been informed that the incident is resolved since 9.06pm.

The incident has been fully resolved.

During scheduled maintenance on our network infrastructure on Jun 23, 2026, one of our edge routers in Frankfurt (FRA) became temporarily unavailable by a software overload. This caused a network interruption of approximately one minute, until the second edge router fully took over the routing and connectivity was restored. Although the maintenance was announced, no service impact was expected. The disturbance was briefly wider than the announced scope, affecting connectivity for most of services in the Frankfurt location rather than only the one announced VLAN. We stopped the change immediately and have paused the remaining maintenance while we review the underlying causes, so the work can be completed reliably. We apologize for the any circumstances.

The issue was caused by unstable firmware on the core router of one of our upstream providers. The firmware has now been updated, and the routes have been returned to their previous state.

This incident has been resolved.

The issue has been identified and resolved.

The incident has been resolved and the environments are all available again. We will provide further information with our postmortem.

We encountered packet loss on virtual machines during a network reload in our virtualization environment when provisioning new SDN settings. The issue was resolved by March 8, 2026, 0:30. Moving forward, we will implement measures to ensure that network reloads do not cause packet loss. We will therefore announce the according maintenance frame here on the statuspage.

At 1:28PM the connection between our locations in Frankfurt and Zurich become degraded since one gateway at our upstreams becomes unavailable. The issue was resolved by 1:49PM completely by changing the gateway's configuration and adapting to the new configuration. Moving forward, we will check for possible improvements to enhance network resilience.

Starting this morning, we have detected packet loss occurring a few times for a few seconds at carrier level. Our analysis revealed that this is related to incoming or outgoing traffic via Liberty Global (AS6830). As a mitigation measure, we have deactivated this carrier and are using alternative routes. We will monitor the situation closely and wait for a response before reactivating the carrier.

One of our upstreams was experiencing network issues for about 5 minutes. Redundancy was working as expected and there was no noticeable impact.

A physical network connection inside our network in our FRA-2 location failed causing packet loss and a disturbance of multiple services. All our links are setup redundantly and the redundancy automatically took over within a few seconds.