<?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>Fri, 05 Dec 2025 00:00:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<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>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>
		<item>
		<title>Cloudflare Incident on January 24th, 2023</title>
		<link>https://noise.getoto.net/2023/01/25/cloudflare-incident-on-january-24th-2023/</link>
		
		<dc:creator><![CDATA[Kenny Johnson]]></dc:creator>
		<pubDate>Wed, 25 Jan 2023 03:47:09 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=e6bfab595b02abbe4720dec072a27250</guid>

					<description><![CDATA[Several Cloudflare services became unavailable for 121 minutes on January 24th, 2023 due to an error releasing code that manages service tokens. The incident degraded a wide range of Cloudflare products]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2023/01/Disruption-1.png" length="0" type="" />

			</item>
		<item>
		<title>Partial Cloudflare outage on October 25, 2022</title>
		<link>https://noise.getoto.net/2022/10/26/partial-cloudflare-outage-on-october-25-2022/</link>
		
		<dc:creator><![CDATA[John Graham-Cumming]]></dc:creator>
		<pubDate>Wed, 26 Oct 2022 03:02:50 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=ad2557c3d5f5befda5d213d55b5895cc</guid>

					<description><![CDATA[Today, a change to our Tiered Cache system caused some requests to fail for users with status code 530]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2022/10/image1-23.png" length="0" type="" />

			</item>
		<item>
		<title>The mechanics of a sophisticated phishing scam and how we stopped it</title>
		<link>https://noise.getoto.net/2022/08/09/the-mechanics-of-a-sophisticated-phishing-scam-and-how-we-stopped-it/</link>
		
		<dc:creator><![CDATA[Matthew Prince]]></dc:creator>
		<pubDate>Tue, 09 Aug 2022 15:56:30 +0000</pubDate>
				<category><![CDATA[Phishing]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=265f48a972db4ec13156fe3eab61166b</guid>

					<description><![CDATA[Yesterday, August 8, 2022, Twilio shared that they’d been compromised by a targeted phishing attack. Around the same time as Twilio was attacked, we saw an attack with very similar characteristics also targeting Cloudflare’s employees]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2022/08/unnamed.png" length="0" type="" />

			</item>
		<item>
		<title>Cloudflare outage on June 21, 2022</title>
		<link>https://noise.getoto.net/2022/06/21/cloudflare-outage-on-june-21-2022/</link>
		
		<dc:creator><![CDATA[Tom Strickx]]></dc:creator>
		<pubDate>Tue, 21 Jun 2022 12:38:05 +0000</pubDate>
				<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=6d569019301d52cd1a07b1aed3b1d070</guid>

					<description><![CDATA[Today, June 21, 2022, Cloudflare suffered an outage that affected traffic in 19 of our data centers]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2022/06/BLOG-1226-Global-Latency.png" length="0" type="" />

			</item>
		<item>
		<title>PIPEFAIL: How a missing shell option slowed Cloudflare down</title>
		<link>https://noise.getoto.net/2022/04/05/pipefail-how-a-missing-shell-option-slowed-cloudflare-down/</link>
		
		<dc:creator><![CDATA[Alex Forster]]></dc:creator>
		<pubDate>Tue, 05 Apr 2022 12:57:28 +0000</pubDate>
				<category><![CDATA[deep dive]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=a7bdddb473c45f4087a6eb5c8d7b4fae</guid>

					<description><![CDATA[This post tells the story of how a missing shell option called “pipefail” slowed Cloudflare down.]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2022/04/image4-3.png" length="0" type="" />

			</item>
		<item>
		<title>Incorrect proxying of 24 hostnames on January 24, 2022</title>
		<link>https://noise.getoto.net/2022/01/26/incorrect-proxying-of-24-hostnames-on-january-24-2022/</link>
		
		<dc:creator><![CDATA[Jeremy Hartman]]></dc:creator>
		<pubDate>Wed, 26 Jan 2022 18:34:08 +0000</pubDate>
				<category><![CDATA[Post Mortem]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=fd0114f6cad509c206cdcad597aa4586</guid>

					<description><![CDATA[On January 24, 2022, as a result of an internal product migration, 24 hostnames (including www.cloudflare.com) that were actively proxied through the Cloudflare global network were mistakenly redirected to the wrong origin]]></description>
		
		
		<enclosure url="http://blog.cloudflare.com/content/images/2022/01/blog-header-939.png" length="0" type="" />

			</item>
		<item>
		<title>A Byzantine failure in the real world</title>
		<link>https://noise.getoto.net/2020/11/27/a-byzantine-failure-in-the-real-world/</link>
		
		<dc:creator><![CDATA[Tom Lianza]]></dc:creator>
		<pubDate>Fri, 27 Nov 2020 12:00:00 +0000</pubDate>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Post Mortem]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[апи]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=4b6641985b82cc533130eb07ed107cd8</guid>

					<description><![CDATA[When we review design documents at Cloudflare, we are always on the lookout for Single Points of Failure (SPOFs). In this post, we present a timeline of a real-world incident, and how an interesting failure mode known as a Byzantine fault played a role in a cascading series of events.]]></description>
		
		
		<enclosure url="https://blog.cloudflare.com/content/images/2020/11/image1-21.png" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 38/359 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-09 10:14:42 by W3 Total Cache
-->