# US Data Center Directory, release 2026-10-02

Frozen copy of the Malachi.Energy data center dataset as published at
https://malachi.energy/data-centers. These files will not change. The moving URLs on
the site always serve the newest version; cite this directory when the numbers
need to stay put.

- Dataset version: 2026-10-02 (last data change)
- Snapshot taken: 2026-10-02
- Methodology version: 4
- First published: 2026-03-09
- Release page: https://malachi.energy/data-centers/releases/2026-10-02
- Latest release (moves): https://malachi.energy/data-centers/releases/latest/
- Maintainer: Malachi Rein, LEED AP BD+C, https://malachi.energy/about

## What is in this release

| Count | Value |
|---|---:|
| Tracked mega projects | 54 |
| Planned capacity, MW | 109,198 |
| Announced investment, USD billions (all bases) | 1,210.2 |
| OSM-verified facilities | 1,771 |
| Jurisdictions covered | 48 |
| Estimated US facilities (Baxtel national count) | 5,274 |

## Files

| File | Rows | License | Description |
|---|---:|---|---|
| mega-projects.csv | 54 | Mega project tally and state estimates, free for personal, educational, and editorial use with attribution to Malachi.Energy | Tracked US data center mega projects with the basis and confidence of every figure. One row per project, sorted by planned capacity. |
| mega-projects.json |  | Mega project tally and state estimates, free for personal, educational, and editorial use with attribution to Malachi.Energy | The same projects as mega-projects.csv in camelCase, with the project description, the source as an object, national totals split by basis, and the basis dictionary inline. |
| states.csv | 48 | Mega project tally and state estimates, free for personal, educational, and editorial use with attribution to Malachi.Energy | Verified and estimated facility counts plus mega project totals for every covered jurisdiction, sorted by verified count. |
| facilities.csv | 1,771 | OSM-verified facility layer, ODbL 1.0 | Every OSM-verified facility in the directory, all jurisdictions in one file. The live site serves this layer per state at /data-centers/<state>/facilities.csv. |
| manifest.json | | | Machine-readable version of this README: counts, files, SHA-256 hashes, changelog. |
| checksums.sha256 | | | SHA-256 of every other file. Verify with `sha256sum -c checksums.sha256`. |
| CITATION.bib | | | BibTeX entry for this release. |
| LICENSE.txt | | | Which license covers which file. |

## Data dictionary

### mega-projects.csv

| Column | Meaning |
|---|---|
| id | Stable slug; also the last segment of the project page URL. |
| name | Campus or project name as the developer uses it. |
| developer | Company building or operating the campus. |
| location | City or county and state, as reported. |
| state | Two-letter USPS abbreviation. |
| capacity_mw | Planned power capacity in megawatts. Planned, not delivered. |
| capacity_basis | What the capacity figure rests on. One of: disclosed, filing, reported, estimated. |
| investment_usd_billions | Announced investment in USD billions. |
| investment_basis | What the investment figure measures. One of: campus-capex, first-phase-capex, bond-authorization, power-plant-capex, program-commitment, press-reported, analyst-estimate. |
| is_estimate | true when capacity is a Malachi.Energy estimate or investment is a third-party analyst estimate. |
| confidence | high when both figures come from the developer or a filing and the site has physical progress or firm contracts; medium when one figure is reported, estimated, or scoped differently than the campus; low when proposed without permits or capacity is an estimate. |
| included_in_aggregate | Whether the row counts toward the headline totals. Currently true for every project. |
| comparable_campus_investment | true when the investment basis is developer-stated campus or first-phase cost, the only bases that measure the same thing. |
| status | operational (first phase serves load), under-construction, announced, or proposed. |
| target_year | Developer-stated year for first or full operation. Empty when none is public. |
| lat | Latitude, WGS84. Precision varies by source; one-decimal values locate a county, not a site. |
| lon | Longitude, WGS84. |
| location_basis | How precisely the coordinate locates the campus. One of: site, address, city-centroid, county-centroid. Distance facts count only site and address rows. |
| source_label | Publisher of the primary public source for the two figures. |
| source_url | URL of that source. |
| source_date | Evidence date of the source, ISO, month precision allowed. |
| last_verified_at | Last release in which every project was re-checked against its source. Trails the dataset version when a release changes only another layer. |
| url | Project page on malachi.energy. |

### mega-projects.json

The same projects as mega-projects.csv in camelCase, with the project description, the source as an object, national totals split by basis, and the basis dictionary inline.

