U.S. overview · licensed discovery layer
The U.S. picture, with the source behind each number.
Compare one consistently processed directory edition across every state. Every number links back to the underlying rows; independently reviewed evidence remains a separate layer.
Reported lifecycle
What the source calls each row.
These are source labels, not DataCenterData findings. Open any segment to inspect its underlying rows.
Source-row concentrations
Three useful ways into the directory.
These rank rows in this edition—not true facilities, market size, electricity use or capacity. Ties break alphabetically and every result opens its evidence layer.
States
- 1Virginia139 licensed rows
- 2Texas112 licensed rows
- 3California95 licensed rows
- 4Ohio90 licensed rows
- 5Illinois66 licensed rows
- 6Georgia58 licensed rows
- 7Pennsylvania51 licensed rows
- 8Oklahoma50 licensed rows
City/state labels
- 1Ashburn, Virginia29 licensed rows
- 2Santa Clara, California27 licensed rows
- 3Hillsboro, Oregon23 licensed rows
- 4Tulsa, Oklahoma16 licensed rows
- 5Elk Grove Village, Illinois15 licensed rows
- 6New Albany, Ohio13 licensed rows
- 6Sterling, Virginia13 licensed rows
- 8Las Vegas, Nevada12 licensed rows
Exact operator labels
- 1Amazon Web Services56 licensed rows
- 1Digital Realty56 licensed rows
- 3Google51 licensed rows
- 4Microsoft47 licensed rows
- 5Flexential46 licensed rows
- 6QTS Data Centers36 licensed rows
- 7Equinix31 licensed rows
- 8DataBank28 licensed rows
Published MW values mix IT load, facility load, design capacity and utility commitments. Unknown is not zero. A clean-looking leaderboard would be mathematically precise and substantively wrong.
Adapted from Compute Atlas by Edward Kubiak, edition 1.33.0, under CC BY 4.0. Source data updated through 18 September 2026. DataCenterData grouped the published rows by state, locality, exact operator label and reported lifecycle.