Entities
Registers of the facilities, companies and countries on record, with the ownership chains between them.
710 of 4,257 facility records carry an operational measure
4,257 facility records are individually browsable here, of which 710 carry an operational measure: power, GPU or FLOP capacity, or a substantive description. The other 3,547 establish that a site exists and stop there. Which of the two a record is depends almost entirely on the catalogue it arrived in.
Two counts appear on this page and they are not the same quantity. The masthead stamps 4,573 tracked records: the full corpus across 110 countries, the figure used site-wide. The register and the plate count the 4,257 that are individually browsable; the 316 in between are rows a licensing term keeps from being served as their own record. They inform aggregates and they are not hidden. They cannot be opened, so a figure about what a reader can inspect must not count them. The same universe is plotted in space on the map, rolled up by jurisdiction on Countries, and the organisations that own and operate these sites are in the company register.
- Epoch AI Frontier Data Centers7064 measured91.4%
- Epoch AI GPU Clusters437397 measured90.8%
- PeeringDB facility registry1,56963 measured4.0%
- IM3 / PNNL data-center corpus3912 measured0.5%
- OpenStreetMap (tagged data centers)1,1731 measured0.1%
- OpenStreetMap2310 measured0.0%
- Microsoft Azure region documentation560 measured0.0%
- Oracle Cloud region documentation450 measured0.0%
- 43 smaller catalogues285183 measured64.2%
Epoch AI Frontier Data Centers runs 91.4% measured across 70 records; OpenStreetMap runs 0.0% across 231. No single catalogue falls in between; the hatched band does, but it is the fold of 43 smaller catalogues and reads mid-scale only because it averages the two kinds. The separation exists because the two kinds of catalogue do different jobs: one is a research dataset built by measuring sites, the other an infrastructure registry built by recording that they exist. Any band’s key below opens the register scoped to that catalogue’s rows.
This is why the register opens on the measured cohort and says so; shown whole, most of the 4,257 rows could not answer the question a reader arrived with. The positional records are not filler: a site that exists is a real fact, and for a governance reader tracing where capacity might appear it is often the fact that matters. But it is a different fact from a megawatt figure, and a register that prints them in one undifferentiated count makes a uniformity claim its records do not support.
The register
Showing all 4,257 records, including the 3,547 positional ones with no capacity figure attached. Show only the 710 measured.
| Facility | Country | Type | Status | Power (MW) |
|---|---|---|---|---|
| STT Delhi 3PeeringDB facility registry | IN | Colocation | Operational | — |
| STT Mumbai 2PeeringDB facility registry | IN | Colocation | Operational | — |
| ColoHouse MiamiPeeringDB facility registry | US | Colocation | Operational | — |
| NEXTDC P2PeeringDB facility registry | AU | Colocation | Operational | — |
| NEXTDC S2PeeringDB facility registry | AU | Colocation | Operational | — |
| Digital Realty BRU1 - BrusselsPeeringDB facility registry | BE | Colocation | Operational | — |
| Equinix FR4 - Frankfurt, WestPeeringDB facility registry | DE | Colocation | Operational | — |
| Teraco Johannesburg Bredell CampusPeeringDB facility registry | ZA | Colocation | Operational | — |
| Equinix SK2 - Stockholm, SköndalPeeringDB facility registry | SE | Colocation | Operational | — |
| Verizon IstanbulPeeringDB facility registry | TR | Colocation | Operational | — |
| NTT Serangoon Data Center (SG1)PeeringDB facility registry | SG | Colocation | Operational | — |
| Equinix DA3 - DallasPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix ME5 - Melbourne (formerly Metronode Melbourne 1)PeeringDB facility registry | AU | Colocation | Operational | — |
| Equinix DE2 - DenverPeeringDB facility registry | US | Colocation | Operational | — |
| NTT Com Asia Tai PoPeeringDB facility registry | HK | Colocation | Operational | — |
| Free Pro - Lyon - RockPeeringDB facility registry | FR | Colocation | Operational | — |
| CNI DC DPSPeeringDB facility registry | ID | Colocation | Operational | — |
| Equinix CH1/CH2/CH4 - ChicagoPeeringDB facility registry | US | Colocation | Operational | — |
| Telehouse Toronto (905 King Street West)PeeringDB facility registry | CA | Colocation | Operational | — |
| Hurricane Electric Fremont 1PeeringDB facility registry | US | Colocation | Operational | — |
| TOPNET/UA/Leontovicha9PeeringDB facility registry | UA | Colocation | Operational | — |
| NTT DOCOMO BUSINESS Tokyo (NW1)PeeringDB facility registry | JP | Colocation | Operational | — |
| Netia Warsaw (WARSC001)PeeringDB facility registry | PL | Colocation | Operational | — |
| Lumen NorfolkPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix SG2 - SingaporePeeringDB facility registry | SG | Colocation | Operational | — |
| Radore IstanbulPeeringDB facility registry | TR | Colocation | Operational | — |
| Global-e Datacenter NLRI1PeeringDB facility registry | NL | Colocation | Operational | — |
| Equinix SE4 - Seattle, KentPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix SO2 - SofiaPeeringDB facility registry | BG | Colocation | Operational | — |
| Equinix HE7 - Helsinki, SinimäkiPeeringDB facility registry | FI | Colocation | Operational | — |
| Equinix WA3 - WarsawPeeringDB facility registry | PL | Colocation | Operational | — |
| Digital Realty Seattle SEA10PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix CU1/CU2/CU3/CU4 - CulpeperPeeringDB facility registry | US | Colocation | Operational | — |
| Evocative DAL6PeeringDB facility registry | US | Colocation | Operational | — |
| Telxius Barracas, Buenos AiresPeeringDB facility registry | AR | Colocation | Operational | — |
| Digital Realty Paris PAR5PeeringDB facility registry | FR | Colocation | Operational | — |
| Digital Realty Paris PAR6PeeringDB facility registry | FR | Colocation | Operational | — |
| Penta Infra Leeuwarden LEE01PeeringDB facility registry | NL | Colocation | Operational | — |
| Equinix PA3 - Paris, Saint-DenisPeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent BordeauxPeeringDB facility registry | FR | Colocation | Operational | — |
| Equinix PA7 - Paris, Energy ParkPeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent DijonPeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent GrenoblePeeringDB facility registry | FR | Colocation | Operational | — |
| ETIX Lyon #1PeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent NantesPeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent PoitiersPeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent RennesPeeringDB facility registry | FR | Colocation | Operational | — |
| TierPoint Omaha - BellevuePeeringDB facility registry | US | Colocation | Operational | — |
| Portus/IPHH HH3 (Wendenstrasse 251)PeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix PA5 - Paris, Victor HugoPeeringDB facility registry | FR | Colocation | Operational | — |