<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Incident - Tag - arleo.eu</title><link>https://www.arleo.eu/en/tags/incident/</link><description>Incident - Tag - arleo.eu</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 08 Apr 2026 00:35:00 +0200</lastBuildDate><atom:link href="https://www.arleo.eu/en/tags/incident/" rel="self" type="application/rss+xml"/><item><title>Post-Mortem — Incident 522 / WAN Failover (April 8, 2026)</title><link>https://www.arleo.eu/en/posts/post-mortem-522-wan-failover/</link><pubDate>Wed, 08 Apr 2026 00:35:00 +0200</pubDate><author>Jmr</author><guid>https://www.arleo.eu/en/posts/post-mortem-522-wan-failover/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/post-mortem-522-wan-failover-featured.jpg" referrerpolicy="no-referrer">
            </div><h2 id="-in-short">⚡ In short</h2>
<p><strong>Date:</strong> April 7-8, 2026 — <strong>Duration:</strong> ~3h (21:28 UTC → 22:31 UTC) — <strong>Severity:</strong> P1</p>
<p>arleo.eu was unreachable for 3 hours. The root cause was not the server, not nginx, not CrowdSec — it was an HTTPS port forwarding rule attached to generic <code>WAN</code> instead of explicit <code>WAN1</code> on the Netgear PR60X. The daily DHCP lease renewal of the 4G modem (WAN2) triggered a NAT rebalance that broke routing to port 443.</p>]]></description></item></channel></rss>