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 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.
- Epoch AI Frontier Data Centers7064 measured91.4%
- Epoch AI GPU Clusters437397 measured90.8%
- PeeringDB facility registry1,56963 measured4.0%
- IM3 / PNNL data-center corpus3912 measured0.5%
- OpenStreetMap (tagged data centers)1,1731 measured0.1%
- OpenStreetMap2310 measured0.0%
- Microsoft Azure region documentation560 measured0.0%
- Oracle Cloud region documentation450 measured0.0%
- 43 smaller catalogues285183 measured64.2%
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.
| Facility | Country | Type | Status | Power (MW) |
|---|---|---|---|---|
| AWS Asia Pacific (Hong Kong)AWS region documentation | HK | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Taipei)AWS region documentation | TW | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Tokyo)AWS region documentation | JP | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Seoul)AWS region documentation | KR | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Osaka)AWS region documentation | JP | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Mumbai)AWS region documentation | IN | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Hyderabad)AWS region documentation | IN | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Singapore)AWS region documentation | SG | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Sydney)AWS region documentation | AU | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Jakarta)AWS region documentation | ID | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Melbourne)AWS region documentation | AU | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Malaysia)AWS region documentation | MY | Hyperscale DC | Operational | — |
| AWS Asia Pacific (New Zealand)AWS region documentation | NZ | Hyperscale DC | Operational | — |
| AWS Asia Pacific (Thailand)AWS region documentation | TH | Hyperscale DC | Operational | — |
| AWS Canada (Central)AWS region documentation | CA | Hyperscale DC | Operational | — |
| AWS Canada West (Calgary)AWS region documentation | CA | Hyperscale DC | Operational | — |
| AWS Europe (Frankfurt)AWS region documentation | DE | Hyperscale DC | Operational | — |
| AWS Europe (Zurich)AWS region documentation | CH | Hyperscale DC | Operational | — |
| AWS Europe (Stockholm)AWS region documentation | SE | Hyperscale DC | Operational | — |
| AWS Europe (Milan)AWS region documentation | IT | Hyperscale DC | Operational | — |
| AWS Europe (Spain)AWS region documentation | ES | Hyperscale DC | Operational | — |
| AWS Europe (Ireland)AWS region documentation | IE | Hyperscale DC | Operational | — |
| AWS Europe (London)AWS region documentation | GB | Hyperscale DC | Operational | — |
| AWS Europe (Paris)AWS region documentation | FR | Hyperscale DC | Operational | — |
| AWS Israel (Tel Aviv)AWS region documentation | IL | Hyperscale DC | Operational | — |
| AWS Middle East (UAE)AWS region documentation | AE | Hyperscale DC | Operational | — |
| AWS Middle East (Bahrain)AWS region documentation | BH | Hyperscale DC | Operational | — |
| AWS Mexico (Central)AWS region documentation | MX | Hyperscale DC | Operational | — |
| AWS South America (São Paulo)AWS region documentation | BR | Hyperscale DC | Operational | — |
| AWS US East (N. Virginia)AWS region documentation | US | Hyperscale DC | Operational | — |
| AWS US East (Ohio)AWS region documentation | US | Hyperscale DC | Operational | — |
| AWS US West (N. California)AWS region documentation | US | Hyperscale DC | Operational | — |
| AWS US West (Oregon)AWS region documentation | US | Hyperscale DC | Operational | — |
| AZURE Australia CentralMicrosoft Azure region documentation | AU | Hyperscale DC | Operational | — |
| AZURE Australia Central 2Microsoft Azure region documentation | AU | Hyperscale DC | Operational | — |
| AZURE Australia EastMicrosoft Azure region documentation | AU | Hyperscale DC | Operational | — |
| AZURE Australia SoutheastMicrosoft Azure region documentation | AU | Hyperscale DC | Operational | — |
| AZURE Austria EastMicrosoft Azure region documentation | AT | Hyperscale DC | Operational | — |
| AZURE Belgium CentralMicrosoft Azure region documentation | BE | Hyperscale DC | Operational | — |
| AZURE Brazil SouthMicrosoft Azure region documentation | BR | Hyperscale DC | Operational | — |
| AZURE Brazil SoutheastMicrosoft Azure region documentation | BR | Hyperscale DC | Operational | — |
| AZURE Canada CentralMicrosoft Azure region documentation | CA | Hyperscale DC | Operational | — |
| AZURE Canada EastMicrosoft Azure region documentation | CA | Hyperscale DC | Operational | — |
| AZURE Central IndiaMicrosoft Azure region documentation | IN | Hyperscale DC | Operational | — |
| AZURE Central USMicrosoft Azure region documentation | US | Hyperscale DC | Operational | — |
| AZURE Chile CentralMicrosoft Azure region documentation | CL | Hyperscale DC | Operational | — |
| AZURE Denmark EastMicrosoft Azure region documentation | DK | Hyperscale DC | Operational | — |
| AZURE East AsiaMicrosoft Azure region documentation | HK | Hyperscale DC | Operational | — |
| AZURE East USMicrosoft Azure region documentation | US | Hyperscale DC | Operational | — |
| AZURE East US 2Microsoft Azure region documentation | US | Hyperscale DC | Operational | — |