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,2513,300 of 4,257Page 66 of 86
FacilityCountryTypeStatusPower (MW)
Pixel Factory Data CenterPeeringDB facility registryUSColocationOperational
NTT DOCOMO BUSINESS OS3 - Osaka (Telepark Dojima Building 3)PeeringDB facility registryJPColocationOperational
EdgeConneX Salt Lake City (EDCSLC01)PeeringDB facility registryUSColocationOperational
Digital Realty Stockholm STO1-6PeeringDB facility registrySEColocationOperational
123.NET - DC1 - 24700 Northwestern Hwy.PeeringDB facility registryUSColocationOperational
H5 Data Centers TampaPeeringDB facility registryUSColocationOperational
H5 Data Centers Buffalo IIIPeeringDB facility registryUSColocationOperational
Level(3) WeehawkenPeeringDB facility registryUSColocationOperational
Cirion Santiago de Chile - SAN1PeeringDB facility registryCLColocationOperational
TierPoint Hawthorne (fka Xand)PeeringDB facility registryUSColocationOperational
4 Data CenterPeeringDB facility registryPLColocationOperational
Data Vault Auckland Data CenterPeeringDB facility registryNZColocationOperational
Data Vault Hamilton Data CenterPeeringDB facility registryNZColocationOperational
Netrality Philadelphia - 401 N BroadPeeringDB facility registryUSColocationOperational
H5 Data Centers Philadelphia (PA01)PeeringDB facility registryUSColocationOperational
Pacheco Datacenter EZE1 Argentina Buenos AiresPeeringDB facility registryARColocationOperational
Spaanse Kubus RotterdamPeeringDB facility registryNLColocationOperational
Computer Concepts Limited (CCL) Christchurch DCPeeringDB facility registryNZColocationOperational
Spark Wellington Central (Featherston)PeeringDB facility registryNZColocationOperational
Teleporto Rio de JaneiroPeeringDB facility registryBRColocationOperational
Digital Realty Dublin DUB13-14PeeringDB facility registryIEColocationOperational
CE Colo PraguePeeringDB facility registryCZColocationOperational
Digital Fortress (TUK)PeeringDB facility registryUSColocationOperational
Albany Data CentrePeeringDB facility registryNZColocationOperational
DC Tower Zizkov CRaPeeringDB facility registryCZColocationOperational
Slovak University of TechnologyPeeringDB facility registrySKColocationOperational
TierPoint Omaha - MidlandsPeeringDB facility registryUSColocationOperational
Flexential - Dallas/Downtown (DAL01)PeeringDB facility registryUSColocationOperational
GTS Telehouse PraguePeeringDB facility registryCZColocationOperational
Equinix DB4 - Dublin, BallycoolinPeeringDB facility registryIEColocationOperational
NTT DOCOMO BUSINESS OS1 - Osaka (Telepark Dojima Building 1)PeeringDB facility registryJPColocationOperational
xneelo JNB1 (Formerly Hetzner SA)PeeringDB facility registryZAColocationOperational
Cabase BUEPeeringDB facility registryARColocationOperational
Corporation-ParkPeeringDB facility registryHKColocationOperational
Arelion Dusseldorf DDF/BPeeringDB facility registryDEColocationOperational
CyrusOne NC-1PeeringDB facility registryUSColocationOperational
Psychz Networks LAX1PeeringDB facility registryUSColocationOperational
M247 Europe BucharestPeeringDB facility registryROColocationOperational
Markley Group One Summer Street BostonPeeringDB facility registryUSColocationOperational
Telco CenterPeeringDB facility registryFRColocationOperational
Pulsant Reading SE-3 (South)PeeringDB facility registryGBColocationOperational
DataSpace MoscowPeeringDB facility registryRUColocationOperational
DataBank Denver (DEN2)PeeringDB facility registryUSColocationOperational
BCE Colocation LuxembourgPeeringDB facility registryLUColocationOperational
Techno-ZPeeringDB facility registryATColocationOperational
Equinix TR2 - TorontoPeeringDB facility registryCAColocationOperational
Telia Telehouse CopenhagenPeeringDB facility registryDKColocationOperational
PIX Samm GoiâniaPeeringDB facility registryBRColocationOperational
DatasferaPeeringDB facility registryUAColocationOperational
IIX-RiauPeeringDB facility registryIDColocationOperational