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.

501550 of 4,257Page 11 of 86
FacilityCountryTypeStatusPower (MW)
AZURE France CentralMicrosoft Azure region documentationFRHyperscale DCOperational
AZURE France SouthMicrosoft Azure region documentationFRHyperscale DCOperational
AZURE Germany NorthMicrosoft Azure region documentationDEHyperscale DCOperational
AZURE Germany West CentralMicrosoft Azure region documentationDEHyperscale DCOperational
AZURE Indonesia CentralMicrosoft Azure region documentationIDHyperscale DCOperational
AZURE Israel CentralMicrosoft Azure region documentationILHyperscale DCOperational
AZURE Italy NorthMicrosoft Azure region documentationITHyperscale DCOperational
AZURE Japan EastMicrosoft Azure region documentationJPHyperscale DCOperational
AZURE Japan WestMicrosoft Azure region documentationJPHyperscale DCOperational
AZURE Korea CentralMicrosoft Azure region documentationKRHyperscale DCOperational
AZURE Korea SouthMicrosoft Azure region documentationKRHyperscale DCOperational
AZURE Malaysia WestMicrosoft Azure region documentationMYHyperscale DCOperational
AZURE Mexico CentralMicrosoft Azure region documentationMXHyperscale DCOperational
AZURE New Zealand NorthMicrosoft Azure region documentationNZHyperscale DCOperational
AZURE North Central USMicrosoft Azure region documentationUSHyperscale DCOperational
AZURE North EuropeMicrosoft Azure region documentationIEHyperscale DCOperational
AZURE Norway EastMicrosoft Azure region documentationNOHyperscale DCOperational
AZURE Norway WestMicrosoft Azure region documentationNOHyperscale DCOperational
AZURE Poland CentralMicrosoft Azure region documentationPLHyperscale DCOperational
AZURE Qatar CentralMicrosoft Azure region documentationQAHyperscale DCOperational
AZURE South Africa NorthMicrosoft Azure region documentationZAHyperscale DCOperational
AZURE South Africa WestMicrosoft Azure region documentationZAHyperscale DCOperational
AZURE South Central USMicrosoft Azure region documentationUSHyperscale DCOperational
AZURE Southeast AsiaMicrosoft Azure region documentationSGHyperscale DCOperational
AZURE South IndiaMicrosoft Azure region documentationINHyperscale DCOperational
AZURE Spain CentralMicrosoft Azure region documentationESHyperscale DCOperational
AZURE Sweden CentralMicrosoft Azure region documentationSEHyperscale DCOperational
AZURE Switzerland NorthMicrosoft Azure region documentationCHHyperscale DCOperational
AZURE Switzerland WestMicrosoft Azure region documentationCHHyperscale DCOperational
AZURE UAE CentralMicrosoft Azure region documentationAEHyperscale DCOperational
AZURE UAE NorthMicrosoft Azure region documentationAEHyperscale DCOperational
AZURE UK SouthMicrosoft Azure region documentationGBHyperscale DCOperational
AZURE UK WestMicrosoft Azure region documentationGBHyperscale DCOperational
AZURE West Central USMicrosoft Azure region documentationUSHyperscale DCOperational
AZURE West EuropeMicrosoft Azure region documentationNLHyperscale DCOperational
AZURE West IndiaMicrosoft Azure region documentationINHyperscale DCOperational
AZURE West USMicrosoft Azure region documentationUSHyperscale DCOperational
AZURE West US 2Microsoft Azure region documentationUSHyperscale DCOperational
AZURE West US 3Microsoft Azure region documentationUSHyperscale DCOperational
GCP Africa South 1Google Cloud region documentationZAHyperscale DCOperational
GCP Asia East 1Google Cloud region documentationTWHyperscale DCOperational
GCP Asia East 2Google Cloud region documentationHKHyperscale DCOperational
GCP Asia Northeast 1Google Cloud region documentationJPHyperscale DCOperational
GCP Asia Northeast 2Google Cloud region documentationJPHyperscale DCOperational
GCP Asia Northeast 3Google Cloud region documentationKRHyperscale DCOperational
GCP Asia South 1Google Cloud region documentationINHyperscale DCOperational
GCP Asia South 2Google Cloud region documentationINHyperscale DCOperational
GCP Asia Southeast 1Google Cloud region documentationSGHyperscale DCOperational
GCP Asia Southeast 2Google Cloud region documentationIDHyperscale DCOperational
GCP Asia Southeast 3Google Cloud region documentationTHHyperscale DCOperational