<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on The Coders Blog</title><link>https://thecodersblog.com/categories/infrastructure/</link><description>Recent content in Infrastructure on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:22:12 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/categories/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>When DNSSEC Goes Wrong: Responding to the .de TLD Outage</title><link>https://thecodersblog.com/dnssec-incident-response-for-de-tld-2026/</link><pubDate>Wed, 06 May 2026 22:22:12 +0000</pubDate><guid>https://thecodersblog.com/dnssec-incident-response-for-de-tld-2026/</guid><description>&lt;p&gt;Millions of .de domains vanished from the internet on May 5, 2026, not due to a sophisticated attack, but a seemingly routine DNSSEC key rotation gone awry. DENIC, the registry for Germany&amp;rsquo;s country-code top-level domain, inadvertently published incorrect DNSSEC signatures, triggering widespread SERVFAIL errors on validating resolvers worldwide. For users of services like Cloudflare&amp;rsquo;s 1.1.1.1, this meant the .de TLD effectively ceased to exist for several agonizing hours.&lt;/p&gt;
&lt;h3 id="the-core-problem-broken-signatures-broken-resolution"&gt;The Core Problem: Broken Signatures, Broken Resolution&lt;/h3&gt;
&lt;p&gt;The incident stemmed from a faulty Zone Signing Key (ZSK) rotation. During this process, DENIC’s system introduced malformed RRSIG records for the .de zone. Specifically, the ZSK tag 33834 was found on an NSEC3 record, a configuration that, when combined with other factors in the validation chain, broke the cryptographic trust model. When a validating resolver queried for a .de domain, it received these flawed signatures, leading it to conclude the DNS data was untrustworthy and respond with SERVFAIL. This &amp;ldquo;fail-closed&amp;rdquo; nature of DNSSEC, while intended to prevent spoofing, directly translated operational errors into complete service unavailability.&lt;/p&gt;</description></item><item><title>AI's Thirsty Truth: Why Its Water Footprint Isn't What You Think [2026]</title><link>https://thecodersblog.com/ai-s-environmental-footprint-debunking-water-use-myths-2026/</link><pubDate>Fri, 01 May 2026 21:27:09 +0000</pubDate><guid>https://thecodersblog.com/ai-s-environmental-footprint-debunking-water-use-myths-2026/</guid><description>&lt;p&gt;Forget the &amp;lsquo;gallons per ChatGPT query&amp;rsquo; headlines; that&amp;rsquo;s not where AI&amp;rsquo;s real water challenge lies. As senior engineers, we need to talk about the system, the infrastructure, and the optimizations that truly define AI&amp;rsquo;s water footprint by &lt;strong&gt;2026&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="the-core-misconception-why-gallons-per-query-is-a-distraction"&gt;The Core Misconception: Why &amp;lsquo;Gallons Per Query&amp;rsquo; is a Distraction&lt;/h2&gt;
&lt;p&gt;The media loves a catchy, easily digestible metric. &amp;ldquo;X gallons per ChatGPT query&amp;rdquo; is precisely that – and it&amp;rsquo;s fundamentally misleading. This pervasive, oversimplified narrative fails to capture the true water demands of modern AI. It’s akin to measuring the fuel efficiency of a car by the amount of gasoline used for a single brake press.&lt;/p&gt;</description></item><item><title>Ubuntu Infrastructure Down: A Critical Cross-Border Cyberattack Exposes Core Weaknesses</title><link>https://thecodersblog.com/ubuntu-infrastructure-under-attack-a-wake-up-call-for-server-security-2026/</link><pubDate>Fri, 01 May 2026 21:17:20 +0000</pubDate><guid>https://thecodersblog.com/ubuntu-infrastructure-under-attack-a-wake-up-call-for-server-security-2026/</guid><description>&lt;p&gt;On &lt;strong&gt;May 1st, 2026&lt;/strong&gt;, the digital heartbeat of Ubuntu.com, the Snap Store, and Launchpad faltered under a declared cyberattack, plunging essential services into darkness. This wasn&amp;rsquo;t merely a fleeting outage; it was a sustained, cross-border assault that brought into sharp relief the vulnerabilities inherent even in the foundational components of our digital world.&lt;/p&gt;
&lt;p&gt;Canonical&amp;rsquo;s web infrastructure, including critical services like &lt;code&gt;login.ubuntu.com&lt;/code&gt; and essential Ubuntu Security APIs for CVEs and notices, became largely unresponsive. While mirror sites and the main Ubuntu archive largely continued to serve &lt;code&gt;apt update&lt;/code&gt; requests, the impact on developer workflows and trust was immediate and severe. This incident should serve as a &lt;strong&gt;critical wake-up call&lt;/strong&gt; for every organization relying on open-source ecosystems.&lt;/p&gt;</description></item><item><title>[Security Breakdown]: Ubuntu's 15+ Hour DDoS - Lessons for Every Developer [2026]</title><link>https://thecodersblog.com/ubuntu-s-extended-ddos-outage-2026/</link><pubDate>Fri, 01 May 2026 11:21:29 +0000</pubDate><guid>https://thecodersblog.com/ubuntu-s-extended-ddos-outage-2026/</guid><description>&lt;p&gt;April 30, 2026: 6 PM UK time. Ubuntu&amp;rsquo;s core services, the very bedrock for millions of developers, started crumbling under a sustained DDoS assault. This wasn&amp;rsquo;t just a hiccup; it was a &lt;strong&gt;15+ hour security breakdown&lt;/strong&gt;, a stark reminder that even the giants can be brought to their knees. This incident isn&amp;rsquo;t merely a cautionary tale for Canonical; it&amp;rsquo;s a blueprint for understanding and hardening your own defenses against the inevitable.&lt;/p&gt;</description></item><item><title>Cloudflare Outage Disrupts X, ChatGPT, Downdetector: What Happened and Resilience Lessons</title><link>https://thecodersblog.com/cloudflare-outage-disrupts-x-chatgpt-downdetector-what-happened-and-resilience-lessons/</link><pubDate>Tue, 18 Nov 2025 00:00:00 +0000</pubDate><guid>https://thecodersblog.com/cloudflare-outage-disrupts-x-chatgpt-downdetector-what-happened-and-resilience-lessons/</guid><description>&lt;p&gt;&lt;em&gt;Disclaimer: This post summarizes publicly available status-page and press report information as of publication. Root cause analysis (RCA) has not yet been published at the time of writing; therefore speculative explanations are avoided.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="1-human-context--why-this-felt-big"&gt;1. Human Context – Why This Felt Big&lt;/h2&gt;
&lt;p&gt;Early on November 18, 2025 (UTC morning, mid‑morning ET) users attempting to reach high‑traffic destinations such as X (formerly Twitter) and ChatGPT encountered challenge failures and generic connectivity / 5xx style errors. Even downtime tracking platform Downdetector briefly showed disruption, creating a recursive reliability moment: when the monitoring site is also impaired, user anxiety escalates.&lt;/p&gt;</description></item></channel></rss>