<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Post Mortem &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/post-mortem/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Tue, 14 Jul 2026 13:00:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>A broken DNSSEC rollover took down .AL. Now 1.1.1.1 tells you when validation is bypassed</title>
		<link>https://noise.getoto.net/2026/07/14/a-broken-dnssec-rollover-took-down-al-now-1-1-1-1-tells-you-when-validation-is-bypassed/</link>
		
		<dc:creator><![CDATA[Sebastiaan Neuteboom]]></dc:creator>
		<pubDate>Tue, 14 Jul 2026 13:00:00 +0000</pubDate>
				<category><![CDATA[1.1.1.1]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[DNSSEC]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[standards]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=2c557b12e7a2181813b16f91782a6892</guid>

					<description><![CDATA[When a failed DNSSEC key rollover took down the .AL TLD, we deployed a Negative Trust Anchor to restore resolution. This time, though, clients didn't have to take our word for it: 1.1.1.1 returned EDE 33, a new DNS error code that signals directly in the response that DNSSEC validation was bypassed.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Code Orange: Fail Small is complete. The result is a stronger Cloudflare network</title>
		<link>https://noise.getoto.net/2026/05/02/code-orange-fail-small-is-complete-the-result-is-a-stronger-cloudflare-network/</link>
		
		<dc:creator><![CDATA[Jeremy Hartman]]></dc:creator>
		<pubDate>Fri, 01 May 2026 21:07:30 +0000</pubDate>
				<category><![CDATA[Code Orange]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=89eda8aba74b40011eb8f09d0aaf1d21</guid>

					<description><![CDATA[We have completed a massive engineering effort to make our infrastructure more resilient. Through new tools like Snapstone and the Engineering Codex, we've implemented safer configuration changes and automated best practices to prevent future incidents.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare outage on February 20, 2026</title>
		<link>https://noise.getoto.net/2026/02/21/cloudflare-outage-on-february-20-2026/</link>
		
		<dc:creator><![CDATA[David Tuber]]></dc:creator>
		<pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate>
				<category><![CDATA[incident response]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=a0901fe339019d63338ef4835169dba1</guid>

					<description><![CDATA[Cloudflare suffered a service outage on February 20, 2026. A subset of customers who use Cloudflare’s Bring Your Own IP (BYOIP) service saw their routes to the Internet withdrawn via Border Gateway Protocol (BGP).]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Route leak incident on January 22, 2026</title>
		<link>https://noise.getoto.net/2026/01/23/route-leak-incident-on-january-22-2026/</link>
		
		<dc:creator><![CDATA[Bryton Herdes]]></dc:creator>
		<pubDate>Fri, 23 Jan 2026 14:00:00 +0000</pubDate>
				<category><![CDATA[bgp]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=57b390cb7138795f66918516b1edaf96</guid>

					<description><![CDATA[An automated routing policy configuration error caused us to leak some Border Gateway Protocol prefixes unintentionally from a router at our Miami data center. We discuss the impact and the changes we are implementing as a result.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>What came first: the CNAME or the A record?</title>
		<link>https://noise.getoto.net/2026/01/14/what-came-first-the-cname-or-the-a-record/</link>
		
		<dc:creator><![CDATA[Sebastiaan Neuteboom]]></dc:creator>
		<pubDate>Wed, 14 Jan 2026 00:00:00 +0000</pubDate>
				<category><![CDATA[1.1.1.1]]></category>
		<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Consumer Services]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[Resolver]]></category>
		<category><![CDATA[standards]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=74a67414f2d202bb3c7ce0d2932cfe89</guid>

					<description><![CDATA[A recent change to 1.1.1.1 accidentally altered the order of CNAME records in DNS responses, breaking resolution for some clients. This post explores the technical root cause, examines the source code of affected resolvers, and dives into the inherent ambiguities of the DNS RFCs.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Code Orange: Fail Small — Our resilience plan following recent incidents</title>
		<link>https://noise.getoto.net/2025/12/20/code-orange-fail-small-our-resilience-plan-following-recent-incidents/</link>
		
		<dc:creator><![CDATA[Dane Knecht]]></dc:creator>
		<pubDate>Fri, 19 Dec 2025 22:35:30 +0000</pubDate>
				<category><![CDATA[Code Orange]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=aea4bee9ab86273eccc63043f4ed9a6f</guid>

					<description><![CDATA[We have declared “Code Orange: Fail Small” to focus everyone at Cloudflare on a set of high-priority workstreams with one simple goal: ensure that the cause of our last two global outages never happens again.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare outage on December 5, 2025</title>
		<link>https://noise.getoto.net/2025/12/05/cloudflare-outage-on-december-5-2025/</link>
		
		<dc:creator><![CDATA[Dane Knecht]]></dc:creator>
		<pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=cec8f5b3b0cf27aa3be913f09714d661</guid>

					<description><![CDATA[Cloudflare experienced a significant traffic outage on  December 5, 2025, starting approximately at 8:47 UTC. The incident lasted approximately 25 minutes before resolution. We are sorry for the impact that it caused to our customers and the Internet. The incident was not caused by an attack and was due to configuration changes being applied to attempt to mitigate a recent industry-wide vulnerability impacting React Server Components.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare outage on November 18, 2025</title>
		<link>https://noise.getoto.net/2025/11/18/cloudflare-outage-on-november-18-2025/</link>
		
		<dc:creator><![CDATA[Matthew Prince]]></dc:creator>
		<pubDate>Tue, 18 Nov 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[Bot Management]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=af5b49bab23152054f98fa40eb9b962c</guid>

					<description><![CDATA[Cloudflare suffered a service outage on November 18, 2025. The outage was triggered by a bug in generation logic for a Bot Management feature file causing many Cloudflare services to be affected.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>A deep dive into Cloudflare’s September 12, 2025 dashboard and API outage</title>
		<link>https://noise.getoto.net/2025/09/13/a-deep-dive-into-cloudflares-september-12-2025-dashboard-and-api-outage/</link>
		
		<dc:creator><![CDATA[Tom Lianza]]></dc:creator>
		<pubDate>Sat, 13 Sep 2025 07:19:00 +0000</pubDate>
				<category><![CDATA[Без категория]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=05ba7dd0814fec04f566743f03c2d8e7</guid>

					<description><![CDATA[Cloudflare’s Dashboard and a set of related APIs were unavailable or partially available for an hour starting on Sep 12, 17:57 UTC.  The outage did not affect the serving of cached files via the]]></description>
		
		
		
			</item>
		<item>
		<title>The impact of the Salesloft Drift breach on Cloudflare and our customers</title>
		<link>https://noise.getoto.net/2025/09/02/the-impact-of-the-salesloft-drift-breach-on-cloudflare-and-our-customers/</link>
		
		<dc:creator><![CDATA[Sourov Zaman]]></dc:creator>
		<pubDate>Tue, 02 Sep 2025 17:10:00 +0000</pubDate>
				<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=2b7669a15da34006b8f2cc4da39b1bdb</guid>

					<description><![CDATA[An advanced threat actor, GRUB1, exploited the integration between Salesloft’s Drift chat agent and Salesforce to gain unauthorized access to Salesforce tenants of Cloudflare and many other companies.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare incident on August 21, 2025</title>
		<link>https://noise.getoto.net/2025/08/22/cloudflare-incident-on-august-21-2025/</link>
		
		<dc:creator><![CDATA[David Tuber]]></dc:creator>
		<pubDate>Fri, 22 Aug 2025 00:58:00 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=00aa656a3bf816f861b50dae76434245</guid>

					<description><![CDATA[On August 21, 2025, an influx of traffic directed toward clients hosted in AWS us-east-1 caused severe congestion on links between Cloudflare and us-east-1. In this post, we explain the details.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Redesigning Workers KV for increased availability and faster performance</title>
		<link>https://noise.getoto.net/2025/08/08/redesigning-workers-kv-for-increased-availability-and-faster-performance/</link>
		
		<dc:creator><![CDATA[Alex Robinson]]></dc:creator>
		<pubDate>Fri, 08 Aug 2025 13:00:00 +0000</pubDate>
				<category><![CDATA[Cloudflare Workers KV]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=b13759eeb06afd2b2afc6097398bb19d</guid>

					<description><![CDATA[Workers KV is Cloudflare's global key-value store. After the incident on June 12, we re-architected KV’s redundant storage backend, remove single points of failure, and make substantial improvements.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare service outage June 12, 2025</title>
		<link>https://noise.getoto.net/2025/06/13/cloudflare-service-outage-june-12-2025/</link>
		
		<dc:creator><![CDATA[Jeremy Hartman]]></dc:creator>
		<pubDate>Thu, 12 Jun 2025 22:00:00 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=4032704136eb202ab8367f3f4fa4fc03</guid>

					<description><![CDATA[Multiple Cloudflare services, including Workers KV, Access, WARP and the Cloudflare dashboard, experienced an outage for up to 2 hours and 28 minutes on June 12, 2025.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare incident on March 21, 2025</title>
		<link>https://noise.getoto.net/2025/03/25/cloudflare-incident-on-march-21-2025/</link>
		
		<dc:creator><![CDATA[Phillip Jones]]></dc:creator>
		<pubDate>Tue, 25 Mar 2025 01:40:38 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[R2 Storage]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=1c9fddea539b299f6dbcba2afd2e2b73</guid>

					<description><![CDATA[On March 21, 2025, multiple Cloudflare services, including R2 object storage experienced an elevated rate of error responses. Here’s what caused the incident, the impact, and how we are making sure it]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare Incident on February 6, 2025</title>
		<link>https://noise.getoto.net/2025/02/07/cloudflare-incident-on-february-6-2025/</link>
		
		<dc:creator><![CDATA[Matt Silverlock]]></dc:creator>
		<pubDate>Fri, 07 Feb 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[R2 Storage]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=500e398136ff5d2bdd4c7c5430254bc7</guid>

					<description><![CDATA[On Thursday February 6th, we experienced an outage with our object storage service (R2) and products that rely on it. Here's what happened and what we're doing to fix this going forward.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare incident on June 20, 2024</title>
		<link>https://noise.getoto.net/2024/06/26/cloudflare-incident-on-june-20-2024/</link>
		
		<dc:creator><![CDATA[Lloyd Wallis]]></dc:creator>
		<pubDate>Wed, 26 Jun 2024 13:00:22 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=26e9fd257c5adf0d52026c12b01b2082</guid>

					<description><![CDATA[A new DDoS rule resulted in an increase in error responses and latency for Cloudflare customers. Here’s how it went wrong, and what we’ve learned]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Major data center power failure (again): Cloudflare Code Orange tested</title>
		<link>https://noise.getoto.net/2024/04/08/major-data-center-power-failure-again-cloudflare-code-orange-tested/</link>
		
		<dc:creator><![CDATA[Matthew Prince]]></dc:creator>
		<pubDate>Mon, 08 Apr 2024 13:00:15 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=21f49ceb81a3498fb1174874c360aa1c</guid>

					<description><![CDATA[Just four months after a complete power outage at a critical data center we were hit with the exact same scenario.  Here’s how we did this time, and what’s next]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>1.1.1.1 lookup failures on  October 4th, 2023</title>
		<link>https://noise.getoto.net/2023/10/04/1-1-1-1-lookup-failures-on-october-4th-2023/</link>
		
		<dc:creator><![CDATA[Ólafur Guðmundsson]]></dc:creator>
		<pubDate>Wed, 04 Oct 2023 19:40:34 +0000</pubDate>
				<category><![CDATA[1.1.1.1]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=e7f72a1641ec2eb08973ecffcf6a21ea</guid>

					<description><![CDATA[On 4 October 2023, Cloudflare experienced DNS resolution problems. Some users may have received SERVFAIL DNS responses to valid queries. In this blog, we’re going to talk about what the failure was, why it occurred, and what we’re doing to make sure this doesn’t happen again]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2023/10/DNS-Incident.png" length="0" type="" />

			</item>
		<item>
		<title>Hardening Workers KV</title>
		<link>https://noise.getoto.net/2023/08/02/hardening-workers-kv/</link>
		
		<dc:creator><![CDATA[Matt Silverlock]]></dc:creator>
		<pubDate>Wed, 02 Aug 2023 13:05:42 +0000</pubDate>
				<category><![CDATA[Cloudflare Workers]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[Workers KV]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=2802945857536dbae9c25f5eaa3a9e08</guid>

					<description><![CDATA[A deep dive into the recent incidents relating to Workers KV, and how we’re going to fix them]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2023/08/Fixing-Workers-KV-Reliability.png" length="0" type="" />

			</item>
		<item>
		<title>Connection errors in Asia Pacific region on July 9, 2023</title>
		<link>https://noise.getoto.net/2023/07/11/connection-errors-in-asia-pacific-region-on-july-9-2023/</link>
		
		<dc:creator><![CDATA[Christian Elmerot]]></dc:creator>
		<pubDate>Tue, 11 Jul 2023 08:48:13 +0000</pubDate>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[DNSSEC]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=606cb966052e3bcfcea0bc7e8b241937</guid>

					<description><![CDATA[On July 9, 2023, users in the Asia Pacific region experienced connection errors due to origin DNS resolution failures to .com and .net TLD nameservers]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2023/07/image2-4.png" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 20/199 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2026-10-24 13:59:38 by W3 Total Cache
-->