Mar <var data-var='date'>23</var>, <var data-var='time'>16:34</var> CET Completed - The scheduled maintenance has been completed.Mar <var data-var='date'>23</var>, <var data-var='time'>16:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'>23</var>, <var data-var='time'>13:36</var> CET Scheduled - We’re commissioning a new upstream connection with ZET.NET and expanding our external connectivity by an additional 100 Gbit/s. This upgrade increases the overall redundancy and resilience of our network. No impact is expected during this change.

Maintenance - Commission of uplink ZET.NET

Mar <var data-var='date'>12</var>, <var data-var='time'>18:24</var> CET Resolved - The issue has been identified and resolved.Mar <var data-var='date'>12</var>, <var data-var='time'>18:21</var> CET Investigating - 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.

Service degration at ZRH1 (Zurich datacenter)

Mar <var data-var='date'>10</var>, <var data-var='time'>13:15</var> CET Resolved - The incident has been resolved and the environments are all available again. We will provide further information with our postmortem.Mar <var data-var='date'>10</var>, <var data-var='time'>11:43</var> CET Update - We are still investigating an issue with the VM's running the database.Mar <var data-var='date'>10</var>, <var data-var='time'>11:13</var> CET Investigating - 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.

MySQL database outage

Mar <var data-var='date'> 7</var>, <var data-var='time'>23:16</var> CET Resolved - 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.

Packet-loss during SDN configuration changes

Mar <var data-var='date'> 6</var>, <var data-var='time'>21:48</var> CET Completed - The maintenance has been successfully completed. As expected there was no impact.Mar <var data-var='date'> 6</var>, <var data-var='time'>17:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'> 6</var>, <var data-var='time'>15:41</var> CET Scheduled - During this maintenance period we plan to perform maintenance on the SSD and HDD CEPH storage and commission a new upstream connection to zet.net. We don't expect any downtime.

Maintenance on CEPH storage & commissioning of new upstream provider in our FRA-2 zone

Mar <var data-var='date'> 4</var>, <var data-var='time'>14:15</var> CET Completed - The scheduled maintenance has been completed.Mar <var data-var='date'> 4</var>, <var data-var='time'>14:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'> 4</var>, <var data-var='time'>09:39</var> CET Scheduled - The authentication service of the Cloud (login.lumaserv.cloud) will undergo maintenance. The Cloud API will be unavailable for a short amount of time during the restart of the service.

Maintenance on the authentication service of the Cloud API

Feb <var data-var='date'>16</var>, <var data-var='time'>20:30</var> CET Resolved - The incident has been resolved and no further impact is expected. We will provide details today afternoon.Feb <var data-var='date'>16</var>, <var data-var='time'>19:30</var> CET Identified - The network is available again since 19:24 CET. We continue investigating and analyzing the route cause.Feb <var data-var='date'>16</var>, <var data-var='time'>19:15</var> CET Investigating - 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.

Network outage

Feb <var data-var='date'>11</var>, <var data-var='time'>13:30</var> CET Resolved - 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.

Degraded connectivity between our locations at FRA and ZUR

Feb <var data-var='date'>11</var>, <var data-var='time'>06:00</var> CET Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>11</var>, <var data-var='time'>01:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 3</var>, <var data-var='time'>16:43</var> CET Scheduled - During 1am and 6am our upstream Liberty Global will do maintenance work at our cross connect to them at Digital Realty, Frankfurt. We will deactivate our imports and exports to them before start of the maintenance. We therefore do not expect any impact. Details to the progress will be provided on this page.

Cross Connect maintenance at Liberty Global

Jan <var data-var='date'>23</var>, <var data-var='time'>09:00</var> CET Resolved - 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.

Packet-loss on carrier-level

Jan <var data-var='date'> 5</var>, <var data-var='time'>23:10</var> CET Completed - The scheduled maintenance has been completed.Jan <var data-var='date'> 5</var>, <var data-var='time'>22:10</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'> 5</var>, <var data-var='time'>22:05</var> CET Scheduled - To increase the redundancy of our CEPH storage, we will be performing maintenance on the storage infrastructure between 10 p.m. and 1 a.m. This may result in slightly increased latency for disk operations. We do not anticipate any service restrictions.

