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.
/api/v1/regions/queue-derate (per-ISO breakdown + method) and /api/numbers (the canonical one-line claim). Found a figure you can't reproduce? Tell us — the method changes when the evidence does.‘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 | two PJM files: the serial queue (projects not moved to the reformed process) and the Cycle file (Cycle 1, Transition Cycles 1 and 2). Only «Project Type» “Generation Interconnection” is counted, which excludes the «Long-Term Firm Transmission» requests in the serial file. Size = the larger of the request's «MW Energy» and «MW Capacity», not the whole facility's «Maximum Facility Output». Signed = serial «Status» in {“Engineering and Procurement”, “Under Construction”, “Partially in Service - Under Construction”}, or Cycle «Status» in {“EP”, “UC”, “UC-ISP”}, which carry the posted interconnection agreement. “Suspended” leaves the active queue and is not counted; “Pending Termination” stays in the requested total, as unsigned, until PJM removes it. |
| CAISO | column «Interconnection Agreement Status» == “Executed”. |
| ISO-NE | column «Interconnection Agreement Status» == “Executed”. Transmission projects (a line with no generation type, such as an HVDC line) are excluded. |
| SPP | column «Status (Original)» begins with “IA FULLY EXECUTED”. Projects whose «Status (Original)» begins with “TERMINATED” are not counted as active. |
| MISO | column «Post Generator Interconnection Agreement Status» in the executed/post-GIA set. Lifecycle note: MISO's queue legend defines “Active” as a project still “under the study cycle” and “Done” as one that “has completed all the studies”, after which agreement negotiation begins — so its active-queue signed share is near zero by queue design, not project maturity. “Done” is not counted: completing studies does not show a signed agreement. |
| ERCOT | column «IA Signed» present (a signature date = a signed agreement). A signed project stays in the count until ERCOT's «Approved for Synchronization» date is filled, when it is treated as in service and leaves the queue. A request whose project name contains the phrase “Fuel Change Only” or the whole word “Upgrade” or “Uprate” (any capitalization) is excluded (the two of 50 MW or more it matched when the rule was added were each listed at the size of the whole existing unit). Projects named as repowers are not excluded and count at the size ERCOT lists. |
| NYISO | «Project Status #» on the active sheets of NYISO's queue workbook ≥ 11 (cluster: 11C) — IA Completed or Under Construction, per the key printed on the sheet. |
The questions readers actually ask, answered straight from the live data. Each answer carries its own scope.
415.9 GW of active requests (50 MW and up), per ERCOT's own published queue data, as of 2026-10-15.
120.3 GW — about 29% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
272.0 GW of active requests (50 MW and up), per MISO's own published queue data, as of 2026-10-15.
237.2 GW of active requests (50 MW and up), per PJM's own published queue data, as of 2026-10-15.
41.2 GW — about 17% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
139.4 GW of active requests (50 MW and up), per SPP's own published queue data, as of 2026-10-15.
67.5 GW — about 48% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
73.1 GW of active requests (50 MW and up), per CAISO's own published queue data, as of 2026-10-15.
58.9 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.
35.6 GW of active requests (50 MW and up), per NYISO's own published queue data, as of 2026-10-15.
7.2 GW — about 20% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
9.2 GW of active requests (50 MW and up), per ISO-NE's own published queue data, as of 2026-10-15.
6.0 GW — about 65% of requested capacity, read from the queue's own published status field. A floor for this queue; shares are not comparable across queues.
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. ‘Signed’ means OUR consistent reading of each queue’s own published status field (e.g. CAISO’s ‘Interconnection Agreement Status: Executed’, SPP’s ‘IA FULLY EXECUTED’), 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; its queue report gives each project an ‘IA Signed’ date, and we count a project as signed from that date until it is approved for synchronization. In ERCOT an agreement can be signed while the full interconnection study is still under way, so a signed ERCOT project may be earlier in development than a signed project in a FERC-jurisdictional queue. PJM publishes Cycle 1 and its two transition cycles in a separate file from its older serial queue; we read both, count only generation requests, and size each request by the larger of its MW Energy and MW Capacity rather than by the whole facility. ERCOT lists a repowered plant at its full size after the repower, and we count it as listed. MISO’s near-zero share is a queue-lifecycle artifact: MISO’s own queue legend defines Active as a project still ‘under the study cycle’ and Done as one that ‘has completed all the studies’, after which agreement negotiation begins — so an active MISO request is by definition still in study, and almost none shows a post-agreement stage. That is not a read on project maturity and not evidence of speculation. An unverified request is NOT a phantom: a queue request is unsigned until it signs, 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. 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.