Rome Sneezes, the Internet Catches a Cold: Of 373 Domains We Checked, 93% Run on One DNS Provider and 85% of Identified Edges Sit Behind Four Companies. Including Ours
If your organization went down this week and you are waiting to learn which vendor did it, here is the short version. The internet that looks like millions of independent companies stands on a few shared layers, and each layer is run by a handful of firms. When one of them pushes a bad change, everyone standing on it gets the same bad day. Rome sneezes, the world catches a cold.
Do three things this month. Write down which single company answers for each of your layers: DNS, edge, cloud, identity, certificates, updates. Add a second DNS provider if your name resolution rests on one. And stagger your own changes, because this week's outages show that the shared layer is often not a vendor at all. It is everybody patching the same thing on the same day.
We measured it instead of asserting it
We took the 411 hostnames, under 381 registrable domains, that we have audited for AI presence over the past year. That group leans toward enterprise, technology and AI companies, so read it as "companies that care about their web presence", not as a random sample of the web. For each one we looked up who answers its DNS and who serves its website, through public resolvers, on November 20, 2026.
DNS: who answers when someone looks your name up. 373 of the 381 domains resolved; 8 no longer exist.
92.8% use a single DNS provider. Only 27 domains, 7.2%, spread their name service across two companies.
Cloudflare answers for 23.3%, AWS Route 53 for 13.4% and Akamai for 8.3%. Three companies answer for 45% of the domains we checked.
49.3% rest on exactly one of five: Cloudflare, Route 53, Akamai, Azure DNS or Google.
Edge: who actually serves your website. We could identify the edge for 296 of the 411 hostnames, from the DNS chain or from the response headers.
84.5% sit behind one of four companies: Cloudflare, Akamai, Fastly or Amazon CloudFront.
Cloudflare alone fronts 31.4% of all 411 hostnames.
Stacked dependence. For 108 of the 411 hostnames, 26.3%, the same company runs both the DNS and the edge. For 66 of them, that company is Cloudflare.
Our own three domains are in that 66. Cloudflare answers our DNS, serves our edge, runs the Worker that blocks attackers at our front door, and resolves our own lookups through 1.1.1.1. Our compute runs on Microsoft Azure. If Cloudflare has a bad push, our site, our blocking and our public checks go down together. We chose that for good reasons, and we are writing it down here as an accepted risk, because a resilience lecture from someone who pretends to stand outside the problem is worth nothing.
Repeat it down the line
The same shape holds layer after layer. A few owners, everyone on top.
Naming, at the top: the entire DNS rests on 13 root server identities run by 12 organizations. Verisign runs two of them. This layer is the healthy exception: it is deliberately spread across independent operators and well over a thousand server instances worldwide.
Naming, at the bottom: the authoritative DNS for most companies we checked is one provider, and for 45% it is one of three.
Edge: four companies front 84.5% of the edges we could identify. W3Techs puts Cloudflare in front of about a quarter of all websites as of September 2026, roughly 85% of the sites whose reverse proxy it can identify, with the next largest, CloudFront, at 1.7% of all sites.
Cloud: Synergy Research's Q3 2026 figures, as reported by trade press, put Amazon at 26% of cloud infrastructure spending, Microsoft at 19% and Google at 16%. Three companies, about three fifths of the market.
And on up: identity (a few sign-in providers), certificates (a few authorities issue most of the web's), operating system updates (a few vendors push to billions of machines on the same schedule), endpoint security (a few agents run with full privileges on most corporate laptops), code and packages (a few registries every build pulls from). Each one is a single place where one change reaches everyone.
Running on networking designed in the sixties
Underneath all of it is plumbing older than most of the people running it. ARPANET carried its first message in October 1969. Vint Cerf and Bob Kahn described TCP/IP in 1974, and ARPANET switched to it on January 1, 1983. DNS was specified in 1983 and rewritten in 1987. BGP, the protocol networks use to tell each other where everything is, was first published in 1989, and it still works largely on trust: a network announces the addresses it can reach, and its neighbors mostly believe it.
That design was built to survive the loss of any one machine, and it still does. What it was never built for is a world where most of the traffic converges on a few companies by choice, because those companies are cheaper, faster and better than running it yourself. They usually are. Resilience left the protocol and moved into the business model.
What this week actually showed
This week brought a run of failures: Microsoft 365 on November 12, then JPMorgan Chase, Apple, Workday, the FAA and the NSA, whose classified network was down for three to four days. Officials say there is no sign the failures are linked or malicious, and on the evidence we have read, that looks right.
But look at the NSA case. Officials tied it to how the agency applied software updates for the PHP vulnerabilities. The shared layer that broke was not a CDN or a cloud. It was the patch itself, applied by everyone in the same window because everyone was told to hurry. Concentration is not only who you buy from. It is also everyone doing the same thing at the same time.
What to do
Map your single points. For each layer, write the one company that answers for it: DNS, edge, cloud region, identity, certificates, endpoint agent, update channel. If a row has one name and no fallback, that is a decision someone should make on purpose.
Put DNS on two providers. It is the cheapest redundancy on the list. Only 7.2% of the domains we checked had it.
Know what your edge does when it is gone. Can your origin serve directly, even badly, if your CDN is down? Can you change DNS if your DNS provider's dashboard is down?
Stagger changes. Patch fast, but not all at once: a canary ring first, then the rest. The outage you cause yourself by patching everything at 2 a.m. is still an outage.
Rehearse the bad day. Pick one layer a quarter and run without it for an hour on paper.
Am I affected?
Run two lookups for your own domain with any DNS tool: the NS record (who answers your DNS) and the CNAME chain for www (who serves your site). If both answers end in the same company, you are in the 26% of our sample that stacks both layers on one vendor. If the NS answers all belong to one company, you are in the 93%.
How we know
Population: the 411 hostnames (381 registrable domains) in our AI-presence audit index, plus our own three domains. It is a convenience sample that leans enterprise, tech and AI, not a random sample of the web.
DNS: NS records for each registrable domain, looked up through Cloudflare's 1.1.1.1 and Google's 8.8.8.8 on November 20, 2026, and classified by name server host. 373 resolved; 8 domains no longer exist. "Single provider" means every name server belongs to one company. 111 domains (29.8%) use providers outside our named list, such as registrars, regional hosts or their own servers, and are counted as "other".
Edge: the CNAME chain for each hostname and its www name, and where that was inconclusive, the headers of one HEAD request. 296 of 411 hostnames had an identifiable edge; the other 115 serve from their own origin or from an edge we could not identify.
Market shares are other people's numbers, cited with their dates: W3Techs for reverse proxy usage (September 2026; its pages from that period range from about 25% to 30% for Cloudflare across all websites) and Synergy Research for cloud spending (Q3 2026, as reported by DatacenterDynamics; we did not read Synergy's own release).
The outage facts come from CNN, NBC News and Al Jazeera reporting on November 20, 2026, and Tom's Guide on the November 12 Microsoft outage.
Sources
How do AI models see YOUR brand?
AIPM has audited 250+ domains. 15 seconds. Free while still in beta.



Comments