From 71b3a421374b1bb011aba6e184563b46ee954eab Mon Sep 17 00:00:00 2001 From: counterweight Date: Tue, 17 Feb 2026 13:56:48 +0100 Subject: [PATCH] WAN incident --- 20260217_loss_of_wan_incident.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 20260217_loss_of_wan_incident.md diff --git a/20260217_loss_of_wan_incident.md b/20260217_loss_of_wan_incident.md new file mode 100644 index 0000000..9611a80 --- /dev/null +++ b/20260217_loss_of_wan_incident.md @@ -0,0 +1,14 @@ +# 2026-02-17 - Loss of WAN incident + +On 2026-02-16 around 14:00:00, connection to WAN went down at home. + +Router was running, devices could connect to the LAN, but no connection to WAN was available. Checking in the router admin panel confirmed this. + +Yoigo technician dropped by, validated that the optic fiber cable was not providing a signal in our flat. We went down to the parking hub and validated that someone had "stolen" our cable (O1.06). + +We replugged again and everything worked fine. + +Some learnings: +- The guy had this little device you can plug the optic fiber ending of our home into and it will tell you if there's any signal or not. +- He also used a funny looking lantern to send light through our ending, which allowed us to quickly validate what was our ending in the garage hub and plug back into it. +