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) |
|---|---|---|---|---|
| DataBank Houston West (HOU1) (HOU2)PeeringDB facility registry | US | Colocation | Operational | — |
| CyrusOne Dallas (Lewisville)PeeringDB facility registry | US | Colocation | Operational | — |
| CyrusOne Dallas (Carrollton)PeeringDB facility registry | US | Colocation | Operational | — |
| CyrusOne Chicago (Lombard)PeeringDB facility registry | US | Colocation | Operational | — |
| CyrusOne PhoenixPeeringDB facility registry | US | Colocation | Operational | — |
| iM Critical MiamiPeeringDB facility registry | US | Colocation | Operational | — |
| Cologix DSM2PeeringDB facility registry | US | Colocation | Operational | — |
| Cologix DSM1PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix MI1 - Miami, NOTAPeeringDB facility registry | US | Colocation | Operational | — |
| 60 HudsonPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix DC16PeeringDB facility registry | US | Colocation | Operational | — |
| TierPoint St. Louis - LocustPeeringDB facility registry | US | Colocation | Operational | — |
| Lumen Kansas CityPeeringDB facility registry | US | Colocation | Operational | — |
| Clackamas ESD DatacenterPeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Las Vegas (LAS1)PeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty NYC (111 8th Ave)PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) NewarkPeeringDB facility registry | US | Colocation | Operational | — |
| H5 Data Centers OmahaPeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - Santa Clara (SV4)PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) BellevuePeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) HaywardPeeringDB facility registry | US | Colocation | Operational | — |
| QTS Atlanta-Fayetteville (ATL2)PeeringDB facility registry | US | Colocation | Operational | — |
| QTS Charlotte (CTL1)PeeringDB facility registry | US | Colocation | Operational | — |
| QTS Richmond - (RIC5)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Orangeburg (LGA3)PeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - Secaucus (NY2)PeeringDB facility registry | US | Colocation | Operational | — |
| Northwestern University co-location facilityPeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty PHX10 (120 E Van Buren)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Miami (MIA1)PeeringDB facility registry | US | Colocation | Operational | — |
| Data Foundry Texas 1PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) Austin (Kramer)PeeringDB facility registry | US | Colocation | Operational | — |
| SBA Edge, LLCPeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) Chicago (Kingsbury)PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) Miami (5th St)PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) HerndonPeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty New Jersey EWR10 (closed)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Dallas (DFW6)PeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty Boston BOS16 (closed)PeeringDB facility registry | US | Colocation | Operational | — |
| H5 Data Centers New YorkPeeringDB facility registry | US | Colocation | Operational | — |
| DataBank New York (LGA2)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Newark (EWR1)PeeringDB facility registry | US | Colocation | Operational | — |
| WOW! Business (Columbus Datacenter)PeeringDB facility registry | US | Colocation | Operational | — |
| Evocative SJC11PeeringDB facility registry | US | Colocation | Operational | — |
| Netrality - Indy Telcom Center - 733 W. HenryPeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Seattle (SEA1)PeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty IAD (43940 Digital Loudoun)PeeringDB facility registry | US | Colocation | Operational | — |
| QTS Phoenix (PHX1)PeeringDB facility registry | US | Colocation | Operational | — |
| Iron Mountain Data Center - Denver (DEN-1)PeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - Los Angeles (LA1) One WilshirePeeringDB facility registry | US | Colocation | Operational | — |
| EdgeConneX Phoenix (EDCPHX01)PeeringDB facility registry | US | Colocation | Operational | — |