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,3513,400 of 4,257Page 68 of 86
FacilityCountryTypeStatusPower (MW)
Eurofiber Datacenter Rotterdam 2PeeringDB facility registryNLColocationOperational
Flexential - Denver/Aurora (DEN03)PeeringDB facility registryUSColocationOperational
Flexential - Denver/Englewood (DEN11)PeeringDB facility registryUSColocationOperational
Flexential - Minneapolis/Chaska (MSP01)PeeringDB facility registryUSColocationOperational
Flexential - Las Vegas/Downtown (LAS03)PeeringDB facility registryUSColocationOperational
Flexential - Las Vegas/North (LAS04)PeeringDB facility registryUSColocationOperational
Flexential - Portland/Hillsboro (PDX01)PeeringDB facility registryUSColocationOperational
Flexential - Salt Lake City/Downtown (SLC04)PeeringDB facility registryUSColocationOperational
Flexential - Portland/Hillsboro 2 (PDX02)PeeringDB facility registryUSColocationOperational
Flexential - Denver/Centennial (DEN05)PeeringDB facility registryUSColocationOperational
InterDC DoetinchemPeeringDB facility registryNLColocationOperational
Flexential - Denver/Downtown (DEN02)PeeringDB facility registryUSColocationOperational
Flexential - Dallas/Richardson (RCH01)PeeringDB facility registryUSColocationOperational
Flexential - Salt Lake City/Cottonwood (SLC05)PeeringDB facility registryUSColocationOperational
Flexential - Salt Lake City/Millcreek (SLC10)PeeringDB facility registryUSColocationOperational
Sify Airoli-DC- MumbaiPeeringDB facility registryINColocationOperational
Sify Rabale - MumbaiPeeringDB facility registryINColocationOperational
Sify Vashi - MumbaiPeeringDB facility registryINColocationOperational
Sify ITPL - BangalorePeeringDB facility registryINColocationOperational
Sify Tidel-DC- ChennaiPeeringDB facility registryINColocationOperational
DataBank Dallas (DFW5)PeeringDB facility registryUSColocationOperational
Equinix ME4 - Melbourne, Derrimut (formerly Metronode Melbourne 2)PeeringDB facility registryAUColocationOperational
Equinix SY6 - Sydney (formerly Metronode Sydney 2)PeeringDB facility registryAUColocationOperational
Level(3) Atlanta (Courtland)PeeringDB facility registryUSColocationOperational
Nxtra Data Chennai DC 1PeeringDB facility registryINColocationOperational
Level(3) Chicago (Canal)PeeringDB facility registryUSColocationOperational
Nxtra Data Bangalore DC 1PeeringDB facility registryINColocationOperational
Cologix NNJ2PeeringDB facility registryUSColocationOperational
Cologix NNJ3PeeringDB facility registryUSColocationOperational
MedNautilus IstanbulPeeringDB facility registryTRColocationOperational
Equinix HE6 - Helsinki, SinimäkiPeeringDB facility registryFIColocationOperational
Cogent MontpellierPeeringDB facility registryFRColocationOperational
DRFortress HNLPeeringDB facility registryUSColocationOperational
MEGA Two (iAdvantage Hong Kong)PeeringDB facility registryHKColocationOperational
Redcentric London Data CentrePeeringDB facility registryGBColocationOperational
Digital Realty SJC (2805 Lafayette)PeeringDB facility registryUSColocationOperational
Digital Realty LAX (2260 E El Segundo)PeeringDB facility registryUSColocationOperational
Miran-2PeeringDB facility registryRUColocationOperational
ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)PeeringDB facility registryPLColocationOperational
Equinix DA2 - DallasPeeringDB facility registryUSColocationOperational
Equinix DA7 - DallasPeeringDB facility registryUSColocationOperational
Equinix TR7 - Toronto, Brampton (formerly Q9 Brampton 4/5)PeeringDB facility registryCAColocationOperational
Centersquare Northern Virginia (IAD1-A/F)PeeringDB facility registryUSColocationOperational
Centersquare New Jersey (EWR2)PeeringDB facility registryUSColocationOperational
Centersquare Los Angeles (LAX3)PeeringDB facility registryUSColocationOperational
Cogent ToulousePeeringDB facility registryFRColocationOperational
Cogent FrankfurtPeeringDB facility registryDEColocationOperational
Nusantara Data Center - JakartaPeeringDB facility registryIDColocationOperational
Nusantara Data Center - MedanPeeringDB facility registryIDColocationOperational
Nusantara Data Center - BatamPeeringDB facility registryIDColocationOperational