### states.csv

| Column | Meaning |
|---|---|
| state | Jurisdiction name. |
| abbr | Two-letter USPS abbreviation. |
| osm_verified | Facilities tagged as data centers in OpenStreetMap with a mapped location in this jurisdiction. |
| estimated_total | Estimated facility count: Baxtel state count where Baxtel publishes one, otherwise osm_verified scaled so all jurisdictions sum to the Baxtel national total. |
| mega_project_count | Tracked mega projects in the jurisdiction. |
| mega_capacity_mw | Sum of planned capacity across those projects, megawatts. |
| mega_investment_usd_billions | Sum of announced investment across those projects, all bases mixed. |
| top_operator | Operator with the most OSM-verified facilities in the jurisdiction. |
| top_hub | City with the most OSM-verified facilities in the jurisdiction. |
| url | State page on malachi.energy. |

### facilities.csv

| Column | Meaning |
|---|---|
| name | Facility name from OpenStreetMap, empty when untagged. |
| operator | Operator from OpenStreetMap, empty when untagged. |
| city | City from the OSM address tags, or from the address source where an address_basis column says it is not osm. |
| state | Two-letter USPS abbreviation, assigned by point-in-polygon against Census boundaries. |
| address | Street address, empty when none is known. From the OSM tags unless an address_basis column says otherwise. |
| postcode | Postal code, empty when none is known. |
| lat | Latitude, WGS84. Centroid for building outlines. |
| lon | Longitude, WGS84. |
| website | Website when tagged. |
| osm_type | node, way, or relation. |
| osm_id | OpenStreetMap element id. |
| osm_url | Link to the element on openstreetmap.org. |
| address_basis | Where the address comes from. One of: osm, address-point, campus, researched. osm is tagged on the element; address-point is a public-domain address point at or near the building (USDOT National Address Database or a public-domain county source, via Overture Maps); campus is the address of an adjacent building on the same campus and can name a neighbour; researched comes from a public source. Every non-osm address was reviewed by hand. Empty when there is no address. |
| address_source | For non-osm addresses, the dataset release or URL the address comes from. Empty for osm and missing addresses. |

## Method (version 4)

Every OpenStreetMap facility carries an address basis: osm when the address is tagged in OpenStreetMap, address-point when it comes from a public-domain address point inside or beside the building outline (the USDOT National Address Database and public-domain county sources, via Overture Maps), campus when it is the address of an adjacent building on the same campus, and researched when it comes from an operator page or public record. Only public-domain, CC0, or PDDL address points are used, so they can enter the ODbL layer. No address is published without a hand review, and an OpenStreetMap tag always takes precedence. The mega project last_verified_at column now dates the last release in which every project was re-checked, instead of the dataset version.

Full method, reconciliation table, and investment split: https://malachi.energy/data-centers#methodology

## Changes in this version

Meta El Paso investment restated to the developer-stated total development cost, and the Baxtel national and state counts refreshed.

- Meta El Paso: investment $10B to $14B (developer-stated campus cost, buildings plus long-lived power, cooling, and connectivity infrastructure), per Meta’s 2026-07-28 release. Capacity stays at 1 GW.
- Baxtel national count: 5,207 to 5,274 facilities and 793 to 804 operators, as listed on Baxtel’s United States page on 2026-10-02.
- Baxtel state counts: Virginia 786 to 793 and Texas 774 to 779; California is unchanged at 312. State estimates for the other jurisdictions rescale so every estimate still sums to the national count.
- The OpenStreetMap layer was not refreshed and no project was added, removed, or moved. Methodology version 4.

## Cite

Rein, Malachi (2026). US Data Center Directory, dataset version 2026-10-02. Malachi.Energy. https://malachi.energy/data-centers/releases/2026-10-02

```bibtex
@misc{malachienergy_data_centers_2026_10_02,
  author = {Rein, Malachi},
  title = {US Data Center Directory},
  howpublished = {Malachi.Energy},
  year = {2026},
  version = {2026-10-02},
  note = {Dataset version 2026-10-02. Facility layer ODbL 1.0 (OpenStreetMap contributors); compilation free with attribution.},
  url = {https://malachi.energy/data-centers/releases/2026-10-02}
}
```

## Licenses

See LICENSE.txt. Facility layer: Open Database License (ODbL) 1.0. Compilation: Mega project tally and state estimates, free for personal, educational, and editorial use with attribution to Malachi.Energy.