LUMASERV had 12 outages in the last 2 years totaling 14h 57m of downtime — averaging 0.5 incidents per month.
There were 12 LUMASERV outages since July 14, 2025 totaling 14h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
The DENIC is currently experiencing a major issue causing all .de Domains to become unresolvable after dns caches run out. DENIC Statuspage: https://status.denic.de/pages/incident/592577eab611ce1e0d00046f/69fa60ef9d12f5057a974f38
This incident has been resolved.
During routine maintenance work, we encountered a service degration at our Zurich datacenter, which affects one hypervisor and the VM's running on it. We are currently investigating this issue and keep you updated here.
The issue has been identified and resolved.
At March 10, 2026, 11:13 AM, our monitoring alerted that the customer MySQL database was not available. The issue affects managed web hosting services which are operated within our Kubernetes clusters.
We are still investigating an issue with the VM's running the database.
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.
One of our uplink providers, IP-Projects (AS48314), is experiencing a network attack. This have lead to packet loss for max. five minutes, starting from 11.42. We have deactivated incoming and outgoing till the network is stable again there. Link to our uplink's status page entry: https://status.ip-projects.de/?page=Issue&id=551
This incident has been resolved.
From 22 July 2025 10pm to 23 July 2025 1.30pm, some customers using our DDoS Protected IP-Transit service experienced connectivity issues during active DDoS mitigation. This was due to an incorrect routing configuration by one of our upstream providers. The incident affected IP addresses with active DDoS mitigations during the mitigation period for the attack (typically 30 minutes). The majority of our services remained operational throughout this period. We resolved the issue by extending our routing policies and working with our provider to prevent this configuration problem from recurring. We apologize for any inconvenience this may have caused.
We are seeing issues regarding routes to Cloudflare, we're investigating and will update you as soon as we have further information.
We identified that Cloudflare DNS has major issues, causing some servers using Cloudflare DNS to have dns resolution issues. This is not an issue on our side but we'll keep monitoring it.
We identified that Cloudflare DNS has major issues, causing some servers using Cloudflare DNS to have dns resolution issues. This is not an issue on our side but we'll keep monitoring it. Cloudflare has posted the incident on their statuspage: https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f
We continuing to monitor
The incident has been resolved by Cloudflare