The gap is not coverage — it is depth
Most datacenter directories give you a map and a phone number. That is genuinely useful for discovery, but it stops exactly where a network buyer's real questions begin: How many carriers are present? Is an internet exchange on-net? Who actually operates this building — and do they own it, or are they reselling someone else's space?
None of that is on the front of a listing, because it is hard to assemble. It takes cross-referencing network registration data, autonomous-system and announced-prefix records, internet-exchange and peering presence, and operator-domain matching — then keeping it current. That is the work we did, and the reason a connectivity layer exists here that a plain directory cannot show.
Connectivity concentrates in a handful of metros
Of 7,847 facilities, only 889 reach the highest connectivity band. They cluster: a small set of metros carry a disproportionate share of interconnection, because each network that joins a dense facility gives the next one a reason to join too.
| Metro | Connected facilities |
|---|---|
| Amsterdam, NL | 33 |
| Frankfurt, DE | 29 |
| London, GB | 29 |
| Tokyo, JP | 25 |
| São Paulo, BR | 24 |
| Ashburn, US | 22 |
| Paris, FR | 21 |
| Kyiv, UA | 20 |
| Singapore, SG | 20 |
| New York, US | 20 |
Facilities with an active or dense connectivity band, 2026-06-10. Exact carrier and network counts are part of the operator dossier.
Why it matters for procurement
Connectivity density is a proxy for the things buyers actually pay for: lower latency to the networks you need, route redundancy when one carrier fails, and competitive transit pricing. Operator verification is a proxy for risk: a verified operator that runs its own building is a different counterparty than a reseller listing space it does not control. Shortlisting on those two signals — rather than on a name and a rate card — is the difference this dataset is built to make.