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) |
|---|---|---|---|---|
| Eurofiber Datacenter Rotterdam 2PeeringDB facility registry | NL | Colocation | Operational | — |
| Flexential - Denver/Aurora (DEN03)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Denver/Englewood (DEN11)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Minneapolis/Chaska (MSP01)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Las Vegas/Downtown (LAS03)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Las Vegas/North (LAS04)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Portland/Hillsboro (PDX01)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Salt Lake City/Downtown (SLC04)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Portland/Hillsboro 2 (PDX02)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Denver/Centennial (DEN05)PeeringDB facility registry | US | Colocation | Operational | — |
| InterDC DoetinchemPeeringDB facility registry | NL | Colocation | Operational | — |
| Flexential - Denver/Downtown (DEN02)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Dallas/Richardson (RCH01)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Salt Lake City/Cottonwood (SLC05)PeeringDB facility registry | US | Colocation | Operational | — |
| Flexential - Salt Lake City/Millcreek (SLC10)PeeringDB facility registry | US | Colocation | Operational | — |
| Sify Airoli-DC- MumbaiPeeringDB facility registry | IN | Colocation | Operational | — |
| Sify Rabale - MumbaiPeeringDB facility registry | IN | Colocation | Operational | — |
| Sify Vashi - MumbaiPeeringDB facility registry | IN | Colocation | Operational | — |
| Sify ITPL - BangalorePeeringDB facility registry | IN | Colocation | Operational | — |
| Sify Tidel-DC- ChennaiPeeringDB facility registry | IN | Colocation | Operational | — |
| DataBank Dallas (DFW5)PeeringDB facility registry | US | Colocation | Operational | — |
| Equinix ME4 - Melbourne, Derrimut (formerly Metronode Melbourne 2)PeeringDB facility registry | AU | Colocation | Operational | — |
| Equinix SY6 - Sydney (formerly Metronode Sydney 2)PeeringDB facility registry | AU | Colocation | Operational | — |
| Level(3) Atlanta (Courtland)PeeringDB facility registry | US | Colocation | Operational | — |
| Nxtra Data Chennai DC 1PeeringDB facility registry | IN | Colocation | Operational | — |
| Level(3) Chicago (Canal)PeeringDB facility registry | US | Colocation | Operational | — |
| Nxtra Data Bangalore DC 1PeeringDB facility registry | IN | Colocation | Operational | — |
| Cologix NNJ2PeeringDB facility registry | US | Colocation | Operational | — |
| Cologix NNJ3PeeringDB facility registry | US | Colocation | Operational | — |
| MedNautilus IstanbulPeeringDB facility registry | TR | Colocation | Operational | — |
| Equinix HE6 - Helsinki, SinimäkiPeeringDB facility registry | FI | Colocation | Operational | — |
| Cogent MontpellierPeeringDB facility registry | FR | Colocation | Operational | — |
| DRFortress HNLPeeringDB facility registry | US | Colocation | Operational | — |
| MEGA Two (iAdvantage Hong Kong)PeeringDB facility registry | HK | Colocation | Operational | — |
| Redcentric London Data CentrePeeringDB facility registry | GB | Colocation | Operational | — |
| Digital Realty SJC (2805 Lafayette)PeeringDB facility registry | US | Colocation | Operational | — |
| Digital Realty LAX (2260 E El Segundo)PeeringDB facility registry | US | Colocation | Operational | — |
| Miran-2PeeringDB facility registry | RU | Colocation | Operational | — |
| ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)PeeringDB facility registry | PL | Colocation | Operational | — |
| Equinix DA2 - DallasPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix DA7 - DallasPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix TR7 - Toronto, Brampton (formerly Q9 Brampton 4/5)PeeringDB facility registry | CA | Colocation | Operational | — |
| Centersquare Northern Virginia (IAD1-A/F)PeeringDB facility registry | US | Colocation | Operational | — |
| Centersquare New Jersey (EWR2)PeeringDB facility registry | US | Colocation | Operational | — |
| Centersquare Los Angeles (LAX3)PeeringDB facility registry | US | Colocation | Operational | — |
| Cogent ToulousePeeringDB facility registry | FR | Colocation | Operational | — |
| Cogent FrankfurtPeeringDB facility registry | DE | Colocation | Operational | — |
| Nusantara Data Center - JakartaPeeringDB facility registry | ID | Colocation | Operational | — |
| Nusantara Data Center - MedanPeeringDB facility registry | ID | Colocation | Operational | — |
| Nusantara Data Center - BatamPeeringDB facility registry | ID | Colocation | Operational | — |