Reuse: the facility downloads below are free to download and reuse under the per-field terms stated with them; reviewed project and claim records are reference only for now.
How whole reviewed records are cleared for reuse
Only the field-level records marked rights-cleared in the rights file receive the published CC BY 4.0 grant. Linked source documents and reference-only records retain their own rights. No record is currently in the licensed-core subset.
Free facility data
Free to download, with per-field reuse terms. DataCenterData fields are licensed CC BY 4.0: credit DataCenterData and link to datacenterdata.com/data/. Fields that come from Compute Atlas keep Compute Atlas’s CC BY 4.0 license and its credit. U.S. government work fields carry no copyright. Values the facility register marks reference only are left out of the files, and each row’s withheld-field list names the fields they belong to; in a list such as operators only the withheld entries are left out, so other entries can remain. Exact column names are in the data dictionary.
Every facility in the register — 2,650 register records — in three formats with the same rows:
- datacenters.csv — spreadsheet, one row per facility (2.4 MB)
- datacenters.geojson — map layer; facilities without a published coordinate have no geometry (5.6 MB)
- datacenters.json — full records with sources, statuses by layer and stated capacity (5.4 MB)
- datacenters-dictionary.json — data dictionary: every field, its reuse terms, attribution, counts and these checksums
File checksums (SHA-256)
- datacenters.csv
- datacenters.geojson
- datacenters.json
Suggested citation: DataCenterData. U.S. data center facility register, free download (data as of 2026-10-18). https://datacenterdata.com/data/. DataCenterData fields CC BY 4.0; Compute Atlas fields CC BY 4.0 (Compute Atlas by Edward Kubiak).
Which fields are CC BY
- DataCenterData fields, CC BY 4.0, every row: dcd_id, public_id, site_class, site_class_label, evidence_level, evidence_tier, record_unit, county_fips, cbsa_code, cbsa_name, coordinate_precision, coordinate_source, location_precision, source_families, first_listed, latest_source_date, field_origins, each row’s Compute Atlas field list and withheld-field list, plus any other field whose
field_originsvalue isdcd_original. - Compute Atlas fields, CC BY 4.0, credit Compute Atlas: the fields named in each row’s Compute Atlas field list (1,728 rows).
- U.S. government works: fields whose
field_originsvalue ispublic_record(U.S. EPA Facility Registry Service fields and Census Geocoder points). - Links only:
source_urlsandsite_class_sources; the linked documents keep their own rights.
Rows carrying each source-dependent field, by origin, and rows where it is withheld:
| Field | DataCenterData | Compute Atlas | U.S. government | Withheld |
|---|---|---|---|---|
| Name | 0 | 1,689 | 127 | 834 |
| Stated operators | 0 | 1,728 | 61 | 1,030 |
| operator_families | 0 | 1,728 | 61 | 663 |
| Operator of record | 0 | 0 | 0 | 39 |
| Other names | 0 | 33 | 60 | 516 |
| Street | 0 | 497 | 187 | 726 |
| City | 0 | 1,525 | 187 | 840 |
| County | 0 | 1,687 | 0 | 120 |
| State | 0 | 1,596 | 187 | 867 |
| ZIP code | 0 | 354 | 191 | 583 |
| Coordinates | 0 | 142 | 417 | 51 |
| DataCenterData lifecycle status | 0 | 0 | 0 | 213 |
| Provider-reported status | 0 | 1,728 | 0 | 0 |
| Operator-stated status | 0 | 0 | 0 | 34 |
| Stated capacity and area | 0 | 1,087 | 0 | 561 |
Labels and evidence
- Crypto-mining and AI compute campuses confirmed from permitted primary sources are included and labelled in
site_class, so you can keep or drop them; none is labelled yet, so every row is unclassified (not evidence either way). evidence_levelgives the register’s evidence tier a plain name:dcd_reviewed(a DataCenterData reviewed record in the verified inventory layer),multiple_source_families(two or more source families joined; their independence is not tested), single-family records andthird_party_listing_onlydiscovery listings, so a lead is not mistaken for a reviewed site.county_fipsis given only where the exported county matches the pinned Census files (1,504 rows). Coordinates appear only where the facility page publishes one (559 rows).
What is not included
- Every value the facility register marks reference only: the operator-listed layer (names, addresses, stated operators, statuses and figures captured from operators’ pages) and DataCenterData reviewed-record fields that have not been cleared field by field. Each row’s withheld-field list names the fields they belong to (in a list such as operators, only those entries are left out); the facility page still shows them with their terms. One exception is visible: dcd_url is the address of the facility’s public DataCenterData page, built from its published page title, so for a row whose name is withheld that address can still contain a form of the name. It is a link, not a licensed value.
- Verbatim quotations from operator pages and other sources (held in capture records; never republished).
- Linked permits, filings, operator pages and other documents (linked, not republished; they keep their own rights).
- Selected factual fields cited to state and local agency records (shown on facility pages with their citation; not relicensed).
- From a Compute Atlas row that cites OpenStreetMap: its coordinate, street address and postal code. Other Compute Atlas values (for example names, cities and capacity text) pass through under Compute Atlas’s CC BY 4.0 terms; DataCenterData has not traced whether Compute Atlas drew any of them from OpenStreetMap or its other inputs. No value from DataCenterData’s own private OpenStreetMap or PNNL/IM3 lead lists is included.
- Coordinates the site itself does not publish (below street precision or withheld after review).
- Contact routes, private captures and internal review notes.
Compute Atlas credit
Values marked Compute Atlas (listed in each row’s Compute Atlas field list) carry this credit: “Compute-infrastructure data from Compute Atlas by Edward Kubiak”, licensed CC BY 4.0. Changes made: Filtered to data-center records in the 50 U.S. states; selected fields normalized for search and display; DataCenterData directory IDs added. In this download: values organized by DataCenterData facility id; coordinates, street addresses and postal codes from rows that cite OpenStreetMap removed. Keep this credit when you reuse those values.
Dates and updates
Data as of 18 October 2026: the newest input date of the facility register, not the build time and not a fresh check of every facility. The files are regenerated with every site release; changes are listed on Changes and in the Atom feed. Counts are register records (campuses, buildings, suites and unresolved presences), not unique sites and not a census.
Dates in downloads: the explained generated_at field in static JSON describes a collection date, not the latest site release or a fresh check of every record. Read the date definitions.
How much operator detail is recorded?
Operator pages captured through 14 October 2026. Each field counts a source listing once, even when it has several values. Company-wide statements are separate and do not establish a facility's services, certification or availability. These overlapping layers are not a count of unique facilities.
Listing-specific and no-value counts partition each layer. Company context, holds and expired statements are additional flags and must not be added to those totals. No value does not mean absent, researched or applicable. This table covers operator-source detail, not every field or evidence layer on the site; it does not measure national discovery or complete profiles.
Operator listings: 661 source listings · field-by-field table
| Field | Listing-specific | Company context | No listing-specific value | Held or conflicting | Not stated in saved source | Expired |
|---|---|---|---|---|---|---|
| Operator-stated status | 43 | 0 | 618 | 0 | 0 | 0 |
| Cooling redundancy | 149 | 0 | 512 | 57 | 28 | 0 |
| UPS redundancy | 86 | 0 | 575 | 81 | 31 | 0 |
| Backup generator redundancy | 32 | 0 | 629 | 44 | 45 | 0 |
| Tier design rating | 27 | 0 | 634 | 66 | 34 | 0 |
| Critical IT capacity | 67 | 0 | 594 | 58 | 42 | 0 |
| Utility capacity | 35 | 0 | 626 | 33 | 44 | 0 |
| Reported total power | 25 | 0 | 636 | 31 | 38 | 0 |
| Backup generation capacity | 7 | 0 | 654 | 48 | 40 | 0 |
| Floor area | 177 | 0 | 484 | 77 | 33 | 0 |
| Raised-floor area | 59 | 0 | 602 | 24 | 47 | 0 |
| Data hall area | 6 | 0 | 655 | 6 | 50 | 0 |
| IT area | 26 | 0 | 635 | 5 | 50 | 0 |
| Site area | 38 | 0 | 623 | 35 | 45 | 0 |
| Year opened | 13 | 0 | 648 | 28 | 31 | 0 |
| Year expected | 5 | 0 | 656 | 9 | 46 | 0 |
| Network presence | 237 | 1 | 424 | 36 | 14 | 0 |
| Service | 45 | 11 | 616 | 47 | 5 | 0 |
| Certification or compliance claim | 70 | 26 | 591 | 21 | 28 | 0 |
| Rack density | 10 | 0 | 651 | 13 | 39 | 0 |
| Availability | 0 | 0 | 661 | 239 | 250 | 0 |
| Specifications and facility pages | 101 | 0 | 560 | 185 | 237 | 0 |
| Business contact | 0 | 102 | 661 | 164 | 228 | 0 |
Operator attachments to licensed rows: 428 source listings · field-by-field table
| Field | Listing-specific | Company context | No listing-specific value | Held or conflicting | Not stated in saved source | Expired |
|---|---|---|---|---|---|---|
| Operator-stated status | 6 | 0 | 422 | 1 | 0 | 0 |
| Cooling redundancy | 151 | 0 | 277 | 54 | 8 | 0 |
| UPS redundancy | 110 | 0 | 318 | 34 | 10 | 0 |
| Backup generator redundancy | 46 | 0 | 382 | 18 | 12 | 0 |
| Tier design rating | 30 | 0 | 398 | 31 | 13 | 0 |
| Critical IT capacity | 69 | 0 | 359 | 62 | 13 | 0 |
| Utility capacity | 26 | 0 | 402 | 17 | 12 | 0 |
| Reported total power | 12 | 0 | 416 | 29 | 13 | 0 |
| Backup generation capacity | 10 | 0 | 418 | 14 | 12 | 0 |
| Floor area | 146 | 0 | 282 | 63 | 10 | 0 |
| Raised-floor area | 22 | 0 | 406 | 16 | 15 | 0 |
| Data hall area | 1 | 0 | 427 | 1 | 18 | 0 |
| IT area | 33 | 0 | 395 | 4 | 18 | 0 |
| Site area | 28 | 0 | 400 | 32 | 16 | 0 |
| Year opened | 6 | 0 | 422 | 19 | 10 | 0 |
| Year expected | 5 | 0 | 423 | 8 | 16 | 0 |
| Network presence | 177 | 0 | 251 | 18 | 7 | 0 |
| Service | 10 | 1 | 418 | 8 | 4 | 0 |
| Certification or compliance claim | 66 | 16 | 362 | 11 | 7 | 0 |
| Rack density | 0 | 0 | 428 | 7 | 12 | 0 |
| Availability | 0 | 0 | 428 | 149 | 207 | 0 |
| Specifications and facility pages | 42 | 0 | 386 | 98 | 224 | 0 |
| Business contact | 2 | 52 | 426 | 184 | 124 | 0 |
For the geography and other evidence layers, see state coverage and how the counts differ. Have a missing detail? Send a correction with its source.
The national directory snapshot is adapted from Compute Atlas by Edward Kubiak under its own CC BY 4.0 license. Its rows are not DataCenterData findings, never enter reviewed counts, and are identified by their own layer and provenance fields. The deployed immutable-ID ledger and source manifest travel with the same atomic release.
Some locations in this layer are reported by the provider as derived from OpenStreetMap (© OpenStreetMap contributors, ODbL, https://www.openstreetmap.org/copyright) and Epoch AI (CC BY 4.0).
The public data behind the pages.
These static JSON files are generated from the same reviewed records used to build the site. There is no separate database or hidden national count. Files keep record units, evidence layers, source locators and uncertainty intact.
Core indexes
- registry.json — Stable IDs, aliases, record units and canonical page links (226 rows)
- licensed-directory/snapshot.json — Third-party licensed discovery rows, kept outside reviewed records and counts (1,822 rows)
- us-coverage.json — Fifty-state coverage labels and non-additive record counts
- claims.json — Canonical claim wording, verdicts, evidence and checked dates (90 rows)
- public-posts.json — Public-statement locators; not Claims & facts verdicts
- policy-actions.json — State and local policy actions. Not facility, project, claim, update, or directory counts
- corrections.json — Visible field and verdict corrections (97 rows)
- lifecycle-events.json — Dated approvals, starts, openings, withdrawals and other changes (9 rows)
- state-data-standard.json — Common state field and counting rules
- rights-manifest.json — Per-record reuse classification and approved-field lineage (220 rows)
- relationships.json — Typed, reviewed links between reviewed records, licensed rows, policy records and metro areas, each with its basis (113 rows)
- facility-classifications.json — Sourced facility classifications for reviewed records; unknown unless a cited source states the value (50 rows)
- metro-directory.json — Census metro areas and the licensed rows assigned to each (387 rows)
- map-licensed.json — Licensed discovery rows with usable map coordinates (the printable national map) (1,818 rows)
- map-detailed.json — Detailed map: eligible listings from every published layer, plotted only at a supported coordinate (3,361 rows)
- material-entities.json — Curated organisations and reviewer-bound SEC identifiers used by Project developments
- capital-risk-contracts.json — Rights gates for market and financing datasets; none is displayed
Published collections
Collection files contain reviewed, attributed or unresolved rows exactly as labeled. Counts from different files may overlap and are not automatically additive. The Indiana facility file is a reviewed sample, not a statewide census.
| File | Scope | Contents |
|---|---|---|
| indiana-census.json | Indiana | 21 records |
| indiana-projects.json | Indiana | 15 records |
| national-projects.json | Multiple states | 86 records |
| new-albany-building-leads.json | Ohio | 43 records |
| ohio-facilities.json | Ohio | 29 records |
| ohio-projects.json | Ohio | 20 records |
| projects.json | Multiple topics | 6 records |
Collection file with no records yet (1)
- discovery.json — Multiple topics · 0 records
Machine access today
Every link above is a stable HTTPS JSON response and can be read without JavaScript. The free facility downloads come as CSV, GeoJSON and JSON with a data dictionary. Matching CSV files are also available for the registry, claims, corrections and lifecycle events. Changes are also published as JSON and an Atom feed. There is no query API, uptime guarantee or completeness promise yet.
Your own facility lists
My lists let you keep lists of records from every published layer, see the dated events and record changes DataCenterData has published for them, and export them as CSV or JSON with stable IDs, units, dates and each layer’s license or reuse notice. Lists are saved only in your browser; there are no accounts, alerts or subscriptions.
What may become paid later
The facility downloads above stay free to download. Their DataCenterData fields are licensed CC BY 4.0 and every other field keeps the terms stated for it in the data dictionary. A later paid product may add convenience: filtered queries, saved alerts, historical comparisons and service guarantees. Those features will use the same reviewed records and cannot bypass the evidence gate.