Where the data centers want to go and how the queue is moving. Each region pairs the ISO's generation interconnection queue, read daily from the ISO's own queue file and dated on the card, with a hand-curated corridor baseline (queue, peak, congestion, transmission) labelled with the date it was set.
255 GW of data center requests in Oncor territory alone — 8x system peak. Severe dilution expected under Batch Zero. South Texas and the Plains offer unconstrained alternatives.
Northern Virginia hosts 70%+ of US hyperscale capacity. PJM Cycle 1 launches 2026 with reformed interconnection. Ohio, Indiana, and West Virginia emerge as overflow markets with lower capacity prices.
MISO South and SPP absorb developers priced out of Texas and PJM. Abundant wind + gas, low land costs, and growing transmission capacity make these the next frontier.
California grid constraints and wildfire risk push developers to Phoenix, Las Vegas, and Reno. Solar abundance but transmission bottlenecks define the Western corridor.
Georgia, Tennessee, and the Carolinas offer nuclear baseload, low rates, and aggressive incentives. TVA and Southern Company actively court hyperscale with dedicated power programs.
Each brief covers one region (PJM, CAISO, MISO and SPP, the Southeast, ERCOT) and
separates two kinds of figure. Live: the region's generation interconnection
queue, summed from DC Hub's daily ingest of each ISO's own queue file, with its
source and date (ERCOT uses its dated monthly report; the Southeast has no ISO
queue feed). Baseline: the per-corridor queue, system peak, congestion,
transmission and dilution figures, set by hand and shown with the date they were
set. Live per-ISO demand and fuel mix are on the grid page.
Per-ISO signals also flow into the Data Center Power Index
(DCPI), the daily 0–100 score that ranks 200+ U.S. markets on whether
they're BUILD, CAUTION, AVOID, or LOW_SIGNAL. If
you're going site-by-site, jump to a specific market on the
markets index — every market page links back to its
serving ISO so the energy-intelligence and site-selection views stay in sync.
For agents, the same data is exposed as JSON at /api/v1/grid-intelligence
and through the DC Hub MCP server.