CEPH maintenance

Nov <var data-var='date'>26</var>, <var data-var='time'>11:50</var> CET Resolved - One of our upstreams was experiencing network issues for about 5 minutes. Redundancy was working as expected and there was no noticeable impact.

Upstream BGP Session Restart (No Impact)

Nov <var data-var='date'>11</var>, <var data-var='time'>13:34</var> CET Resolved - 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.

Hardware network link failure in FRA-2

Oct <var data-var='date'>27</var>, <var data-var='time'>19:00</var> CET Completed - The scheduled maintenance has been completed.Oct <var data-var='date'>27</var>, <var data-var='time'>16:30</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Oct <var data-var='date'>23</var>, <var data-var='time'>18:55</var> CEST Scheduled - We will be upgrading the authentication service that serves authorization for the Cloud API. This means that the authentication service (https://login.lumaserv.cloud) as well as services relying on it (https://api.lumaserv.cloud, https://panel.lumaserv.cloud) will be temporarily unavailable.

Oct <var data-var='date'> 4</var>, <var data-var='time'>14:20</var> CEST Resolved - This incident has been resolved.Oct <var data-var='date'> 4</var>, <var data-var='time'>13:51</var> CEST Investigating - 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

Packet loss via routes of AS48314

Jul <var data-var='date'>23</var>, <var data-var='time'>09:00</var> CEST 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.

Network disturbance during active DDoS mitigation

Jul <var data-var='date'>15</var>, <var data-var='time'>01:20</var> CEST Resolved - The incident has been resolved by CloudflareJul <var data-var='date'>15</var>, <var data-var='time'>00:15</var> CEST Update - We continuing to monitorJul <var data-var='date'>15</var>, <var data-var='time'>00:14</var> CEST Update - 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/28r0vbbxsh8fJul <var data-var='date'>15</var>, <var data-var='time'>00:11</var> CEST Identified - 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.Jul <var data-var='date'>15</var>, <var data-var='time'>00:06</var> CEST Investigating - We are seeing issues regarding routes to Cloudflare, we're investigating and will update you as soon as we have further information.

DNS resolution issues caused by Cloudflare DNS unavailability

Apr <var data-var='date'> 2</var>, <var data-var='time'>23:27</var> CEST Resolved - This incident has been resolved.Apr <var data-var='date'> 2</var>, <var data-var='time'>15:24</var> CEST Monitoring - The network issue has been fixed and our network is stable again. We keep monitoring and will provide updates here.Apr <var data-var='date'> 2</var>, <var data-var='time'>15:00</var> CEST Investigating - We are currently experiencing network issues at our Frankfurt locations.

Network disturbance at FRA01

Dec <var data-var='date'> 6</var>, <var data-var='time'>10:40</var> CET Resolved - 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.Dec <var data-var='date'> 5</var>, <var data-var='time'>23:14</var> CET Update - All services are running as expected again. We will keep monitoring and let the incident open till we publish an official statement tomorrow.Dec <var data-var='date'> 5</var>, <var data-var='time'>19:00</var> CET Monitoring - We brought all services back up and are closely monitoring themDec <var data-var='date'> 5</var>, <var data-var='time'>15:27</var> CET Update - We are currently booting all affected servers again. The services will be back online in the next minutes.Dec <var data-var='date'> 5</var>, <var data-var='time'>15:22</var> CET Identified - We've identified the issue and are working on recovering all services ASAPDec <var data-var='date'> 5</var>, <var data-var='time'>14:54</var> CET Investigating - 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

Major outage of our compute infrastructure in FRA-2

Oct <var data-var='date'>31</var>, <var data-var='time'>13:56</var> CET Resolved - This incident has been resolved.Oct <var data-var='date'>31</var>, <var data-var='time'>11:31</var> CET Monitoring - 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.Oct <var data-var='date'>31</var>, <var data-var='time'>10:50</var> CET Investigating - One of our hypervisors became unavailable, we're currently investigating the issue

Single Hypervisor Outage

Sep <var data-var='date'>28</var>, <var data-var='time'>09:22</var> CEST Resolved - This incident has been resolved.Sep <var data-var='date'>28</var>, <var data-var='time'>08:32</var> CEST Monitoring - The issue has been mitigated, we continue to monitor and post an update once we have all information on what exactly happenedSep <var data-var='date'>28</var>, <var data-var='time'>08:01</var> CEST Investigating - We are currently investigating

Network outage in FRA

Sep <var data-var='date'>20</var>, <var data-var='time'>09:30</var> CEST Resolved - One of our uplink providers experienced a hardware failure resulting in an outage of that uplink. Our redundancy took over automatically but there was temporary packet loss noticeable during the switch-over phase.

Temporary packet loss due to outage of an uplink provider

Aug <var data-var='date'>25</var>, <var data-var='time'>22:14</var> CEST Completed - The scheduled maintenance has been completed.Aug <var data-var='date'>17</var>, <var data-var='time'>23:38</var> CEST Update - The maintenance has been completed since approximately 22:05. We have checked all VMs and servers for operational status. We are continuing to monitor our infrastructure.Aug <var data-var='date'>17</var>, <var data-var='time'>22:12</var> CEST Update - We are currently experiencing issues with the planned maintenance with two hypervisors. Our technicians currently looking into it and we will provide an update here shortly.Aug <var data-var='date'>17</var>, <var data-var='time'>22:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Aug <var data-var='date'>14</var>, <var data-var='time'>15:48</var> CEST Scheduled - Our data center provider MK Netzdienste has scheduled a power maintenance for this Saturday starting at 22:00. The maintenance is scheduled to last about five minutes. Due to our redundancy concept we don't expect any downtime in our infrastructure. The power maintenance will be covered by UPS and generator. If you have any questions, please feel free to contact us at support@lumaserv.com.

Power maintenance at MK Netzdienste

Jun <var data-var='date'>10</var>, <var data-var='time'>19:30</var> CEST Resolved - This incident has been resolved.Jun <var data-var='date'>10</var>, <var data-var='time'>18:47</var> CEST Investigating - Today at 18:47 CEST we had a hardware failure on our virtualization node ls-ds-46. After the problem could not be solved via IPMI, we migrated all VMs to other hosts and restarted them. By 19:24 at the latest, all VMs were completely restarted. The affected host was deactivated immediately and will be investigated and tested before being reactivated.

Hardware failure on virtualisation node ls-ds-46

Aug <var data-var='date'>31</var>, <var data-var='time'>22:00</var> CEST Resolved - This incident has been resolved.Jul <var data-var='date'>31</var>, <var data-var='time'>20:40</var> CEST Investigating - On 8.42pm CEST we've experienced a hardware failure on our cloud server hypervisor "ls-ds-32". We've taken this node out of service for now and rebooted all VM's on another hypervisor. At 9.06 p.m. at the latest, all VMs were online again.

Is LUMASERV down?

LUMASERV status is UP

Lastest published events

Maintenance - Commission of uplink ZET.NET

Service degration at ZRH1 (Zurich datacenter)

MySQL database outage

LUMASERV Services, Components and Regions

Recent LUMASERV events

Maintenance - Commission of uplink ZET.NET

Service degration at ZRH1 (Zurich datacenter)

MySQL database outage

Packet-loss during SDN configuration changes

Maintenance on CEPH storage & commissioning of new upstream provider in our FRA-2 zone

Maintenance on the authentication service of the Cloud API

Get your FREE account now,
5 monitors included!

Is LUMASERV down?

LUMASERV status is UP

Lastest published events

Maintenance - Commission of uplink ZET.NET

Service degration at ZRH1 (Zurich datacenter)

MySQL database outage

LUMASERV Services, Components and Regions

Recent LUMASERV events

Maintenance - Commission of uplink ZET.NET

Service degration at ZRH1 (Zurich datacenter)

MySQL database outage

Packet-loss during SDN configuration changes

Maintenance on CEPH storage & commissioning of new upstream provider in our FRA-2 zone

Maintenance on the authentication service of the Cloud API

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!