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) |
|---|---|---|---|---|
| Evocative ATL1PeeringDB facility registry | US | Colocation | Operational | — |
| NJFXPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix SV1/SV5/SV10 - Silicon Valley, San JosePeeringDB facility registry | US | Colocation | Operational | — |
| H5 Data Centers San AntonioPeeringDB facility registry | US | Colocation | Operational | — |
| NYI NY2 (60 Hudson Street)PeeringDB facility registry | US | Colocation | Operational | — |
| Iron Mountain Data Center - Boston (BOS-1)PeeringDB facility registry | US | Colocation | Operational | — |
| Iron Mountain Data Center - Western Pennsylvania (WPA-1)PeeringDB facility registry | US | Colocation | Operational | — |
| Iron Mountain Data Center - Kansas City (KCM-1)PeeringDB facility registry | US | Colocation | Operational | — |
| H5 Data Centers CincinnatiPeeringDB facility registry | US | Colocation | Operational | — |
| Telecom Center LAPeeringDB facility registry | US | Colocation | Operational | — |
| RagingWire TX1 - NTTPeeringDB facility registry | US | Colocation | Operational | — |
| RagingWire VA3 - NTTPeeringDB facility registry | US | Colocation | Operational | — |
| Colocation Northwest - SeattlePeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty CHI (505 N Railroad)PeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - Atlanta (AT2)PeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - Reston (VA1)PeeringDB facility registry | US | Colocation | Operational | — |
| Centersquare Northern Virginia (IAD4)PeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - Miami (MI1)PeeringDB facility registry | US | Colocation | Operational | — |
| CoreSite - New York (NY1)PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) RaleighPeeringDB facility registry | US | Colocation | Operational | — |
| ColoHouse MiamiPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix DA3 - DallasPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix DE2 - DenverPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix CH1/CH2/CH4 - ChicagoPeeringDB facility registry | US | Colocation | Operational | — |
| Hurricane Electric Fremont 1PeeringDB facility registry | US | Colocation | Operational | — |
| Lumen NorfolkPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix SE4 - Seattle, KentPeeringDB facility registry | US | 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 | — |
| TierPoint Omaha - BellevuePeeringDB facility registry | US | Colocation | Operational | — |
| Telehouse - Teleport Center (New York)PeeringDB facility registry | US | Colocation | Operational | — |
| Neutron - SpokanePeeringDB facility registry | US | Colocation | Operational | — |
| Switch Las VegasPeeringDB facility registry | US | Colocation | Operational | — |
| SFN IA-DavenportPeeringDB facility registry | US | Colocation | Operational | — |
| Aligned Dallas (DFW-01)PeeringDB facility registry | US | Colocation | Operational | — |
| Aligned Phoenix (PHX-01)PeeringDB facility registry | US | Colocation | Operational | — |
| Aligned Salt Lake (SLC-02)PeeringDB facility registry | US | Colocation | Operational | — |
| QTS Hillsboro (HIL1)PeeringDB facility registry | US | Colocation | Operational | — |
| Coloblox Data Centers ATL1PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix LA1 - Los AngelesPeeringDB facility registry | US | Colocation | Operational | — |
| Cologix MIN1PeeringDB facility registry | US | Colocation | Operational | — |
| Stream Data Centers - DFW VIIPeeringDB facility registry | US | Colocation | Operational | — |
| Stream Data Centers - Chicago IPeeringDB facility registry | US | Colocation | Operational | — |
| FIBERTOWN Houston Data CenterPeeringDB facility registry | US | Colocation | Operational | — |
| ark data centers - Tucson, AZPeeringDB facility registry | US | Colocation | Operational | — |
| T5@ChicagoPeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Atlanta (ATL1)PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix SV17 - Silicon Valley, Santa ClaraPeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) Salt Lake CityPeeringDB facility registry | US | Colocation | Operational | — |