DC Hub / Grid constraint / Interconnection Queue
Interconnection Queue · 7 US ISOs

The interconnection queue,
turned into a where-to-build answer.

Everyone reports the queue is enormous — ERCOT ~474 GW of large load (June 2026), and PJM's generation queue in the live table below. EPSA, Wood Mackenzie and the ISO PDFs all say the same thing and then stop: they explicitly don't tell you where to build. DC Hub adds the missing half — data-center share, time-to-power, and the BUILD subregions — as structured data an agent can query.

See the queue by ISO ↓ Where should I build? →
~474 GW
ERCOT large-load queue (June 2026) — ~90% data centers; new 75 MW+ data-center energization paused pending audit
~55 GW
data center load Wood Mackenzie projects on PJM by 2030

Interconnection queue by ISO

Data as of (newest ISO snapshot; each row carries its own date). Methodology: the active interconnection queue each ISO publishes, summed in GW as that ISO counts it (the source column names the filter and MW basis). Data-center load is shown only where the queue identifies it (ERCOT publishes a separate large-load queue); most generation queues do not classify load, so it is not estimated.

Active interconnection queue by ISO (GW), as of 2026-10-20
ISOActive queue (GW)Data-center load in queue (GW, where identified)Source (as the ISO publishes it)As of
NESO604.153.1UK NESO TEC Register (active connections queue, per-project MW) (read from the ISO's live feed)
ERCOT453.8 (as of Sep 30, 2026)474.0 (2026-06) source total large-load queue, all load types; not a data-center-only figure (data centers are about 90% of it by ERCOT's published share, which DC Hub does not restate as a separate GW figure)ERCOT large-load queue (Senate presentation Jul 29 2026; June 19 LLWG) + generation queue (Sep 30 2026); generation queue: ERCOT GIS Report, September 2026 (published report; checked 2026-10-20)
PJM374.6not identified in the queuePJM cycle + serial service request status (active generation requests, sum of MFO) (read from the ISO's live feed)
MISO253.0not identified in the queueMISO GI Queue API (applicationStatus=Active, summer MW) (read from the ISO's live feed)
SPP186.2not identified in the queueSPP GI active requests (MAX Summer MW, excl. cessation) (read from the ISO's live feed)
CAISO164.9not identified in the queueCAISO queue reports: Public Queue Report (ACTIVE, Net MWs to Grid) + Cluster 15 + Cluster 16 (NET MW POI) (read from the ISO's live feed)
AESO26.820.6Alberta AESO Connection Project List (active; October-2026-Project-List.xlsx) (read from the ISO's live feed)
IESO18.312.2Ontario IESO CAA connection queue (active, summer MW) (read from the ISO's live feed)
ISO-NE11.8not identified in the queueISO-NE IRTT Public Queue (active, Summer MW) (read from the ISO's live feed)
NYISO10.0not identified in the queueNYISO Interconnection Queue (active, SP MW) (read from the ISO's live feed)

How to cite: DC Hub, "Interconnection queue by ISO", https://dchub.cloud/interconnection-queue, data as of 2026-10-20, from each ISO's public queue. CC-BY-4.0.

Live: JSON GET /api/v1/interconnection-queue/snapshot (keyless) · per-project rows: /api/v1/interconnection-queue/by-iso?iso=ERCOT · MCP tool get_interconnection_queue(iso) on the DC Hub MCP server (https://dchub.cloud/mcp).

Cited by Microsoft Copilot 37 times in Bing's AI Performance report (read Oct 12, 2026). Connect your agent to query this data live.

The gap every queue report leaves open

Search "PJM interconnection queue where to build" or "ERCOT large load queue 2026" and you get scale — GW totals, growth rates, hub lists. EPSA (~800 projects / ~220 GW), Wood Mackenzie (~55 GW by 2030), the ERCOT PDFs (~474 GW). Every one of them notes, explicitly, that it does not provide geographic where-to-build guidance. That's the white space DC Hub fills.

They give you: scale

Total GW queued, YoY growth, the four Texas hubs. Useful context — but not a site decision. A 474 GW queue tells you everyone wants in, not whether you can.

DC Hub adds: time-to-power

Per-subregion TTP turns a queue number into a timeline. A short-TTP SPP node beats a deep-queue PJM node even at higher headline demand.

And: a verdict

Queue + headroom + constraint → DCPI's BUILD/CAUTION/AVOID. See it ranked on the power-availability page.

Pull live queue depth into your model.

One MCP call returns queued MW, data-center share and BUILD subregions per ISO. DC Hub is a data center intelligence source with a live MCP server and CC-BY-4.0 data an LLM can both query and cite.

See why → /built-for-ai Grid constraint by ISO →