Cloudflare and a few giants are the web's single point of failure
Docker pulls failed in Spain because Cloudflare R2 was caught up in a La Liga football block. Docker Hub was collateral damage, and commenters say everything proxied through Cloudflare goes dark when a match starts. Another thread has users of Pale Moon, SeaMonkey, w3m and even Chromium on Linux locked out by Cloudflare's 'verify you are human' checks. Commenters warned about the danger to the open web of so much traffic running through a handful of providers. A concern in the RPKI thread has the same shape: automated enforcement from one registry database in the Netherlands could become a point of legal pressure.
Beyond the network layer, the Chromium comparison between Google and Igalia, the Gentoo comment about giving up building Chromium from source, and Qualcomm's court win over Arm's license all show the same thing. Control sits in a few hands and shows up when something breaks or a deal is contested.
Another view: on the AWS billing bug that briefly showed bills in the billions, people took it as a prompt to finally lock down old accounts.
So what?
Your uptime depends on someone else's legal fight or policy fix. Plan for a regional block or a vendor outage with a second path for registries and artifacts, and know which of your dependencies share a single provider underneath.
Read these
Tell HN: Docker pull fails in Spain due to football Cloudflare block
Tell HN: Cloudflare is blocking Pale Moon and other non-mainstream browsers
RPKI now protects 70% of internet routes
Comparing Chromium Development at Google and Igalia
Qualcomm Legally Proves Arm Breached Its License, Wins $2
AWS: Inaccurate Estimated Billing Data – $1.7 billion