<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Outage on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/outage/</link><description>Recent content in Outage on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/outage/index.xml" rel="self" type="application/rss+xml"/><item><title>DENIC .de TLD DNSSEC Outage</title><link>https://ai-blog.noorshomelab.dev/postmortems/denic-de-tld-dnssec-outage-may-2026/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/postmortems/denic-de-tld-dnssec-outage-may-2026/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Incident:&lt;/strong&gt; DENIC .de TLD DNSSEC Outage
&lt;strong&gt;Date:&lt;/strong&gt; 2026-05-05 | &lt;strong&gt;Duration:&lt;/strong&gt; ~None hours | &lt;strong&gt;Severity:&lt;/strong&gt; P0-critical
&lt;strong&gt;Affected:&lt;/strong&gt; Millions of domains unreachable | &lt;strong&gt;Systems:&lt;/strong&gt; .de TLD DNSSEC validation, DNS resolvers globally
&lt;strong&gt;Root cause (summary):&lt;/strong&gt; DENIC, the registry operator for the .de TLD, published incorrect DNSSEC signatures for the .de zone.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="incident-summary"&gt;Incident Summary&lt;/h3&gt;
&lt;p&gt;On May 5, 2026, the internet experienced a significant disruption affecting millions of domains under the &lt;code&gt;.de&lt;/code&gt; country-code top-level domain (ccTLD). This outage was triggered when DENIC, the authoritative registry operator for the &lt;code&gt;.de&lt;/code&gt; TLD, began publishing incorrect DNSSEC signatures for its zone.&lt;/p&gt;</description></item><item><title>QUIC Congestion Window Stalling Due to Linux Kernel Idle Optimization Misport: Engineering Postmortem</title><link>https://ai-blog.noorshomelab.dev/postmortems/quic-congestion-window-stalling-linux-kernel-idle-optimization-misport/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/postmortems/quic-congestion-window-stalling-linux-kernel-idle-optimization-misport/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Incident:&lt;/strong&gt; QUIC Congestion Window Stalling Due to Linux Kernel Idle Optimization Misport
&lt;strong&gt;Date:&lt;/strong&gt; 2023-08-15 (Discovered) | &lt;strong&gt;Duration:&lt;/strong&gt; Latent for years, ~6 hours (diagnosis &amp;amp; fix deployment) | &lt;strong&gt;Severity:&lt;/strong&gt; P1-high
&lt;strong&gt;Affected:&lt;/strong&gt; All Cloudflare QUIC connections utilizing the &lt;code&gt;quiche&lt;/code&gt; library, impacting global user experience, especially after packet loss.
&lt;strong&gt;Systems:&lt;/strong&gt; Cloudflare &lt;code&gt;quiche&lt;/code&gt; QUIC implementation, Linux kernel CUBIC porting layer, QUIC-enabled services.
&lt;strong&gt;Root cause (summary):&lt;/strong&gt; Incorrect calculation of &amp;ldquo;idle&amp;rdquo; periods in &lt;code&gt;quiche&lt;/code&gt;&amp;rsquo;s CUBIC congestion control port, preventing congestion window recovery after packet loss by perpetually resetting the idle timer.&lt;/p&gt;</description></item></channel></rss>