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 25 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,5013,550 of 4,257Page 71 of 86
FacilityCountryTypeStatusPower (MW)
DATA4 Paris Marcoussis - PAR1PeeringDB facility registryFRColocationOperational
CoreSite - Santa Clara (SV7)PeeringDB facility registryUSColocationOperational
DATA4 Milan-Cornaredo - MIL1PeeringDB facility registryITColocationOperational
QTS Sacramento (SAC1)PeeringDB facility registryUSColocationOperational
colozueri.ch ZurichPeeringDB facility registryCHColocationOperational
QTS Princeton (PJC1)PeeringDB facility registryUSColocationOperational
QTS Chicago (CHI1)PeeringDB facility registryUSColocationOperational
QTS Irving - Dallas (DFW1)PeeringDB facility registryUSColocationOperational
QTS Overland Park (OVP1)PeeringDB facility registryUSColocationOperational
TurkNet Iletisim Hizmetleri A.SPeeringDB facility registryTRColocationOperational
Naquadria Datacenter PiacenzaPeeringDB facility registryITColocationOperational
Digital Realty Singapore SIN11PeeringDB facility registrySGColocationOperational
Netrality Chicago - 717 S WellsPeeringDB facility registryUSColocationOperational
Digital Realty London LHR18PeeringDB facility registryGBColocationOperational
Telehouse - London (Docklands North)PeeringDB facility registryGBColocationOperational
Biznet JakartaPeeringDB facility registryIDColocationOperational
Vaultica Data Centers | OSL01PeeringDB facility registryNOColocationOperational
Level(3) TorontoPeeringDB facility registryCAColocationOperational
Level(3) New YorkPeeringDB facility registryUSColocationOperational
Crown Castle Philadelphia (401 N Broad)PeeringDB facility registryUSColocationOperational
Linxdatacenter (Moscow)PeeringDB facility registryRUColocationOperational
Digital Realty Dublin DUB3PeeringDB facility registryIEColocationOperational
Quicktel Sp. z o.o.PeeringDB facility registryPLColocationOperational
Digital Realty London LHR17PeeringDB facility registryGBColocationOperational
165 Halsey Meet-Me RoomPeeringDB facility registryUSColocationOperational
Equinix DU1 - DusseldorfPeeringDB facility registryDEColocationOperational
2Connect DC10PeeringDB facility registryHUColocationOperational
C21PeeringDB facility registryITColocationOperational
London Hosting CentrePeeringDB facility registryGBColocationOperational
Level(3) London (Goswell Road)PeeringDB facility registryGBColocationOperational
MK Netzdienste DatacenterPeeringDB facility registryDEColocationOperational
Equinix NY2/NY4/NY5/NY6 - New York, SecaucusPeeringDB facility registryUSColocationOperational
NTT Munich 2 Data Center (MUC2)PeeringDB facility registryDEColocationOperational
OADC, UmhlangaPeeringDB facility registryZAColocationOperational
CoreSite - Los Angeles (LA2)PeeringDB facility registryUSColocationOperational
DataCentre220PeeringDB facility registryNZColocationOperational
CoreSite - Orlando (OR1)PeeringDB facility registryUSColocationOperational
NewTelco KievPeeringDB facility registryUAColocationOperational
TierPoint Lehigh ValleyPeeringDB facility registryUSColocationOperational
WIIT Datacenter DUS5PeeringDB facility registryDEColocationOperational
T5@DallasPeeringDB facility registryUSColocationOperational
Network 222PeeringDB facility registryUSColocationOperational
Digital Realty ATL14 - AtlantaPeeringDB facility registryUSColocationOperational
Iron Mountain Data Center - Amsterdam (AMS-1)PeeringDB facility registryNLColocationOperational
Equinix AM1/AM2 - Amsterdam, LuttenbergwegPeeringDB facility registryNLColocationOperational
Equinix ZW1 - ZwollePeeringDB facility registryNLColocationOperational
Fibre CentrePeeringDB facility registryCAColocationOperational
BR.Digital Porto Alegre (PAE1)PeeringDB facility registryBRColocationOperational
noris network datacenter.de MUC5PeeringDB facility registryDEColocationOperational
Equinix NY9 - New York, 111 8th AvenuePeeringDB facility registryUSColocationOperational