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,6013,650 of 4,257Page 73 of 86
FacilityCountryTypeStatusPower (MW)
Sba Edge Sao PauloPeeringDB facility registryBRColocationOperational
MEGA Plus (iAdvantage Hong Kong)PeeringDB facility registryHKColocationOperational
Omega Telecom KyivPeeringDB facility registryUAColocationOperational
Datacenter SYTPeeringDB facility registryARColocationOperational
BIT-2PeeringDB facility registryNLColocationOperational
Sabey Intergate East Building 4PeeringDB facility registryUSColocationOperational
Netmagic Chandivali - MUM-DC05PeeringDB facility registryINColocationOperational
Innovation Place - 121RDPeeringDB facility registryCAColocationOperational
TTC TELEPORT DC1PeeringDB facility registryCZColocationOperational
Equinix SY7 - Sydney (formerly Metronode Illawara 1)PeeringDB facility registryAUColocationOperational
QTS Groningen (GRO1)PeeringDB facility registryNLColocationOperational
NorthC HamburgPeeringDB facility registryDEColocationOperational
NorthC AlmerePeeringDB facility registryNLColocationOperational
DataBank Dallas (DFW1)PeeringDB facility registryUSColocationOperational
DataBank Dallas (DFW2)PeeringDB facility registryUSColocationOperational
DataBank Dallas (DFW3)PeeringDB facility registryUSColocationOperational
DataBank Minneapolis (MSP1)PeeringDB facility registryUSColocationOperational
DataBank Minneapolis (MSP2)PeeringDB facility registryUSColocationOperational
DataBank Kansas City (MCI2)PeeringDB facility registryUSColocationOperational
DataBank Cleveland (CLE1)PeeringDB facility registryUSColocationOperational
DataBank Pittsburgh (PIT1)PeeringDB facility registryUSColocationOperational
DataBank Salt Lake City (SLC1)PeeringDB facility registryUSColocationOperational
DataBank Salt Lake City (SLC2)PeeringDB facility registryUSColocationOperational
DataBank Salt Lake City (SLC3)PeeringDB facility registryUSColocationOperational
Digital Realty London LHR19PeeringDB facility registryGBColocationOperational
Level(3) OaklandPeeringDB facility registryUSColocationOperational
Equinix SP3 - São PauloPeeringDB facility registryBRColocationOperational
Gothnet DC MarieholmPeeringDB facility registrySEColocationOperational
Netrality Kansas City - 1102 GrandPeeringDB facility registryUSColocationOperational
Equinix SV3 - Silicon Valley, San JosePeeringDB facility registryUSColocationOperational
Telehouse - London (Docklands North Two)PeeringDB facility registryGBColocationOperational
Telehouse - SingaporePeeringDB facility registrySGColocationOperational
Telehouse - HanoiPeeringDB facility registryVNColocationOperational
Equinix SV2 - Silicon Valley, Santa ClaraPeeringDB facility registryUSColocationOperational
TierPoint DallasPeeringDB facility registryUSColocationOperational
TierPoint Dallas2 - AllenPeeringDB facility registryUSColocationOperational
TierPoint JacksonvillePeeringDB facility registryUSColocationOperational
TierPoint NashvillePeeringDB facility registryUSColocationOperational
NXDATA-1 Bucharest (BUH1)PeeringDB facility registryROColocationOperational
NTT Rhein-Ruhr 1 Data Center (CGN1)PeeringDB facility registryDEColocationOperational
CoreSite - Chicago (CH1)PeeringDB facility registryUSColocationOperational
Databarn AmsterdamPeeringDB facility registryNLColocationOperational
Rack Centre LagosPeeringDB facility registryNGColocationOperational
KIO México 1 (MEX1)PeeringDB facility registryMXColocationOperational
KIO México 2 (MEX2)PeeringDB facility registryMXColocationOperational
Previder PDC1PeeringDB facility registryNLColocationOperational
noris network datacenter.de NBG3 / NBG4PeeringDB facility registryDEColocationOperational
Equinix DE1 - DenverPeeringDB facility registryUSColocationOperational
CarrierColo Berlin Luetzow (I/P/B/ site B)PeeringDB facility registryDEColocationOperational
LightBound IND1PeeringDB facility registryUSColocationOperational