Licence and attribution text last reviewed 10 August 2026. Per-layer data refresh dates: When each layer was last refreshed.
Licence sources last checked automatically: not loaded. This is a link-reachability check, not a review of the licence text. Raw results.
DC Hub exists to aggregate public infrastructure data into one place, so that nobody has to rebuild the same picture from forty scattered sources. If you rely on a number we publish, you should be able to see where it came from and what you are allowed to do with it. This page is that answer, in full.
The rule: what DC Hub computed is openly licensed and we want it cited. What DC Hub collected carries its upstream's terms, and that is not ours to give away.
The licence therefore differs by layer. A single answer across all four layers would necessarily be false about at least one of them, so we publish four.
open layer CC-BY-4.0 sub-scores: Pro, licensed separately
Open layer: the BUILD / CAUTION / AVOID verdicts and their band
thresholds, composite_score, per-market rankings by
those, and the published methodology.
Licensed under Creative Commons Attribution 4.0 International. Republish it, chart it, build on it, put it in a client report, train on it. Just attribute it.
Current data (from 1 December 2026): a verdict or composite for a day on or after 1 December 2026 comes under CC-BY-4.0 30 days after that day. Until then, read it here and quote current verdicts and composite scores, for as many markets as the work needs, in editorial work: an article, report, research note, post, presentation, or an AI assistant's answer to a user's question. Attribute it. A DCPI licence is needed only to republish current values in bulk (the full current list, or a table of more than 25 markets in one piece) or on a recurring basis (a feed, dashboard, newsletter section or product that tracks DCPI markets): jonathan@dchub.cloud. Training AI models on dchub.cloud pages is allowed; it does not grant a right to republish current values in bulk. Days before 1 December 2026, the band thresholds, the methodology and the monthly DCPI Rankings release stay CC-BY-4.0. Details in Terms §5.2.
This is our own derived analytical work: the inputs are public, the transform is ours, and a third party with no access to our database can reproduce it from published inputs. We would rather be cited than paid for this layer — an index nobody may quote is worthless.
Sub-scores (since 31 October 2026):
excess_power_score, constraint_score,
time_to_power_months, the risk and opportunity detail,
narrative and forecast are on Pro and above and are not CC-BY. Use them
internally and in work for your own clients, with attribution.
Republishing them in a product or dataset needs a DCPI redistribution
licence, which can include custom markets, weightings or a delivered
feed: jonathan@dchub.cloud. Values
released before that date remain CC-BY-4.0.
Cite as: Data Center Power Index (DCPI), DC Hub, dchub.cloud, CC-BY-4.0. Retrieved <date>.
Include the date and the
method_version (e.g. 2.3.0). DCPI is
recomputed daily and the bands are versioned — a score without a
version and a date is not reproducible.
our analysis CC-BY-4.0 raw readings: operator's terms
Live and historical grid conditions come directly from the system operators who publish them. Our normalisation and the rankings and headroom analysis built on top are ours, and are CC-BY-4.0 on the same terms as §1’s open layer (the DCPI sub-scores are not part of it). The underlying readings are not ours to relicense — if you want the raw feed, take it from the operator. Several are one HTTP call away.
| Region | Operator |
|---|---|
| United States — 7 ISOs (ERCOT, PJM, CAISO, MISO, SPP, NYISO, ISO-NE) | EIA-930 — US federal, public domain |
| United States — TVA, BPA and 40+ EIA balancing authorities | EIA-930 |
| Canada — Ontario (IESO) | IESO |
| Canada — Alberta (AESO) | AESO |
| Canada — Québec (Hydro-Québec) | Hydro-Québec open data |
| Great Britain | NESO / Elexon |
| Europe — 30+ bidding zones | ENTSO-E Transparency Platform |
| Taiwan | Taipower |
| Japan | OCCTO |
| South Korea | KPX |
| Brazil | ONS |
| Australia (partial) | AEMO |
| Singapore (partial) | EMA |
| Modeled (not live): Nord Pool | DC Hub model |
mostly US federal, public domain
| Layer | Source | Licence |
|---|---|---|
| Power plants, generation, retail rates | EIA | US federal, public domain |
| Substations, transmission lines, gas pipelines | OpenStreetMap, gap-filling earlier HIFLD records (HIFLD Open closed August 2025) | ODbL 1.0, share-alike — extracts and method |
| Carrier and fiber facilities | FCC | US federal, public domain |
| Middle-mile fiber routes | NTIA Enabling Middle Mile Broadband Infrastructure Program | terms unconfirmed |
| Natural-hazard risk | FEMA National Risk Index | US federal, public domain |
| Air permits | EPA ECHO | US federal, public domain |
| Global power & gas infrastructure | Global Energy Monitor | CC-BY 4.0 |
| ERCOT queue milestones, developer, completion probability | ERCOTQueue (Matt Prusak) | CC-BY 4.0 |
| Submarine cables & landing points | TeleGeography Submarine Cable Map public API | terms unconfirmed |
attribution required no redistribution grant
The facility inventory is a composite. It contains data from OpenStreetMap — © OpenStreetMap contributors, licensed under the Open Database License (ODbL) 1.0 — plus PeeringDB, Wikidata (CC0), operator disclosure and operator websites, regulatory filings and press releases, third-party directories, and our own curation.
You may read, query and cite it — through the product, the API and the MCP tools, including in published work with attribution.
DC Hub does not currently grant redistribution of this corpus as a dataset, and we would rather say so than claim otherwise. Two honest reasons:
robots.txt saying
Allow: / means a crawler may fetch a page — it grants
nothing about reusing a compiled directory, and we are not going to
treat it as if it did.That review runs per source, and sources clear individually rather than all at once. It is ordinary data hygiene, not a hold on the product.
These dates are read live from DC Hub's public freshness feed when this page loads. None is typed in by hand. Each is the date of the newest record DC Hub holds for that layer, in UTC: when DC Hub last computed, retrieved or synced it. It is not the publication date of the upstream dataset, which DC Hub does not capture.
| Layer | Newest record | What the date is |
|---|---|---|
| DCPI scores and verdicts (§1) | Not loaded | When DC Hub last computed the index |
| Retail electricity rates (§3) | Not loaded | Newest record retrieved from the source |
| Transmission lines (§3) | Not loaded | Newest record added |
| PeeringDB networks (§4) | Not loaded | Last sync from the source |
| Substations (§3) | No date shown | This table mixes sources. Its newest record is the newest write to any of them, which would make the HIFLD portion look fresher than it may be. |
| Grid telemetry (§2) | No date shown | No per-operator reading date is published on a compact endpoint. The full freshness feed reports the oldest live stream and the streams that are behind. |
| Facility inventory (§4) | No date shown | A composite of sources that refresh on different schedules. A newest-record date would make the whole look as fresh as its fastest part, so none is shown. |
| FCC, FEMA, EPA ECHO, Global Energy Monitor, ERCOTQueue and TeleGeography layers (§3) | No date shown | The freshness feed publishes no refresh date for these layers. We would rather say so than show a date that was not measured. |
If a live date reads “Not loaded”,
your browser blocked the request or JavaScript is off. The feed
itself is public JSON at
/api/v1/freshness/radar.
These are fields people reasonably expect us to carry, inside topics we do cover, and we do not have them. We would rather you learn that here than after a day of API calls.
Instead points at a different real field — never a stand-in for the missing one. A cooling type is not a PUE, and we will not infer one.
Please do — no agreement needed for the open DCPI layer in §1 (current values: quote any number of markets in editorial work; bulk or recurring republishing needs a DCPI licence) or for §2. Cite the verdicts, the composite, the methodology or our grid analysis as described above, and tell us if you would like us to link your work back.
Redistributing the facility corpus as a dataset needs a written agreement, because it needs per-source clearance we do not yet have across the board. Ask: jonathan@dchub.cloud.
Found something wrong here? A source named incorrectly, or a licence stated incorrectly, is a defect and we will treat it as a bug report. Email jonathan@dchub.cloud and we will correct this page.
The machine-readable version of this statement
ships in the DC Hub repository as DATA-LICENSE.md, and the
per-layer licence is emitted on every API response in the
provenance block.