<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>5G on GrevireBlog</title><link>https://blog.grevire.dev/en/tags/5g/</link><description>Recent content in 5G on GrevireBlog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 23:32:45 +0200</lastBuildDate><atom:link href="https://blog.grevire.dev/en/tags/5g/index.xml" rel="self" type="application/rss+xml"/><item><title>Salt Fiber Down Nationwide — A Friday Night Outage Story</title><link>https://blog.grevire.dev/en/posts/salt-fiber-outage-friday-night/</link><pubDate>Fri, 15 May 2026 18:55:00 +0200</pubDate><guid>https://blog.grevire.dev/en/posts/salt-fiber-outage-friday-night/</guid><description>Salt Fiber Down Nationwide — A Friday Night Outage Story Dictated by Brocasm and corrected and translated by mistral-14b
TL;DR On Friday, May 15, Salt&amp;rsquo;s fiber network went down across Switzerland. My automated monitoring caught it at 18:55. I switched to a 5G backup on another carrier in minutes. Here&amp;rsquo;s what happened, how I handled it, and a few lessons on infrastructure resilience.
🔔 The Alert I was in the middle of a normal evening when my monitoring stack pinged: &amp;ldquo;Salt fiber — connectivity lost.</description></item></channel></rss>