Data guide · last changed 17 November 2026

Use the right layer before using the number.

DataCenterData keeps broad discovery leads, reviewed records, policy actions, public statements and evidence checks separate. This guide shows what each one can establish—and what it cannot.

Start with the question you have

Your taskStart hereWhat you get
Find a possible facilityMap or directory1,822 licensed source rows with provenance, reported status and location precision; the map holds 3,361 source listings across all layers. These are discovery leads, not a verified national total.
See every source on one facilityFacility register2,650 register records, each joining the source layers that name one campus, building, suite or operator presence, with state and county lists and a free download. Different units, not a count of distinct sites.
Check a project or facilityReviewed records or searchNarrower records with a stable ID, defined record unit, evidence status, sources and dates.
Check a statement or questionEvidence & answers or public statementsA bounded finding, its evidence, remaining uncertainty and correction history.
Understand a rule or government actionPolicy tracker567 policy actions, one row per sourced legal or administrative action. Policy rows are not facility counts and do not label a state “open” or “closed.”
Analyze or reuse recordsData downloadsStatic JSON, selected CSV files, rights boundaries and source provenance from the same release that built the public pages.
Do not add unlike populations.

Every total on the site, what it counts and where it appears is listed on Why counts differ. A project or campus may contain several buildings, tenants or provider presences. The reviewed project/campus inventory, reviewed facility/building inventory and licensed directory are separate, overlapping populations. Their counts are never added into one national facility total.

What one row means

Record unitMeaningDo not assume
ProjectA development proposal or undertaking documented in public records.That it was approved, built or operates today.
CampusA named site that may contain several phases or buildings.That every announced phase exists or that one campus equals one building.
Building or operating facilityA physical data-center structure or operating site supported at that level.That every tenant, suite or provider presence is a separate building.
Provider presenceA company reports service or space at a site.That the provider owns or operates the building.
Licensed discovery rowA third-party source row preserved with its upstream ID, attribution and DataCenterData directory ID.That DataCenterData independently verified its identity, status, capacity or coordinates.
Policy actionA sourced law, rule, order, tariff, pause, incentive, study or other government or grid action.That it applies to every project, is permanent, or describes a facility.
Claim or public statementA specific proposition reviewed against cited evidence.That documenting the statement proves it true.

Read the evidence label before the headline

See every evidence-result definition →

Location and map precision

LabelHow to read it
Exact (provider label)The upstream provider labeled the coordinates exact. DataCenterData has not converted that label into a parcel finding.
ApproximateThe point is suitable for regional or local navigation, not a property boundary. This includes source points whose own notes describe only a city, ZIP code, metro or area.
Approximate (Census address interpolation)The source publishes a street address but no coordinate. The point is the U.S. Census Bureau geocoder’s address-range interpolation of that published street, admitted only after DataCenterData checked the house number, street name, state, city or postal code and the state outline. It is a place to draw one listing, not a rooftop, parcel or building coordinate, and never proof that the listing is a distinct or operating facility.
Approximate (government address point)The source publishes a street address but no coordinate, and the Census geocoder gave no usable answer. The point is a state or local government address record, named on the point, admitted only after DataCenterData checked the same house number, street name, state, city or postal code and the state outline. It marks an address record, not a rooftop, parcel or building, and is never proof that the listing is a distinct or operating facility. These points stay out of the free download because they are cited from their publishers, not relicensed.
RepresentativeThe point represents the named place or record for display and should not be read as the facility entrance or parcel.
Shown through an attached licensed rowAn operator’s own listing or a government record published on a licensed row’s page shares that row’s marker instead of receiving a second one. The list says so; the shared marker is not a same-site finding.
Bounded nearby groupNearby source points are combined into one accessible map target. The original rows remain available from the linked result.

A marker shows where a source places a row; it does not prove ownership, parcel boundaries, operating status or capacity. Use the row’s source citations for those questions.

Status, dates and capacity

Downloads and reuse

What the download dates mean

Static JSON files with a generated_at_basis explanation retain the older field name generated_at for compatibility. Its value is a derived collection date from recorded review, history, lifecycle and correction dates. It is not the build or publication time, and it does not mean every record was checked on that date. A site update can therefore be newer than this date.

Use each record’s source, capture and review dates to judge its evidence. Licensed-source editions and snapshot dates describe their own datasets. In files created by the browser’s facility-list export, generated_at instead means when you downloaded the list; it does not refresh the evidence dates.

The free facility downloads (CSV, GeoJSON and JSON; per-field reuse terms, with DataCenterData fields under CC BY 4.0) use generated_at for the facility register’s newest input date and carry a version string (that date plus a digest of the exported rows). Each release replaces them; earlier versions are not kept online, so cite the version with your access date.

The data page lists the public JSON and CSV files, their scope and reuse boundary. The licensed directory snapshot travels with its source manifest and stable-ID ledger. The national map SVG is available for reports with the attribution and limitations printed on the map page.

Edition identifiers

Reader pages name the licensed directory by its upstream edition number and date. The full identifier of the edition this site was built from is 1.34.1+reviewed-2610e0556b3d, dated 14 October 2026: the upstream Compute Atlas edition, then a suffix that identifies DataCenterData's reviewed preservation of retained rows and publication holds. The same identifier is in the snapshot and its manifest. State research notes cite the Compute Atlas state extracts they used; the exact snapshot names are kept in the research files.

Linked permits, orders, filings, company pages and other source documents keep their own rights. A public URL is not, by itself, permission to republish the underlying document or database.

Report a missing facility or stronger evidence

Use the correction and missing-record form. For a missing facility or project, include the state and locality, the name used by the source, its reported status, and at least one public primary-source URL. An official permit, utility or commission filing, tax or incentive record, government page, or operator document is most useful.

A submission enters review; it does not publish automatically. DataCenterData first checks identity, record unit, dates, source rights and possible duplicates. Accepted factual changes appear in the public correction and change history.

Fastest useful submission

Send one public source that identifies the place and one that supports the current status. If the source gives only a city or area, say that—the record can preserve an approximate location without inventing a parcel.