National directory · 50 states · source edition 1.34.1

Browse data centers by state.

Start with 1,822 licensed leads (source listings to investigate, not necessarily distinct data centers), then open the separate reviewed-evidence layer when you need to see what public sources support.

Search facilities, cities and operators →

State and local policy tracker — sourced pauses, requirements, and incentives. It does not score a state as allowed or prohibited, and it is not part of the directory counts.

Show licensed discovery activity map

Licensed discovery activity by state.

1,822 licensed leads995 city/state labels778 eligible organization labels50 state pages

Licensed counts are broad discovery rows, not independently verified facilities or a census. Jump to the state finder ↓

Browse all 50 states.

How to read these cards: Licensed directory leads appear first; each lead is a source listing to investigate, not necessarily one distinct data center. “Map listings” counts what the interactive map lists for the state across the licensed, operator and DataCenterData layers, and how many of them have a map point of their own. Independently reviewed project/campus and facility/building counts remain separate. None of these counts are added together.

Compare independently reviewed research coverage
We do not publish a national total. Published rows use different record units and evidence layers. Indiana and Ohio, for example, separate large-project or campus records from physical facilities because the inventories overlap. Adding incompatible rows would create a precise-looking but misleading U.S. total.

See how the deepest state indexes are compared →

History is data—not another facility

The first cross-state lifecycle register preserves nine dated acquisitions, energizations, groundbreakings, approvals and expirations. It shows why names and statuses cannot simply be overwritten: DataBank’s former 365 Data Centers operator, STACK’s acquired New Albany campus, and Hammond’s expired expansion all belong to stable entities. Open the lifecycle-event JSON →

What “every” can honestly mean

We can target every evidence-identified facility, project and historical lifecycle record after a dated audit of operators, government records, dockets, permits, tax records, archives and directory leads. We cannot prove that an undisclosed private server room does not exist. Completeness is therefore a published audit boundary—not a marketing adjective.

Open data: U.S. coverage JSON · common state-data standard. Every state page shows the draft source-family audit and remaining gaps. Research drafts do not add records to published counts.