Skip to main content
4,573 tracked

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 on this page

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.

  1. Epoch AI Frontier Data Centers7064 measured91.4%
  2. Epoch AI GPU Clusters437397 measured90.8%
  3. PeeringDB facility registry1,56963 measured4.0%
  4. IM3 / PNNL data-center corpus3912 measured0.5%
  5. OpenStreetMap (tagged data centers)1,1731 measured0.1%
  6. OpenStreetMap2310 measured0.0%
  7. Microsoft Azure region documentation560 measured0.0%
  8. Oracle Cloud region documentation450 measured0.0%
  9. 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 carrying at least one operational measure (power, GPU or FLOP capacity, or a substantive description). 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 26 August 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. 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.

2,7012,750 of 4,257Page 55 of 86
FacilityCountryTypeStatusPower (MW)
NorthC Rotterdam Zestienhoven 1PeeringDB facility registryNLColocationOperational
NorthC NieuwegeinPeeringDB facility registryNLColocationOperational
DTP GSD AlphaPeeringDB facility registryIDColocationOperational
Telehouse - FrankfurtPeeringDB facility registryDEColocationOperational
Equinix ML5 - MilanPeeringDB facility registryITColocationOperational
NorthC Amsterdam 1PeeringDB facility registryNLColocationOperational
STT Makati (Formerly MK2)PeeringDB facility registryPHColocationOperational
Green Datacenter ZRH1 (fka: Green Lupfig)PeeringDB facility registryCHColocationOperational
EdgeConneX Munich (EDCMUC01)PeeringDB facility registryDEColocationOperational
DEEP Resilience Centre Luxembourg SouthPeeringDB facility registryLUColocationOperational
Odata DC BG01PeeringDB facility registryCOColocationOperational
DataBank San Diego (SAN1)PeeringDB facility registryUSColocationOperational
DataBank McLean (IAD2)PeeringDB facility registryUSColocationOperational
DataBank Chicago (ORD2)PeeringDB facility registryUSColocationOperational
DataBank Chicago (ORD4)PeeringDB facility registryUSColocationOperational
DataBank Denver (DEN3)PeeringDB facility registryUSColocationOperational
DataBank Denver (DEN4)PeeringDB facility registryUSColocationOperational
DataBank Piscataway (EWR2)PeeringDB facility registryUSColocationOperational
DataBank Dallas (DFW4)PeeringDB facility registryUSColocationOperational
DataBank Dallas (DFW7)PeeringDB facility registryUSColocationOperational
DataBank Austin (AUS1)PeeringDB facility registryUSColocationOperational
DataBank Waco (ACT1)PeeringDB facility registryUSColocationOperational
DataBank Kansas City (MCI3)PeeringDB facility registryUSColocationOperational
DataBank Minneapolis (MSP4)PeeringDB facility registryUSColocationOperational
DataBank Indianapolis (IND1)PeeringDB facility registryUSColocationOperational
DataBank Phoenix (PHX1)PeeringDB facility registryUSColocationOperational
DataBank Phoenix (PHX2)PeeringDB facility registryUSColocationOperational
DataBank Phoenix (PHX3)PeeringDB facility registryUSColocationOperational
PIX Samm FloridaPeeringDB facility registryBRColocationOperational
Equinix AT2/AT3 - AtlantaPeeringDB facility registryUSColocationOperational
BIT-1PeeringDB facility registryNLColocationOperational
Matrix Data Center JK3 (MDC JK3)PeeringDB facility registryIDColocationOperational
Digital Realty SJC (2220 De La Cruz Blvd)PeeringDB facility registryUSColocationOperational
nLighten Besancon MLH1PeeringDB facility registryFRColocationOperational
RagingWire CA1 - NTTPeeringDB facility registryUSColocationOperational
STT Quezon City (Formerly QC2)PeeringDB facility registryPHColocationOperational
RagingWire VA1 - NTTPeeringDB facility registryUSColocationOperational
neuCentrIX - Karet TengsinPeeringDB facility registryIDColocationOperational
neuCentrIX - Surabaya GubengPeeringDB facility registryIDColocationOperational
PIX DBUGPeeringDB facility registryBRColocationOperational
Equinix HK2 - Hong KongPeeringDB facility registryHKColocationOperational
Equinix MU4 - Munich, DornachPeeringDB facility registryDEColocationOperational
Databridge Sites Silver SpringPeeringDB facility registryUSColocationOperational
Level(3) Paris (Le Capitole)PeeringDB facility registryFRColocationOperational
Bezeq International Shacham Data CenterPeeringDB facility registryILColocationOperational
PIX Nossa Telecom PAEPeeringDB facility registryBRColocationOperational
Data Center Ukr-ComPeeringDB facility registryUAColocationOperational
STT Bangkok 1PeeringDB facility registryTHColocationOperational
Cirion La UrbinaPeeringDB facility registryVEColocationOperational
Equinix BX1 - BordeauxPeeringDB facility registryFRColocationOperational