Historial de interrupciones de Lumaserv

1. 27 de septiembre de 2026 a las 23:59 UTCinvestigating

   Actualmente estamos experimentando problemas de red que afectan la accesibilidad de nuestra red ubicada en Frankfurt. Proporcionaremos actualizaciones sobre esta página tan pronto como sea posible.

2. 28 de septiembre de 2026 a las 0:23 UTCmonitoring

   Desde las 00:05 UTC, todos los servicios en nuestra ubicación de Frankfurt son totalmente accesibles de nuevo. La causa fue el fracaso de un motor de enrutamiento en uno de nuestros routers centrales. El motor redundante de enrutamiento se hizo cargo automáticamente. Durante el cambio, la capacidad de alcance de nuestra red de Frankfurt se vio afectada entre aprox. 23:52 y 00:05 UTC. La red se encuentra actualmente en funcionamiento estable en el motor de enrutamiento redundante. Estamos trabajando para restaurar el componente fallido y seguimos monitoreando la situación de cerca. Proporcionaremos otra actualización una vez que se haya restaurado la redundancia completa.

3. 28 de septiembre de 2026 a las 21:31 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 11 de agosto de 2026 a las 18:07 UTCinvestigating

   Our upstream provider at our Zurich cloud environment, has confirmed network issues. They are currently investigating and we will provide updates as soon as available here. Link to our upstream‘s status page: https://status.nine.ch/

2. 11 de agosto de 2026 a las 20:01 UTCresolved

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

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de julio de 2026 a las 9:20 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 22 de julio de 2026 a las 10:00 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 22 de julio de 2026 a las 17:15 UTCresolved

   El incidente se ha resuelto completamente.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de junio de 2026 a las 9:01 UTCresolved

   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.

1. 19 de junio de 2026 a las 9:46 UTCidentified

   We have identified packet loss to one of our upstream providers, routes have been switched. We will be monitoring the situation.

2. 19 de junio de 2026 a las 12:36 UTCresolved

   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.

1. 5 de mayo de 2026 a las 21:41 UTCidentified

   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

2. 6 de mayo de 2026 a las 7:35 UTCresolved

   This incident has been resolved.

1. 12 de marzo de 2026 a las 17:21 UTCinvestigating

   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.

2. 12 de marzo de 2026 a las 17:30 UTCresolved

   The issue has been identified and resolved.

1. 10 de marzo de 2026 a las 12:23 UTCinvestigating

   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.

2. 10 de marzo de 2026 a las 12:24 UTCinvestigating

   We are still investigating an issue with the VM's running the database.

3. 10 de marzo de 2026 a las 12:54 UTCresolved

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

1. 10 de marzo de 2026 a las 14:29 UTCresolved

   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.

1. 16 de febrero de 2026 a las 18:19 UTCinvestigating

   We are currently experiencing a network outage at our location in Frankfurt. We are currently investigating and provide updates on this page as soon as possible.

2. 16 de febrero de 2026 a las 18:30 UTCidentified

   The network is available again since 19:24 CET. We continue investigating and analyzing the route cause.

3. 17 de febrero de 2026 a las 9:15 UTCresolved

   The incident has been resolved and no further impact is expected. We will provide details today afternoon.

4. 17 de febrero de 2026 a las 17:48 UTCpostmortem

   On February 16, 2026, an incident identified as INC-262 occurred, resulting in a critical network outage that affected all systems in our Frankfurt data centers for a duration of 8 minutes. The incident was triggered by a routine configuration change made to a static route on one of our routers. Prior to implementation, the configuration underwent validation via the operating system \(Juniper Junos OS\), which generally checks for errors. However, due to a bug in the firmware, the system incorrectly accepted a faulty configuration change. 4 minutes after the change was applied, both forwarding engines were reported unreachable by the routing engine. The issue was promptly detected and reported by our monitoring systems. An automatic rollback occurred one minute following the failure due to a lack of manual confirmation, which restored both routing engines and forwarding engines. Safety mechanisms have worked as expected and resulted in a quick recovery completed by 7:27 PM. To preemptively harden our infrastructure against similar issues in the future, we already planned to transition from a redundant routing chassis to completely isolated devices, ensuring full redundancy even in case of such failures. This transition is scheduled for April/May during a planned maintenance. We appreciate your understanding and patience as we work to enhance our systems' reliability.

