Skip to content

CONCEPT Cited by 1 source

CDN as critical Internet infrastructure

Edge CDN / proxy operators like Cloudflare, Fastly, CloudFront, and Akamai sit in front of a large fraction of the world's web traffic. When one of them has an outage, the non-technical blast radius is first-order: people cannot check email, log into banking, reach AI assistants, or load news sites. The incident makes the front page of every major newspaper.

Framing

From Cloudflare's 2025-11-18 post-mortem:

Given Cloudflare's importance in the Internet ecosystem any outage of any of our systems is unacceptable. That there was a period of time where our network was not able to route traffic is deeply painful to every member of our team. We know we let you down today.

The disclosure is unusual in two ways: (a) the severity framing is higher than a typical SaaS-vendor incident, and (b) the language is oriented toward the public Internet, not just Cloudflare customers.

Structural consequences

  • Post-mortem discipline is higher. CDN operators routinely publish same-day or next-day deep-dive RCAs naming the missing engineering discipline, not just the specific bug.
  • Scaled incidents are always public. There is no "we quietly rolled back" option; external observers notice within minutes and inspect for days.
  • The remediation backlog is public record. Follow-up incidents are evaluated against the remediation list from prior incidents. See e.g. sources/2025-12-05-cloudflare-outage-on-december-5-2025 explicitly naming 2025-11-18's remediations as still-incomplete.
  • Centralization risk is discussed openly. Every CDN outage re-opens the public conversation about Internet centralization.

Canonical instance

sources/2025-11-18-cloudflare-outage-on-november-18-2025 — ~3 hours of core-traffic impact on Cloudflare's network; front- page news; 1,465 HN points; "worst outage since 2019" framing.

Seen in

Last updated · 200 distilled / 1,178 read