Entities
Registers of the facilities, companies and countries on record, with the ownership chains between them.
709 of 4,257 facility records have an operational measure
4,257 facility records are individually browsable here, of which 709 have an operational measure: power, GPU or FLOP capacity, or a substantive description. The other 3,548 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 Clusters437396 measured90.6%
- 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%
Coverage by catalogue. Each band is one catalogue: its length is that catalogue’s share of the largest one’s row count, and the inked run inside it is the rows with at least one operational measure.
Nothing here is schematic; both lengths are measured proportions of the counts printed beside them.
No share-of-megawatts is drawn: every megawatt-bearing row satisfies the measured predicate by construction, so a capacity share would be a tautology.
Counts cover the full individually-browsable set, 4,257 rows, read 4 September 2026.
The smallest catalogues are folded into one band whose run is hatched, because it averages catalogues of both kinds. Each named catalogue’s key opens the register below scoped to its rows.
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.
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 1,303 matching records, including the 1,010 positional ones with no capacity figure attached. Show only the 293 measured.
| Facility | Country | Type | Status | Power (MW) |
|---|---|---|---|---|
| Cogent Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cologix Jacksonville JAX1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| ColovoreIM3 / PNNL data-center corpus | US | Other | Operational | — |
| Compass Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| COPT Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| CoreSite AT1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite BO1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite Chicago Data Center (CH2)IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite DC1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite NY3IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite Reston Campus VA1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite SV2IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSite SV3IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CoreSpace DallasIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cox Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Credit Suisse: Clifton Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Crown Castle BaltimoreIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Csquare SFO1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Csquare SFO2IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Csquare SFO3IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Csquare SFO4IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyberNAP Glen BurnieIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne Austin Data Center IIIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne Chicago Aurora CMEIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne CIN2IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne Cincinnati-Hamilton CIN4IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne Cincinnati-LebanonIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne Cincinnati-Mason CIN3IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne NorwalkIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne NVA1, NVA2 & NVA3IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne NVA5IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne PHX1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne San Antonio IIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne SomersetIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CyrusOne Sterling IXIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CYS41 DatacenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| CYS42 DatacenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Cyxtera Dallas-Fort Worth Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cyxtera (Digital Realty Trust) Citibank Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cyxtera Tampa TP1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Dakota Carrier NetworkIM3 / PNNL data-center corpus | US | Other | Operational | — |
| Data Center LenexaIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Data Holdings Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| DataBank Dallas Empire Central Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| DataBank Pittsburgh PIT2IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| DataBank Santa Clara SFO1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| DataBankIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| DataSite AtlantaIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| DBT Data - Harrisonburg CenterIM3 / PNNL data-center corpus | US | Other | Operational | — |
| Digital CrossroadIM3 / PNNL data-center corpus | US | Colocation | Operational | — |