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,4513,500 of 4,257Page 70 of 86
FacilityCountryTypeStatusPower (MW)
Digital Realty EWR (3 Corporate Pl)PeeringDB facility registryUSColocationOperational
DataBank Irvine (SNA1)PeeringDB facility registryUSColocationOperational
Evocative EWR1PeeringDB facility registryUSColocationOperational
TierPoint Chicago - WestPeeringDB facility registryUSColocationOperational
Evocative SEA1PeeringDB facility registryUSColocationOperational
BIX Building (Victor Hugo street)PeeringDB facility registryHUColocationOperational
Dataplex BudapestPeeringDB facility registryHUColocationOperational
TierPoint PhiladelphiaPeeringDB facility registryUSColocationOperational
TierPoint Chicago - PolkPeeringDB facility registryUSColocationOperational
RETNNet OV DCPeeringDB facility registryRUColocationOperational
China Unicom (Hong Kong) Global CenterPeeringDB facility registryHKColocationOperational
Equinix PA2 - Paris, Saint-DenisPeeringDB facility registryFRColocationOperational
Telehouse – OSAKA 1&2PeeringDB facility registryJPColocationOperational
H5 Data Centers DenverPeeringDB facility registryUSColocationOperational
H5 Data Centers PhoenixPeeringDB facility registryUSColocationOperational
H5 Data Centers SeattlePeeringDB facility registryUSColocationOperational
H5 Data Centers AtlantaPeeringDB facility registryUSColocationOperational
nLighten Madrid MAD1PeeringDB facility registryESColocationOperational
DataLine Moscow DC OSTPeeringDB facility registryRUColocationOperational
DataLine Moscow DC NORDPeeringDB facility registryRUColocationOperational
Nessus NDC2PeeringDB facility registryATColocationOperational
Level(3) Nashville (Sidco Drive)PeeringDB facility registryUSColocationOperational
Digital Realty SJC (1100 Space Park)PeeringDB facility registryUSColocationOperational
Level(3) CincinnatiPeeringDB facility registryUSColocationOperational
Equinix LD10 - London, SloughPeeringDB facility registryGBColocationOperational
Equinix SK3 - Stockholm, SpångaPeeringDB facility registrySEColocationOperational
Orange Business - La Fabrique [Grenoble]PeeringDB facility registryFRColocationOperational
Metrotel - CPS ComunicacionesPeeringDB facility registryARColocationOperational
Elisa Tampere NalkalaPeeringDB facility registryFIColocationOperational
Hetzner Online FSN1 (Falkenstein)PeeringDB facility registryDEColocationOperational
Hetzner Online NBG1 (Nuremberg)PeeringDB facility registryDEColocationOperational
Equinix CL3 - Calgary (formerly Q9 Calgary Three)PeeringDB facility registryCAColocationOperational
eStruxture CAL-1PeeringDB facility registryCAColocationOperational
Digital Realty HOU (12001 North Freeway)PeeringDB facility registryUSColocationOperational
Evolink Data Center Sofia 2PeeringDB facility registryBGColocationOperational
Evolink Data Center Sofia 1PeeringDB facility registryBGColocationOperational
Digital Realty Portland - PDX10PeeringDB facility registryUSColocationOperational
NorthC BerlinPeeringDB facility registryDEColocationOperational
Cologix MIN3PeeringDB facility registryUSColocationOperational
Cologix COL3PeeringDB facility registryUSColocationOperational
Equinix SY4 - SydneyPeeringDB facility registryAUColocationOperational
Netrality St. Louis - 900 WalnutPeeringDB facility registryUSColocationOperational
Equinix LA3/LA4 - Los Angeles, El SegundoPeeringDB facility registryUSColocationOperational
Equinix TY5 - TokyoPeeringDB facility registryJPColocationOperational
Equinix TY6 - TokyoPeeringDB facility registryJPColocationOperational
Equinix TY7 - TokyoPeeringDB facility registryJPColocationOperational
Equinix TY8 - TokyoPeeringDB facility registryJPColocationOperational
Equinix TY9 - TokyoPeeringDB facility registryJPColocationOperational
Equinix TY10 - TokyoPeeringDB facility registryJPColocationOperational
Pulsant Maidenhead SE-2PeeringDB facility registryGBColocationOperational