Verify · the pickaxe, in the open
How the LOADSTAR Number is computed
Every figure below is pulled live from official U.S. ISO interconnection queues and recomputable from the raw JSON. This is the whole derivation — no hidden step. Don't trust; recompute.
The one-line claim, straight from the single source that every LOADSTAR surface reads:
Of the 958.5 GW requested across the seven active U.S. ISO generation interconnection queues, at least 145.1 GW — about 15.1% — carries an executed interconnection agreement, based on data from the 4 queues that publish a usable status field (CAISO, ISONE, SPP and PJM). A floor, not a rate: what our reading cannot see counts as unverified, never as speculative.
The derivation, step by step
1Pull the live queues.
Active interconnection-queue rows, 50 MW and up, from the seven live U.S. ISOs — PJM, ERCOT, CAISO, MISO, SPP, ISO-NE, NYISO. This is the generation queue (power plants & storage seeking to connect), not data-center load requests. Any fuel type. Bulk annual datasets without a status field (e.g. LBNL) are reported separately, never mixed in.
2Sum requested, per ISO.
Requested = ∑ capacity of those active rows. Signed = the subset showing a signed agreement or construction status in that queue's own published data (how we read it per ISO is in the next section).
| ISO / RTO | Requested (GW) | Signed (GW) | Requests | Status coverage |
| ERCOT | 307.2 | 0.0 | 1,128 | 100.0% |
| MISO | 241.7 | 0.2 | 1,053 | 14.8% |
| SPP | 150.5 | 60.7 | 686 | 40.3% |
| PJM | 148.8 | 16.6 | 650 | 11.1% |
| CAISO | 73.9 | 59.7 | 235 | 80.8% |
| NYISO | 24.9 | 0.0 | 135 | 1.1% |
| ISONE | 11.6 | 7.9 | 36 | 68.8% |
| ALL SEVEN | 958.5 | 145.1 | 3,923 | — |
The largest verified block — about 41.8% of all verified GW — comes from SPP, whose published status field is the most complete in our reading. Where the table shows ~0 verified, our reading finds no machine-readable agreement-status field in that queue — a limit of our reading of the public data, not a claim that those projects are speculative. Provenance of the read: about 11.4% of all verified GW (PJM) rests on a keyword match over the queue's status text rather than a named agreement-status column — the weaker of our two reads, and where a false positive would come from. We flag it, and treat that share as a floor: the column-read queues carry a smaller keyword tail this figure does not count.
3Divide.
6.6× requested vs verified-signed · ~15% verified (a floor)
The Number is the ratio; the floor is the honesty. 958.5 GW requested ÷ 145.1 GW verified = 6.6×. ‘Verified’ is a floor by construction: in 1 of the 7 queues our reading finds no machine-readable agreement-status field, so those GW count as unverified — never as speculative. The ratio is therefore an upper bound on the true requested-to-signed gap. An unverified request is not a phantom.
How we read “signed”, per ISO
‘Signed / under construction’ is our reading of each ISO's published queue-status data, applied consistently across all seven queues — it is not a single certified field (there is no national one). Exact rule per ISO, mirrored from the collector:
| ISO / RTO | What we count as “signed” |
|---|
| PJM | our keyword read of the queue's published status text — PJM tiers its published status in prose rather than a single machine-readable agreement column. A floor, not a boundary. |
| CAISO | column «Interconnection Agreement Status» == “Executed”. |
| ISO-NE | column «Interconnection Agreement Status» == “Executed”. |
| SPP | column «Status (Original)» begins with “IA FULLY EXECUTED”. |
| MISO | column «Post Generator Interconnection Agreement Status» in the executed/post-GIA set. |
| ERCOT | column «IA Signed» present (a signature date = a signed agreement). Lifecycle note: in ERCOT's published data, signing moves a project out of the active queue (to “Completed”) — so its active-queue signed share is near zero by queue design, not project maturity. |
| NYISO | column «S» (stage code) ≥ 11 — IA Completed, Under Construction, or In Service. |
Worked example — SPP, end to end
Pull 686 active rows (50 MW and up) from SPP’s published queue → sum requested =
150.5 GW → apply the queue’s own status rule (“column «Status (Original)» begins with “IA FULLY EXECUTED”.”) → sum the rows that meet it =
60.7 GW → divide:
40% of SPP’s requested capacity carries an executed agreement — that queue’s floor. Redo it from the raw JSON:
/api/v1/regions/queue-derate.
Queue by queue — quick answers
The questions readers actually ask, answered straight from the live data. Each answer carries its own scope.
How much generation capacity is requested in ERCOT's interconnection queue?
307.2 GW of active requests (50 MW and up), per ERCOT's own published queue data, as of 2026-08-30.
How much generation capacity is requested in MISO's interconnection queue?
241.7 GW of active requests (50 MW and up), per MISO's own published queue data, as of 2026-08-30.
How much generation capacity is requested in SPP's interconnection queue?
150.5 GW of active requests (50 MW and up), per SPP's own published queue data, as of 2026-08-30.
How much of SPP's queue carries an executed interconnection agreement?
60.7 GW — about 40% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
How much generation capacity is requested in PJM's interconnection queue?
148.8 GW of active requests (50 MW and up), per PJM's own published queue data, as of 2026-08-30.
How much of PJM's queue carries an executed interconnection agreement?
16.6 GW — about 11% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
How much generation capacity is requested in CAISO's interconnection queue?
73.9 GW of active requests (50 MW and up), per CAISO's own published queue data, as of 2026-08-30.
How much of CAISO's queue carries an executed interconnection agreement?
59.7 GW — about 81% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
How much generation capacity is requested in NYISO's interconnection queue?
24.9 GW of active requests (50 MW and up), per NYISO's own published queue data, as of 2026-08-30.
How much generation capacity is requested in ISONE's interconnection queue?
11.6 GW of active requests (50 MW and up), per ISONE's own published queue data, as of 2026-08-30.
How much of ISONE's queue carries an executed interconnection agreement?
7.9 GW — about 68% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
The caveat travels with the number
This is the GENERATION interconnection queue — power plants and storage seeking to connect to serve future load growth, of which AI data centers are one driver — not data-center (large-load) requests, which most ISOs do not publish. ‘Verified’ means OUR consistent reading of each queue’s own published status field (e.g. CAISO’s ‘Interconnection Agreement Status: Executed’, MISO’s post-GIA stage), including projects already under construction — which require an executed agreement; it is not a certified or audited figure. Status taxonomies differ by ISO, so per-queue shares are not directly comparable, and a near-zero share can be queue design rather than weakness: ERCOT runs a connect-and-manage regime outside FERC’s interconnection jurisdiction, and in its published data a project whose agreement is signed moves out of the active queue (it is listed as Completed) — so ERCOT’s active-queue signed share is near zero by construction, a queue-lifecycle artifact, not a read on project maturity. MISO’s near-zero share has a different cause, not a shared one: its post-generator-interconnection-agreement stage field is populated on only a small slice of its rows, so most of its queue carries no readable agreement status at all and cannot count as signed under our rule — an absence of data, not evidence of speculation. Where our reading finds no usable machine-readable field (currently NYISO), that says nothing about those ISOs’ disclosure — it may be our parsing limit — and those GW are counted as unverified, never as phantom. An unverified request is NOT a phantom: queues are unsigned by nature and status is graded (FERC Order No. 2023 replaced serial first-come with first-ready cluster studies). The raw queue is not deduplicated; the same project can appear more than once (part of what FERC’s RM26-4 show-cause targets). Historically most queued generation never reaches operation: of the capacity that requested interconnection from 2000 to 2020, 13% reached commercial operation by the end of 2025, 75% was withdrawn and 10% was still active (LBNL, ‘Queued Up: 2026 Edition’, p.55; by project count rather than capacity the completion figure is 19%, p.4). That cohort ran under the serial regime Order 2023 has since replaced, so it benchmarks history rather than this queue — which is why we report what carries a signed agreement today instead of forecasting what will be built. Descriptive of today, not a forecast.