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,9012,950 of 4,257Page 59 of 86
FacilityCountryTypeStatusPower (MW)
DCI Indonesia (JK5)PeeringDB facility registryIDColocationOperational
HivelocityPeeringDB facility registryUSColocationOperational
Equinix SY1/SY2 - SydneyPeeringDB facility registryAUColocationOperational
IPTP, Matrix 4, Amsterdam, The NetherlandsPeeringDB facility registryNLColocationOperational
COLT in Asia Tokyo Data Center 1 (TDC1)PeeringDB facility registryJPColocationOperational
NTT Bangkok 2 Data Center (BKK2)PeeringDB facility registryTHColocationOperational
5GN Melbourne Data Centre (MDC)PeeringDB facility registryAUColocationOperational
Equinix AM3 - Amsterdam, Science ParkPeeringDB facility registryNLColocationOperational
CyrusOne Madrid 1PeeringDB facility registryESColocationOperational
firstcolo - FRA4PeeringDB facility registryDEColocationOperational
Qatar Data Center 5PeeringDB facility registryQAColocationOperational
TIVIT Sao PauloPeeringDB facility registryBRColocationOperational
DataBank Minneapolis (MSP3)PeeringDB facility registryUSColocationOperational
brusselsdcPeeringDB facility registryBEColocationOperational
Cologix VAN1PeeringDB facility registryCAColocationOperational
Qupra DCPeeringDB facility registryNLColocationOperational
Pulsant Manchester NW-1PeeringDB facility registryGBColocationOperational
Layer1PeeringDB facility registryUAColocationOperational
Quantum Switch DOA APeeringDB facility registryQAColocationOperational
Quantum Switch DMM APeeringDB facility registrySAColocationOperational
CoreSite - Atlanta (AT1)PeeringDB facility registryUSColocationOperational
IXcellerate MOS1PeeringDB facility registryRUColocationOperational
Flexential - Atlanta/Douglasville (ATL5)PeeringDB facility registryUSColocationOperational
NEXTDC M1PeeringDB facility registryAUColocationOperational
Flexential - Portland/Hillsboro 3 (PDX03)PeeringDB facility registryUSColocationOperational
NEXTDC B1PeeringDB facility registryAUColocationOperational
NorthC DelftPeeringDB facility registryNLColocationOperational
Balkan Gate ThessalonikiPeeringDB facility registryGRColocationOperational
neuCentrIX - Yogyakarta Kota BaruPeeringDB facility registryIDColocationOperational
DGN Teknoloji - BursaPeeringDB facility registryTRColocationOperational
EdgeCore VA1PeeringDB facility registryUSColocationOperational
EvoSwitch WDC1PeeringDB facility registryUSColocationOperational
EdgeCore VA2PeeringDB facility registryUSColocationOperational
EdgeCore Reno 1PeeringDB facility registryUSColocationOperational
Area31 Data CenterPeeringDB facility registryIDColocationOperational
Level(3) BrusselsPeeringDB facility registryBEColocationOperational
STACK infrastructure ZUR01PeeringDB facility registryCHColocationOperational
Lumen JacksonvillePeeringDB facility registryUSColocationOperational
Lumen PortlandPeeringDB facility registryUSColocationOperational
Lumen PittsburghPeeringDB facility registryUSColocationOperational
Lumen PhiladelphiaPeeringDB facility registryUSColocationOperational
2degrees Auckland - AlbanyPeeringDB facility registryNZColocationOperational
Equinix BG1 - BogotaPeeringDB facility registryCOColocationOperational
Equinix DX1 - DubaiPeeringDB facility registryAEColocationOperational
Iron Mountain Data Center - Bangalore (BLR-1)PeeringDB facility registryINColocationOperational
Iron Mountain Data Center - Hyderabad (HYD-1)PeeringDB facility registryINColocationOperational
Iron Mountain Data Center - Mumbai (MUM-1)PeeringDB facility registryINColocationOperational
Iron Mountain Data Center - Delhi (NCR-1)PeeringDB facility registryINColocationOperational
Iron Mountain Data Center - Pune (PUN-1)PeeringDB facility registryINColocationOperational
Iron Mountain Data Center - Frankfurt (FRA-2)PeeringDB facility registryDEColocationOperational