1. 11 de febrero de 2026 a las 13:51 UTCresolved

   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.

1. 23 de enero de 2026 a las 12:00 UTCresolved

   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.

1. 26 de noviembre de 2025 a las 11:09 UTCresolved

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

1. 11 de noviembre de 2025 a las 13:11 UTCresolved

   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.

1. 4 de octubre de 2025 a las 12:17 UTCinvestigating

   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

2. 5 de octubre de 2025 a las 22:16 UTCresolved

   This incident has been resolved.

1. 23 de julio de 2025 a las 14:13 UTCresolved

   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.

1. 14 de julio de 2025 a las 22:06 UTCinvestigating

   We are seeing issues regarding routes to Cloudflare, we're investigating and will update you as soon as we have further information.

2. 14 de julio de 2025 a las 22:11 UTCidentified

   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.

3. 14 de julio de 2025 a las 22:14 UTCidentified

   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

4. 15 de julio de 2025 a las 7:12 UTCidentified

   We continuing to monitor

5. 15 de julio de 2025 a las 7:13 UTCresolved

   The incident has been resolved by Cloudflare

1. 2 de abril de 2025 a las 13:11 UTCinvestigating

   We are currently experiencing network issues at our Frankfurt locations.

2. 2 de abril de 2025 a las 13:24 UTCmonitoring

   The network issue has been fixed and our network is stable again. We keep monitoring and will provide updates here.

3. 2 de abril de 2025 a las 21:27 UTCresolved

   This incident has been resolved.

4. 2 de abril de 2025 a las 21:27 UTCpostmortem

   At approximately 15:00 CET on April 2nd, 2025, we experienced a brief network disruption affecting our Frankfurt \(FRA\) infrastructure. The incident occurred during a scheduled maintenance window for one of our upstream providers. The network disruption lasted for approximately seven minutes, during which some of our services experienced reduced accessibility. Our network engineering team identified the issue immediately and implemented necessary measures to restore service stability. While we typically handle such maintenance windows without any customer impact, this particular incident resulted in a brief service interruption. We have conducted a thorough review of our maintenance procedures and will be implementing additional safeguards to prevent similar incidents in the future. We understand the impact this may have had on your operations and apologize for any inconvenience caused. Our team remains committed to providing reliable service and continuous improvement of our infrastructure management processes. If you have any questions or concerns, please don't hesitate to reach out to us.

1. 5 de diciembre de 2024 a las 13:54 UTCinvestigating

   We're currently experiencing a major outage on our compute infrastructure in our FRA-2 location. We're investigating the issue and will provide additional information soon

2. 5 de diciembre de 2024 a las 14:22 UTCidentified

   We've identified the issue and are working on recovering all services ASAP

3. 5 de diciembre de 2024 a las 14:27 UTCidentified

   We are currently booting all affected servers again. The services will be back online in the next minutes.

4. 5 de diciembre de 2024 a las 18:00 UTCmonitoring

   We brought all services back up and are closely monitoring them

5. 5 de diciembre de 2024 a las 22:14 UTCmonitoring

   All services are running as expected again. We will keep monitoring and let the incident open till we publish an official statement tomorrow.

6. 6 de diciembre de 2024 a las 9:40 UTCresolved

   All systems and services have been stable since the recovery and the normal operational state has been fully recovered. The root cause was a power outage in one of our locations. We don't have information about the exact cause yet but are in contact with the datacenter provider to get more information about the incident. To ensure that a similar incident can be preempted or mitigated, we will do an internal review and inform you about our steps as soon as this has been completed.

1. 31 de octubre de 2024 a las 9:50 UTCinvestigating

   One of our hypervisors became unavailable, we're currently investigating the issue

2. 31 de octubre de 2024 a las 10:31 UTCmonitoring

   The hypervisor has been taken out of service and all services have been distributed to different hypervisors. We're closely monitoring the situation and we'll post postmortem once we have all information on what happened.

3. 31 de octubre de 2024 a las 12:56 UTCresolved

   This incident has been resolved.