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.

3,1013,150 of 4,257Page 63 of 86
FacilityCountryTypeStatusPower (MW)
Obenet RiverlakePeeringDB facility registrySEColocationOperational
CoreSite - Santa Clara (SV4)PeeringDB facility registryUSColocationOperational
OMNIDC JAKARTAPeeringDB facility registryIDColocationOperational
NTT-ME Ikebukuro DCPeeringDB facility registryJPColocationOperational
NTT-ME Marunouchi DCPeeringDB facility registryJPColocationOperational
NTT-ME Kayabakabuto DCPeeringDB facility registryJPColocationOperational
NTT-ME Kuramae DCPeeringDB facility registryJPColocationOperational
TATA Communications DelhiPeeringDB facility registryINColocationOperational
SDCT Data CenterPeeringDB facility registryIDColocationOperational
Voxility IR1 BucharestPeeringDB facility registryROColocationOperational
Level(3) BellevuePeeringDB facility registryUSColocationOperational
Equinix DB1 - Dublin, CityWestPeeringDB facility registryIEColocationOperational
Level(3) HaywardPeeringDB facility registryUSColocationOperational
3U Rechenzentrum BerlinPeeringDB facility registryDEColocationOperational
SEACOM Mombasa CLSPeeringDB facility registryKEColocationOperational
Equinix SP4 - São PauloPeeringDB facility registryBRColocationOperational
1-DC EUPeeringDB facility registryPLColocationOperational
QTS Atlanta-Fayetteville (ATL2)PeeringDB facility registryUSColocationOperational
QTS Charlotte (CTL1)PeeringDB facility registryUSColocationOperational
QTS Richmond - (RIC5)PeeringDB facility registryUSColocationOperational
DataBank Orangeburg (LGA3)PeeringDB facility registryUSColocationOperational
NEXTDC S1PeeringDB facility registryAUColocationOperational
Vocus Melbourne MEL03PeeringDB facility registryAUColocationOperational
Harbour Centre VancouverPeeringDB facility registryCAColocationOperational
CoreSite - Secaucus (NY2)PeeringDB facility registryUSColocationOperational
Orange Polska / Warsaw św. Barbary 10PeeringDB facility registryPLColocationOperational
Digital Realty Lekki (LKK1-2)PeeringDB facility registryNGColocationOperational
Equinix CN1 - ChennaiPeeringDB facility registryINColocationOperational
Equinix TY1 - TokyoPeeringDB facility registryJPColocationOperational
ANS - MAN6PeeringDB facility registryGBColocationOperational
GlobalConnect Hamburg (HAM1)PeeringDB facility registryDEColocationOperational
GlobalConnect Hamburg (HAM2)PeeringDB facility registryDEColocationOperational
Digital Realty London LHR26PeeringDB facility registryGBColocationOperational
Equinix HK1 - Hong KongPeeringDB facility registryHKColocationOperational
Cologix CGY1PeeringDB facility registryCAColocationOperational
Reliance HousePeeringDB facility registryGBColocationOperational
Equinix HK6 - Hong KongPeeringDB facility registryHKColocationOperational
Northwestern University co-location facilityPeeringDB facility registryUSColocationOperational
Digital Realty PHX10 (120 E Van Buren)PeeringDB facility registryUSColocationOperational
DataBank Miami (MIA1)PeeringDB facility registryUSColocationOperational
Data Foundry Texas 1PeeringDB facility registryUSColocationOperational
Level(3) Austin (Kramer)PeeringDB facility registryUSColocationOperational
SBA Edge, LLCPeeringDB facility registryUSColocationOperational
Level(3) Chicago (Kingsbury)PeeringDB facility registryUSColocationOperational
Level(3) Miami (5th St)PeeringDB facility registryUSColocationOperational
Level(3) HerndonPeeringDB facility registryUSColocationOperational
Digital Realty New Jersey EWR10 (closed)PeeringDB facility registryUSColocationOperational
DataBank Dallas (DFW6)PeeringDB facility registryUSColocationOperational
Digital Realty AMS11 - AmsterdamPeeringDB facility registryNLColocationOperational
Digital Realty AMS16 - AmsterdamPeeringDB facility registryNLColocationOperational