Queue Wire
Which interconnection requests moved, and which did not.
Why this exists
Both PJM and ERCOT publish their interconnection queues, and several sites will show you a copy. A snapshot answers "what is filed today". It cannot answer the question that actually matters to someone choosing a site: is this project moving, or has it stalled?
Queue Wire compares each published snapshot against the last one and records only the differences — requests that advanced a status, requests that went to withdrawn or cancelled, and requests whose filed capacity was restated. That record does not exist in the published data. It only exists if somebody stores the old snapshot and diffs it, which is what this pipeline does every week.
What a change does not tell you. A request leaving the queue does not mean capacity is obtainable at that location. Deliverability depends on thermal and voltage limits, upgrade obligations and the rest of the study cluster — none of which the queue data reports. Every figure here is nameplate MW as filed, and every status is the ISO's own label.
The weekly delta report
Generated from the pipeline, published as-is. Expand any week to read it without leaving the page.
August 31, 2026
Queue Wire — weekly interconnection queue delta
Scan executed: 2026-08-31 14:35:19 UTC
ISOs processed: cached
Run ID: 20260831110054_d9a305
Projects evaluated: 0
Nameplate MW as filed on requests that went terminal (≥ 50 MW): 490.5 MW
Commentary mode: offline
How to read this. Every line below is a change between two published queue snapshots. A request moving to a terminal status is removed from the study queue; it does not follow that capacity became available at that location, because deliverability depends on thermal and voltage limits, upgrade obligations and the rest of the study cluster, none of which the queue data reports. Figures are nameplate MW as filed. Verify with the ISO before relying on anything here.
Requests moved to terminal status
Dequine - Eugene — Fountain County, IN (PJM)
Nameplate MW as filed: 490.5 MW across 2 request(s)
| Queue ID | Project | Resource | kV | MW as filed | Status change |
|---|---|---|---|---|---|
| C01-2193 | Dequine - Eugene 345 kV | Storage | 345 | 250 | Active → Withdrawn |
| C01-2192 | Dequine - Eugene 345 kV | Solar | 345 | 240.5 | Active → Withdrawn |
What this records: A 490.5 MW Storage, Solar request at the 345 kV level at Dequine - Eugene, Fountain County, IN is recorded in a terminal status in the latest PJM queue publication, where it was previously active. This removes that request from the study queue; whether any capacity is obtainable at this location depends on thermal and voltage limits, deliverability rights and upgrade obligations that the queue data does not report, so it must be confirmed with PJM directly.
New requests entering study (>100 MW)
No new requests above 100 MW appeared in this run.
Status changes
Direction is not inferred. The ISO publishes status as a label, and the labels do not form a strictly ordered sequence, so both values are shown as filed and the reader judges whether it represents progress.
| ISO | Queue ID | Project | Status was | Status now |
|---|---|---|---|---|
| PJM | AC1-065 | Walnut Solar I | Under Construction | Partially in Service - Under Construction |
LinkedIn Post Snippet
Queue Wire: 490.5 MW of filed nameplate capacity moved to terminal status in the PJM and ERCOT interconnection queues this week.
• Dequine - Eugene (Fountain County, IN — PJM): 490.5 MW as filed
What that does and does not mean: those requests are out of the study queue. It does not follow that capacity is obtainable at those locations — deliverability turns on thermal and voltage limits, upgrade obligations and the rest of the study cluster, none of which the queue data reports.
The reason I track the deltas rather than just the queue: a snapshot tells you what is filed, while the week-over-week change tells you which requests are moving and which are not.
Also in the diff: 1 status change(s) on existing requests, shown as filed rather than as progress — ISO status labels do not form a strictly ordered sequence.
Sourced from public PJM and ERCOT queue filings. Screening aid only.
#DataCenters #SiteSelection #PJM #ERCOT #EnergyInfrastructureAugust 27, 2026
Queue Wire — weekly interconnection queue delta
Scan executed: 2026-08-27 23:09:50 UTC
ISOs processed: PJM, ERCOT
Run ID: 20260827230912_de4fbb
Projects evaluated: 11,965
Nameplate MW as filed on requests that went terminal (≥ 50 MW): 0 MW
Commentary mode: offline
How to read this. Every line below is a change between two published queue snapshots. A request moving to a terminal status is removed from the study queue; it does not follow that capacity became available at that location, because deliverability depends on thermal and voltage limits, upgrade obligations and the rest of the study cluster, none of which the queue data reports. Figures are nameplate MW as filed. Verify with the ISO before relying on anything here.
Baseline run. This scan established the historical record for 11,965 projects across both ISOs. Week-over-week deltas begin with the following scan; this report is retained so the start of the record is visible.
Sources:
- PJM: serial 9263 (live:PlanningQueues.xml) + cycle 1792 (live:GenerateExcelTransitionProjectsAll), 917 superseded dropped -> 10138 unified
- ERCOT: live:GIS_Report_July2026 (published 2026-08-03T15:39:49-05:00) -> 1827 projects, 15 cancelled, 170 inactive
Requests moved to terminal status
No requests at or above 50 MW moved to a terminal status in this run.
New requests entering study (>100 MW)
Suppressed on the baseline run — every project looks "new" against an empty database. Real entries appear from the next scan.
LinkedIn Post Snippet
Queue Wire: no requests above 50 MW moved to terminal status across PJM and ERCOT this cycle.
A quiet week is still a data point. Study positions held, and nothing ahead of the current cluster changed in the published data.
Sourced from public PJM and ERCOT queue filings. Screening aid only.
#DataCenters #SiteSelection #PJM #ERCOT #EnergyInfrastructureReports are generated weekly. Only 2 reports exist so far — tracking began August 27, 2026, so the archive is short by design.
Every change tracked so far
4 changes since August 27, 2026. The first scan stored the baseline for 3,054 requests; because there was nothing to compare it against, those first observations are not counted as changes. Full change log →
| Detected | ISO | Change | Request | MW as filed | Status was → now |
|---|---|---|---|---|---|
| 2026-08-31 | PJM | Terminal status | Southern Ocean Waretown Solar AG1-189 · Ocean County, NJ |
5.1 | Engineering and Procurement → Pending Termination |
| 2026-08-31 | PJM | Status change | Walnut Solar I AC1-065 · King and Queen County, VA |
n/a | Under Construction → Partially in Service - Under Construction |
| 2026-08-31 | PJM | Terminal status | Dequine - Eugene 345 kV C01-2193 · Fountain County, IN |
250 | Active → Withdrawn |
| 2026-08-31 | PJM | Terminal status | Dequine - Eugene 345 kV C01-2192 · Fountain County, IN |
240.5 | Active → Withdrawn |
Coverage
Two ISOs today. Each is tracked separately because the schemas are not comparable — PJM publishes discrete statuses, ERCOT publishes composite milestone strings.
PJM
Updated continuously; source regenerated on demand.
10,138
requests in the queue
- Active (non-terminal)
- 2,912
- Changes tracked
- 4
- Feed
- live
ERCOT
Published monthly; data can be up to ~30 days old.
1,995
requests in the queue
- Active (non-terminal)
- 1,827
- Changes tracked
- 0
- Feed
- live
MISO, Southeast, SPP, CAISO
not covered yet
—
on the roadmap
- Next
- MISO
- Then
- Southeast
- After
- SPP, CAISO