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) |
|---|---|---|---|---|
| Amazon IAD120IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD125IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD130IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD144IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD150IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD163IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD51IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD62IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD73IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD76IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon IAD78IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon New Albany: Jug and Beach RoadIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon PDX2IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon PDX63IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon PDX80IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon PDX91IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon Web Services Building CIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon Web Services CMH50IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Amazon Web Services us-west-2IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| amnet Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| AngelTrax Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Apple Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Applied Digital / Ellendale Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Ark Duluth Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| AWS IAD105IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Baltimore Technology ParkIM3 / PNNL data-center corpus | US | Other | Operational | — |
| Bank of America Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Barclays DatacenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| BB&T Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Bloomberg Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| BT Radianz: 492 River RoadIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centeris SH2 Build-to-SuitIM3 / PNNL data-center corpus | US | Other | Operational | — |
| Centersquare Atlanta ATL1IM3 / PNNL data-center corpus | US | Other | Operational | — |
| Centersquare Elk Grove Village Data Center Campus ORD2IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centersquare IAD1-BIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centersquare IAD2-AIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centersquare IAD3IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centersquare Lisle ORD4 Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centersquare Lynnwood SE1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Centersquare: Phoenix - (PHX1 - Mesa)IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Lumen Technologies (formerly CenturyLink)IM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Charles Schwab Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Cherokee Data CenterIM3 / PNNL data-center corpus | US | Hyperscale DC | Operational | — |
| Choctaw Nation of Oklahoma Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cisco AllenIM3 / PNNL data-center corpus | US | Other | Operational | — |
| CloudHQ LC1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| CloudHQ MCC1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cogent Data CenterIM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| Cologix Jacksonville JAX1IM3 / PNNL data-center corpus | US | Colocation | Operational | — |
| ColovoreIM3 / PNNL data-center corpus | US | Other | Operational | — |