Service has been restored. At 09:02 UTC the session-handling process on de-fra2-lns2 stopped unexpectedly and restarted automatically within about a second. The affected DSL and FTTH lines reconnected via de-fra2-lns1, starting about 40 seconds later.
We haven't yet found why the process stopped. The system recorded no error, and we found no sign of overload, memory exhaustion or gradual degradation beforehand. de-fra2-lns1 was unaffected. We are adding diagnostics so that a repeat records exactly what triggers a stop, and we will keep the situation under observation.
Posted Sep 28, 2026 - 09:50 UTC
Update
Service has been restored. At 09:02 UTC the session-handling process on de-fra2-lns2 stopped unexpectedly and restarted automatically within about a second. The affected DSL and FTTH lines reconnected via de-fra2-lns1, starting about 40 seconds later.
We haven't yet found why the process stopped. The system recorded no error, and we found no sign of overload, memory exhaustion or gradual degradation beforehand. de-fra2-lns1 was unaffected. We are adding diagnostics so that a repeat records exactly what triggers a stop, and we will keep the situation under observation.
Posted Sep 28, 2026 - 09:50 UTC
Identified
It looks like the above mentioned LNS did crash and all sessions automatically failed over to de-fra2-lns1.level66.network causing a reconnect of all affected DSL and FTTH lines. We are currently checking the logs and are assessing the situation.
Posted Sep 28, 2026 - 09:15 UTC
This incident affected: Broadband - DSL / FTTH / IP-BSA.