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) |
|---|---|---|---|---|
| Amazon IAD102OpenStreetMap (tagged data centers) | US | Hyperscale DC | Operational | — |
| OVHcloud HIL-1OVHcloud universal registration document (2024) | US | Hyperscale DC | Operational | — |
| OVHcloud VIN-1OVHcloud universal registration document (2024) | US | Hyperscale DC | Operational | — |
| Equinix DC1-DC15,DC21-DC22 - AshburnPeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty NYC (60 Hudson)PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix LA2 - Los AngelesPeeringDB facility registry | US | Colocation | Operational | — |
| LCOG Park PlacePeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) Seattle (Denny Way)PeeringDB facility registry | US | Colocation | Operational | — |
| Zayo NetworksPeeringDB facility registry | US | Colocation | Operational | — |
| SBA Edge - Jacksonville (JAX)PeeringDB facility registry | US | Colocation | Operational | — |
| OpenColoPeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty DFW18 (1210 Integrity Dr)PeeringDB facility registry | US | Colocation | Operational | — |
| Level(3) Kansas CityPeeringDB facility registry | US | Colocation | Operational | — |
| DataBank San Diego (SAN1)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank McLean (IAD2)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Chicago (ORD2)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Chicago (ORD4)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Denver (DEN3)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Denver (DEN4)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Piscataway (EWR2)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Dallas (DFW4)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Dallas (DFW7)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Austin (AUS1)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Waco (ACT1)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Kansas City (MCI3)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Minneapolis (MSP4)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Indianapolis (IND1)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Phoenix (PHX1)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Phoenix (PHX2)PeeringDB facility registry | US | Colocation | Operational | — |
| DataBank Phoenix (PHX3)PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix AT2/AT3 - AtlantaPeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty SJC (2220 De La Cruz Blvd)PeeringDB facility registry | US | Colocation | Operational | — |
| RagingWire CA1 - NTTPeeringDB facility registry | US | Colocation | Operational | — |
| RagingWire VA1 - NTTPeeringDB facility registry | US | Colocation | Operational | — |
| Databridge Sites Silver SpringPeeringDB facility registry | US | Colocation | Operational | — |
| TierPoint BethlehemPeeringDB facility registry | US | Colocation | Operational | — |
| TierPoint Boston - MarlboroughPeeringDB facility registry | US | Colocation | Operational | — |
| TierPoint St. Louis – MillparkPeeringDB facility registry | US | Colocation | Operational | — |
| Cologix SV1PeeringDB facility registry | US | Colocation | Operational | — |
| Cologix ASH1PeeringDB facility registry | US | Colocation | Operational | — |
| Ridgeview MinnetonkaPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix DA11 - DallasPeeringDB facility registry | US | Colocation | Operational | — |
| QTS Piscataway (PNJ1)PeeringDB facility registry | US | Colocation | Operational | — |
| T5@SiliconValleyPeeringDB facility registry | US | Colocation | Operational | — |
| T5@PortlandPeeringDB facility registry | US | Colocation | Operational | — |
| T5@CharlottePeeringDB facility registry | US | Colocation | Operational | — |
| T5@AtlantaPeeringDB facility registry | US | Colocation | Operational | — |
| T5@AugustaPeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty NYC (32 AofA)PeeringDB facility registry | US | Colocation | Operational | — |
| Lumen Tulsa 1PeeringDB facility registry | US | Colocation | Operational | — |