<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel>
<title>System Design Road: engineering blogs</title>
<link>https://systemdesignroad.in/blogs/</link>
<description>Real outages and engineering stories retold in plain words: what broke, why, and what the engineers learned.</description>
<language>en</language>
<atom:link href="https://systemdesignroad.in/blogs/feed.xml" rel="self" type="application/rss+xml"/>
<item><title>An empty query parameter withdrew a quarter of Cloudflare's customer IP ranges</title><link>https://systemdesignroad.in/blogs/cloudflare-byoip-2026/</link><guid>https://systemdesignroad.in/blogs/cloudflare-byoip-2026/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A new clean-up task asked for &quot;prefixes pending delete&quot; but sent the flag with no value. The API read that as &quot;all prefixes&quot;, and the task began removing customers' addresses from the internet.</description></item>
<item><title>Clerk's sign-ins failed because Postgres guessed wrong about one column</title><link>https://systemdesignroad.in/blogs/clerk-query-plan-flip/</link><guid>https://systemdesignroad.in/blogs/clerk-query-plan-flip/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A routine automatic statistics refresh sampled a column that was almost always empty, concluded it was always empty, and changed how a hot query ran. Over 95% of sign-in traffic was rejected.</description></item>
<item><title>The race condition that emptied DynamoDB's address, and half the internet with it</title><link>https://systemdesignroad.in/blogs/aws-dynamodb-dns-2025/</link><guid>https://systemdesignroad.in/blogs/aws-dynamodb-dns-2025/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Two copies of DynamoDB's DNS automation raced each other. One applied an old plan, the other deleted it, and DynamoDB's address in us-east-1 pointed nowhere. Apps around the world went down, and EC2 took until the afternoon to recover.</description></item>
<item><title>CrowdStrike and the 21st field: the biggest IT outage in history</title><link>https://systemdesignroad.in/blogs/crowdstrike-2024/</link><guid>https://systemdesignroad.in/blogs/crowdstrike-2024/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A routine security content update told millions of Windows PCs to read a 21st field from a list that only had 20. The code ran inside the operating system's kernel, so every one of them crashed, again and again.</description></item>
<item><title>Roblox was down for 73 hours. Two hidden bugs, and blind monitoring.</title><link>https://systemdesignroad.in/blogs/roblox-73-hours/</link><guid>https://systemdesignroad.in/blogs/roblox-73-hours/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Millions of players locked out for three days. The cause sat deep inside Consul, the system everything else used to find each other, and the monitoring that should have pointed to it depended on the same system.</description></item>
<item><title>Slack's first workday of 2021, and the autoscaler that read the wrong signal</title><link>https://systemdesignroad.in/blogs/slack-january-4/</link><guid>https://systemdesignroad.in/blogs/slack-january-4/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Everyone came back from the holidays on the same morning. A network hub couldn't keep up, servers looked idle while they waited, and the autoscaler removed capacity at exactly the wrong moment.</description></item>
<item><title>Cloudflare, a half-broken switch, and a six-hour outage</title><link>https://systemdesignroad.in/blogs/cloudflare-half-broken-switch/</link><guid>https://systemdesignroad.in/blogs/cloudflare-half-broken-switch/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A network switch failed for six minutes, but only partly. The machines it connected disagreed about who could reach whom, a database failover kicked in, and a hidden bug turned six minutes into six and a half hours.</description></item>
<item><title>GitLab deleted its production database, and found its backups didn't work</title><link>https://systemdesignroad.in/blogs/gitlab-database-deletion/</link><guid>https://systemdesignroad.in/blogs/gitlab-database-deletion/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A tired engineer, a late night, and a command run on the wrong server. Then the real shock: of five ways to restore the data, almost none worked. GitLab livestreamed the recovery.</description></item>
</channel></rss>
