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 211 matching records, including the 189 positional ones with no capacity figure attached. Show only the 22 measured.
| Facility | Country | Type | Status | Power (MW) |
|---|---|---|---|---|
| noris network datacenter.de NBG6PeeringDB facility registry | DE | Colocation | Operational | — |
| firstcolo - FRA4PeeringDB facility registry | DE | Colocation | Operational | — |
| Iron Mountain Data Center - Frankfurt (FRA-2)PeeringDB facility registry | DE | Colocation | Operational | — |
| NorthC Munich 1PeeringDB facility registry | DE | Colocation | Operational | — |
| NorthC DuesseldorfPeeringDB facility registry | DE | Colocation | Operational | — |
| Speedbone BerlinPeeringDB facility registry | DE | Colocation | Operational | — |
| 3U Rechenzentrum BerlinPeeringDB facility registry | DE | Colocation | Operational | — |
| GlobalConnect Hamburg (HAM1)PeeringDB facility registry | DE | Colocation | Operational | — |
| GlobalConnect Hamburg (HAM2)PeeringDB facility registry | DE | Colocation | Operational | — |
| NorthC NürnbergPeeringDB facility registry | DE | Colocation | Operational | — |
| EMC Home of Data MUC I/II - MuCon-XPeeringDB facility registry | DE | Colocation | Operational | — |
| NorthC Munich 2PeeringDB facility registry | DE | Colocation | Operational | — |
| DeutschherrnkarreePeeringDB facility registry | DE | Colocation | Operational | — |
| Arelion Dusseldorf DDF/BPeeringDB facility registry | DE | Colocation | Operational | — |
| Cogent FrankfurtPeeringDB facility registry | DE | Colocation | Operational | — |
| WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7PeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Frankfurt 1 Data Center (FRA1)PeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Frankfurt 3 Data Center (FRA3)PeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Frankfurt 2 Data Center (FRA2)PeeringDB facility registry | DE | Colocation | Operational | — |
| aixit FrankfurtPeeringDB facility registry | DE | Colocation | Operational | — |
| NewColo FrankfurtPeeringDB facility registry | DE | Colocation | Operational | — |
| Hetzner Online FSN1 (Falkenstein)PeeringDB facility registry | DE | Colocation | Operational | — |
| Hetzner Online NBG1 (Nuremberg)PeeringDB facility registry | DE | Colocation | Operational | — |
| NorthC BerlinPeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix DU1 - DusseldorfPeeringDB facility registry | DE | Colocation | Operational | — |
| MK Netzdienste DatacenterPeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Munich 2 Data Center (MUC2)PeeringDB facility registry | DE | Colocation | Operational | — |
| WIIT Datacenter DUS5PeeringDB facility registry | DE | Colocation | Operational | — |
| noris network datacenter.de MUC5PeeringDB facility registry | DE | Colocation | Operational | — |
| NorthC HamburgPeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Rhein-Ruhr 1 Data Center (CGN1)PeeringDB facility registry | DE | Colocation | Operational | — |
| noris network datacenter.de NBG3 / NBG4PeeringDB facility registry | DE | Colocation | Operational | — |
| CarrierColo Berlin Luetzow (I/P/B/ site B)PeeringDB facility registry | DE | Colocation | Operational | — |
| DNS:NET Colo I BerlinPeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix FR2 - Frankfurt, NorthPeeringDB facility registry | DE | Colocation | Operational | — |
| euNetworks Colocation BerlinPeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix FR6 - Frankfurt, WestPeeringDB facility registry | DE | Colocation | Operational | — |
| Nepustil Stuttgart Zettachring 10aPeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Berlin 1 Data Center (BER1)PeeringDB facility registry | DE | Colocation | Operational | — |
| Digital Realty Frankfurt FRA29-32PeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix MU1/MU3 - MunichPeeringDB facility registry | DE | Colocation | Operational | — |
| Datacenter Leipzig - envia TEL GmbHPeeringDB facility registry | DE | Colocation | Operational | — |
| maincubes FRA01PeeringDB facility registry | DE | Colocation | Operational | — |
| Digital Realty Frankfurt FRA1-27PeeringDB facility registry | DE | Colocation | Operational | — |
| ITENOS Frankfurt (FRA1)PeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix FR5 - Frankfurt, KleyerStrassePeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix FR4 - Frankfurt, WestPeeringDB facility registry | DE | Colocation | Operational | — |
| Portus/IPHH HH3 (Wendenstrasse 251)PeeringDB facility registry | DE | Colocation | Operational | — |
| Equinix FR7 - Frankfurt, GutleutstrassePeeringDB facility registry | DE | Colocation | Operational | — |
| NTT Frankfurt 4 Data Center (FRA4)PeeringDB facility registry | DE | Colocation | Operational | — |