Infrastructure chokepoints keep surprising people
Docker pull failed in Spain because Cloudflare IPs get swept up in blocks aimed at illegal football streams. Commenters said the blocks hit the whole of Cloudflare R2 whenever a La Liga match starts. In the AWS billing thread, users got alerts for hundreds of millions to billions of dollars on hobby accounts, from an estimated billing data bug listed at $1.7 billion. The DeepSeek fetch thread raised the same worry on the buyer side: what happens when a page sits behind Cloudflare or Anubis?
The pattern: a handful of providers sit in the path of everything, and failures or policy decisions reach you with no warning. A football match in Spain broke a container pipeline. A billing glitch gave strangers a scare.
Commenters offered the usual advice, VPNs or alternate DNS, and some wanted a Cloudflare-run registry as a product. That says a lot about how much trust is being concentrated.
So what?
Audit your build and deploy path for hidden single dependencies like registries, CDNs and billing alerts. Add a mirror or fallback where a regional block could stop shipping, and set hard budget caps rather than trusting alerts.