Mastodawn

Cloudflare outage should not have happened

https://ebellani.github.io/blog/2025/cloudflare-outage-should-not-have-happened-and-they-seem-to-be-missing-the-point-on-how-to-avoid-it-in-the-future/

#HackerNews #CloudflareOutage #CloudflareFail #TechNews #InternetReliability #FutureSolutions

Cloudflare's outage should not have happened, and they seem to be missing the point on how to avoid it in the future

Yet again, another global IT outage happened (dèjá vu strikes again in our industry). This time at cloudflare(Prince 2025). Again, taking down large swaths of the internet with it(Booth 2025). And yes, like my previous analysis of the GCP and CrowdStrike’s outages, this post critiques Cloudflare’s root cause analysis (RCA), which — despite providing a great overview of what happened — misses the real lesson. Here’s the key section of their RCA:

Show thread

Ohmbudsman Jul 17, 2025

1️⃣ Cloudflare’s 1.1.1.1 DNS went dark for 66 min—someone fat-fingered a config, not an attack. Root-cause postmortem: https://www.bleepingcomputer.com/news/security/cloudflare-says-1111-outage-not-caused-by-attack-or-bgp-hijack

#Cloudflare #DNS #InternetReliability

Cloudflare says 1.1.1.1 outage not caused by attack or BGP hijack

To quash speculation of a cyberattack or BGP hijack incident causing the recent 1.1.1.1 Resolver service outage, Cloudflare explains in a post mortem that the incident was caused by an internal misconfiguration.

BleepingComputer

Hacker News Apr 17, 2025

Zoom Outage Caused by Accidental 'Shutting Down' of the Zoom.us Domain

https://status.zoom.us/incidents/pw9r9vnq5rvk

#HackerNews #Zoom #Outage #DomainIssue #TechNews #InternetReliability #ZoomStatus