https://approjects-vendor-status-watch.static.hf.space/v/lumaserv.htmlIncidents from Lumaserv's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/0d7jhn6gfn3mlumaserv:2026-08-11T19:30:13.000+02:00Tue, 11 Aug 2026 17:30:13 +0000We have been informed that the incident is resolved since 9.06pm.https://stspg.io/ytngnzbffxx4lumaserv:2026-07-22T11:20:51.083+02:00Wed, 22 Jul 2026 09:20:51 +0000The incident has been fully resolved.https://stspg.io/k0rngj558q9slumaserv:2026-06-23T18:40:00.000+02:00Tue, 23 Jun 2026 16:40:00 +0000During 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.https://stspg.io/377qy4b23gqnlumaserv:2026-06-19T11:46:55.190+02:00Fri, 19 Jun 2026 09:46:55 +0000The 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.https://stspg.io/nm8cq1cqftj4lumaserv:2026-05-05T23:41:18.015+02:00Tue, 05 May 2026 21:41:18 +0000This incident has been resolved.https://stspg.io/f0j5jsvl12ymlumaserv:2026-03-12T18:21:36.533+01:00Thu, 12 Mar 2026 17:21:36 +0000The issue has been identified and resolved.https://stspg.io/pwnkk3qnftywlumaserv:2026-03-10T11:13:44.000+01:00Tue, 10 Mar 2026 10:13:44 +0000The incident has been resolved and the environments are all available again. We will provide further information with our postmortem.https://stspg.io/frvvdt6fz6qylumaserv:2026-03-07T23:00:00.000+01:00Sat, 07 Mar 2026 22:00:00 +0000We 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.https://stspg.io/12g4spm944n4lumaserv:2026-02-16T19:15:23.000+01:00Mon, 16 Feb 2026 18:15:23 +0000On 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 https://stspg.io/lgxmq2457jj2lumaserv:2026-02-11T13:30:00.000+01:00Wed, 11 Feb 2026 12:30:00 +0000At 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.https://stspg.io/q01hv1lycwnclumaserv:2026-01-23T09:00:00.000+01:00Fri, 23 Jan 2026 08:00:00 +0000Starting 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.https://stspg.io/qm83wwvytmt3lumaserv:2025-11-26T10:50:00.000+01:00Wed, 26 Nov 2025 09:50:00 +0000One of our upstreams was experiencing network issues for about 5 minutes. Redundancy was working as expected and there was no noticeable impact.https://stspg.io/vdtyk3zgpgk5lumaserv:2025-11-11T12:34:00.000+01:00Tue, 11 Nov 2025 11:34:00 +0000A 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.https://stspg.io/gkbrcmnxs47nlumaserv:2025-10-04T13:51:31.000+02:00Sat, 04 Oct 2025 11:51:31 +0000This incident has been resolved.