of monitored services depend on AWS for hosting, CDN or DNS. One AWS incident can reach all of them.
Who runs the internet?
We mapped the infrastructure behind — APIs, SaaS platforms, banks, shops and media sites, and probed them every five minutes. The internet looks decentralised from the outside. Underneath, a handful of companies carry most of it.
depend on Cloudflare, mostly as their edge network and DNS.
sit behind a CDN. Their real hosting is invisible from outside, and so is part of their risk.
run hosting, DNS and edge on one single vendor: no independent layer left.
01
The blast radius ranking
How many services would be touched if a provider failed, counting every layer we can see: hosting, CDN/edge and DNS.
02
Four layers, four oligopolies
Hosting
CDN / edge
DNS
Share of all mapped services. Hosting is only visible for services not hidden behind a CDN, so hosting shares are lower bounds.
03
Every sector has its single point of failure
| Sector | Services | Largest dependency | Share |
|---|
04
All eggs, one basket
— services (—) run their hosting, DNS and edge on the same provider. If that provider has a bad day, there is no independent layer left to route around it.
Examples
05
Money has the same shape
From official SEC filings: — disclosed customer-to-supplier revenue links across — companies. — of them earn more than half of their revenue from a single customer.
| Supplier | Single customer | Revenue share |
|---|
Customers with the most dependent suppliers
Method and limits
Measured reachability over the last 7 days: — across — probes; — provider incidents detected in 30 days.
Cite this report
ShadowGraph (2026). Who runs the internet? Hidden dependencies behind critical services. Data as of —. https://shadowgraph-live.floot.app/report
Download the data (JSON)See it live on the radar