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) |
|---|---|---|---|---|
| DCI Indonesia (JK5)PeeringDB facility registry | ID | Colocation | Operational | — |
| HivelocityPeeringDB facility registry | US | Colocation | Operational | — |
| Equinix SY1/SY2 - SydneyPeeringDB facility registry | AU | Colocation | Operational | — |
| IPTP, Matrix 4, Amsterdam, The NetherlandsPeeringDB facility registry | NL | Colocation | Operational | — |
| COLT in Asia Tokyo Data Center 1 (TDC1)PeeringDB facility registry | JP | Colocation | Operational | — |
| NTT Bangkok 2 Data Center (BKK2)PeeringDB facility registry | TH | Colocation | Operational | — |
| 5GN Melbourne Data Centre (MDC)PeeringDB facility registry | AU | Colocation | Operational | — |
| Equinix AM3 - Amsterdam, Science ParkPeeringDB facility registry | NL | Colocation | Operational | — |
| CyrusOne Madrid 1PeeringDB facility registry | ES | Colocation | Operational | — |
| firstcolo - FRA4PeeringDB facility registry | DE | Colocation | Operational | — |
| Qatar Data Center 5PeeringDB facility registry | QA | Colocation | Operational | — |
| TIVIT Sao PauloPeeringDB facility registry | BR | Colocation | Operational | — |
| DataBank Minneapolis (MSP3)PeeringDB facility registry | US | Colocation | Operational | — |
| brusselsdcPeeringDB facility registry | BE | Colocation | Operational | — |
| Cologix VAN1PeeringDB facility registry | CA | Colocation | Operational | — |
| Qupra DCPeeringDB facility registry | NL | Colocation | Operational | — |
| Pulsant Manchester NW-1PeeringDB facility registry | GB | Colocation | Operational | — |
| Layer1PeeringDB facility registry | UA | Colocation | Operational | — |
| Quantum Switch DOA APeeringDB facility registry | QA | Colocation | Operational | — |
| Quantum Switch DMM APeeringDB facility registry | SA | Colocation | Operational | — |
| CoreSite - Atlanta (AT1)PeeringDB facility registry | US | Colocation | Operational | — |
| IXcellerate MOS1PeeringDB facility registry | RU | Colocation | Operational | — |
| Flexential - Atlanta/Douglasville (ATL5)PeeringDB facility registry | US | Colocation | Operational | — |
| NEXTDC M1PeeringDB facility registry | AU | Colocation | Operational | — |
| Flexential - Portland/Hillsboro 3 (PDX03)PeeringDB facility registry | US | Colocation | Operational | — |
| NEXTDC B1PeeringDB facility registry | AU | Colocation | Operational | — |
| NorthC DelftPeeringDB facility registry | NL | Colocation | Operational | — |
| Balkan Gate ThessalonikiPeeringDB facility registry | GR | Colocation | Operational | — |
| neuCentrIX - Yogyakarta Kota BaruPeeringDB facility registry | ID | Colocation | Operational | — |
| DGN Teknoloji - BursaPeeringDB facility registry | TR | Colocation | Operational | — |
| EdgeCore VA1PeeringDB facility registry | US | Colocation | Operational | — |
| EvoSwitch WDC1PeeringDB facility registry | US | Colocation | Operational | — |
| EdgeCore VA2PeeringDB facility registry | US | Colocation | Operational | — |
| EdgeCore Reno 1PeeringDB facility registry | US | Colocation | Operational | — |
| Area31 Data CenterPeeringDB facility registry | ID | Colocation | Operational | — |
| Level(3) BrusselsPeeringDB facility registry | BE | Colocation | Operational | — |
| STACK infrastructure ZUR01PeeringDB facility registry | CH | Colocation | Operational | — |
| Lumen JacksonvillePeeringDB facility registry | US | Colocation | Operational | — |
| Lumen PortlandPeeringDB facility registry | US | Colocation | Operational | — |
| Lumen PittsburghPeeringDB facility registry | US | Colocation | Operational | — |
| Lumen PhiladelphiaPeeringDB facility registry | US | Colocation | Operational | — |
| 2degrees Auckland - AlbanyPeeringDB facility registry | NZ | Colocation | Operational | — |
| Equinix BG1 - BogotaPeeringDB facility registry | CO | Colocation | Operational | — |
| Equinix DX1 - DubaiPeeringDB facility registry | AE | Colocation | Operational | — |
| Iron Mountain Data Center - Bangalore (BLR-1)PeeringDB facility registry | IN | Colocation | Operational | — |
| Iron Mountain Data Center - Hyderabad (HYD-1)PeeringDB facility registry | IN | Colocation | Operational | — |
| Iron Mountain Data Center - Mumbai (MUM-1)PeeringDB facility registry | IN | Colocation | Operational | — |
| Iron Mountain Data Center - Delhi (NCR-1)PeeringDB facility registry | IN | Colocation | Operational | — |
| Iron Mountain Data Center - Pune (PUN-1)PeeringDB facility registry | IN | Colocation | Operational | — |
| Iron Mountain Data Center - Frankfurt (FRA-2)PeeringDB facility registry | DE | Colocation | Operational | — |