ISO Queues Overwrote Last Week. Here Is What Changed [2026]

The six United States ISO interconnection queues — CAISO, ERCOT, ISO-NE, MISO,
NYISO, and SPP — publish their queue reports in place. Each new report replaces
the previous one. None of the six maintains a public archive of prior versions,
which means that when a project's status changes, the evidence of what it said
last week is gone unless someone kept a copy.

We keep a copy. Since June 11, 2026 we have taken a weekly snapshot of all six
queues — nine snapshots held so far — and diffed each week against the last.
This page is one week of that feed, published in full: every number below was
counted from our archived copies of the ISOs' own published queue reports,
retrieved on July 23 and July 30, 2026. Where our archive cannot support a
claim, we say unknown; nothing on this page is estimated.

The week in numbers: July 23 → July 30, 2026

Counted across the 12,327 project rows present in the July 30 snapshot:

The distribution is lopsided on purpose — that is what queue data actually
looks like. Of the 118 status changes, 116 were in MISO, one in SPP, and one in
CAISO. ERCOT, ISO-NE, and NYISO published no status changes between our two
retrievals. A quiet week in a queue is a real fact, and it is only provable if
you hold both versions.

The one that disappeared quietly

The single CAISO change this week is the kind the overwrite practice hides
best: queue position 1806, CAPTIVA ENERGY STORAGE, a 250 MW battery project in
California, moved from ACTIVE to WITHDRAWN between July 23 and July 30. The
CAISO report now simply lists it as withdrawn; the fact that it was still
active on July 23 exists only in archived copies. If your pipeline analysis,
offtake shortlist, or competitive map still counts that project as active, the
public record will not correct you — it already moved on.

MISO's batch: 116 revisions cleared

The 116 MISO changes are not 116 independent market events, and it would be
dishonest to present them that way. The bulk are projects moving from "Pending
Revision Approval" or "Pending Transfer" to "Active" — an administrative batch
in which MISO cleared a backlog of pending revisions in one reporting cycle.
The individually notable part is which projects came out the other side as
active, and at what scale. The largest by reported capacity:

Project names, capacities, and statuses are as MISO reported them in its own
queue report on the retrieval dates; we do not adjust or normalize the ISO's
figures. Arkansas readers will notice three 375 MW solar entries on the same
McNeil corridor clearing in the same week — the kind of clustering that is
obvious in a diff and invisible in a point-in-time table.

Six new entries, most of them nearly blank

The six rows that appeared for the first time in the July 30 retrievals are a
useful lesson in what queue reports actually contain on day one. SPP added two
Kansas generation requests, GEN-2026-SR30 at 504 MW and GEN-2026-SR29 at
196.56 MW, both in "Special Study" status — capacity and state reported, fuel
type not yet published. MISO added four rows — S1164 (Dell–Manila 161 kV),
R5095, R5094, and J4249 — all listed as Active with no reported capacity, no
fuel, and in three of the four cases no project name at all. We publish those
blanks as blanks. Where the ISO's report leaves a field empty, our feed leaves
it empty; a data vendor that quietly fills in "0 MW" or guesses a fuel type is
manufacturing facts, and you would have no way to tell. New entries usually
gain detail in later reports, and because we keep every version, the date each
field first appeared is itself part of the record.

Why point-in-time queue tables mislead

Anyone can download today's queue report from any ISO, and plenty of sites
republish those tables. The table is not the product. The problems a queue
table cannot solve, because they live between two versions of it:

1. Withdrawals are silent. A project that leaves ACTIVE status does not
   announce itself. This week that was CAPTIVA — knowable only by comparison.

2. Status transitions carry timing information. A batch of revisions
   clearing tells you the queue administrator moved; a single project advancing
   tells you the developer did. Both are dated events, and the date is the
   analytically useful part.

3. A quiet week is unprovable without the archive. Zero exits across all
   six ISOs this week is a checkable claim only because both retrievals are
   content-hashed in our archive. "No news" from a source that overwrites
   itself is otherwise indistinguishable from "didn't look."

If you are a developer tracking competitors in a cluster study, an analyst
maintaining a project pipeline model, a landman working transmission
corridors, or a consultant whose deliverable quotes queue positions, the diff
is the part of the record you currently reconstruct by hand — or lose.

How the archive works

The method is deliberately boring. Once a week, an automated collector
retrieves the current public queue report from each of the six ISOs and stores
the file as retrieved, content-hashed, alongside every previous retrieval.
Each project row is keyed by ISO and queue position, and the fields we track
are the ones the ISOs themselves publish: project name, status, fuel type,
reported capacity in megawatts, and state. The weekly diff is a straight
row-by-row comparison of the two most recent retrievals — a status change is
reported only when the same queue position shows different status text in the
two files, a new entry only when a queue position exists in the later file and
not the earlier one, and an exit only when the reverse is true.

Two limitations are inherent to the cadence, and we would rather you hear them
from us: a status that changes and reverts inside a single week is invisible
to a weekly diff, and the diff dates a change to the retrieval window — we can
say a project moved between July 23 and July 30, not on which day. A
collection failure is also not the same fact as a quiet week; if a retrieval
ever fails, that ISO's column reports unknown for the window rather than
zero changes.

How to get this feed

The path from this page to the ongoing feed has three steps, and only the
third one costs money:

1. This weekly brief — free, published from the same archive that fulfils
   the paid service, so you can judge the data quality on a real week before
   anyone asks for an email address.

2. The free sample on the service page — the current week-over-week diff
   for all six ISOs in one file, with per-row retrieval provenance, so you can
   check our counts against any copy of the reports you kept yourself.

3. The Interconnection queue sentinel — the paid subscription, $175 per
   month, billed monthly, cancel any time: every week, what changed in all six
   queues — status moves, commercial-operation-date shifts, capacity changes,
   entries and exits — each row carrying its source retrieval dates, delivered
   to you before the ISOs overwrite the evidence again. Checkout opens by
   emailed invoice link from the request form on the service page; we reply
   the same working day.

Both the sample and the subscription live on the
Interconnection queue sentinel service page,
and the rest of what we sell from this archive is priced on the
services index.

Provenance and terms

US Tech Automations is a data and automation company. We are not affiliated
with, endorsed by, or speaking for CAISO, ERCOT, ISO-NE, MISO, NYISO, SPP, or
any ISO or RTO. Every figure above comes from our archived retrievals of the
ISOs' publicly published queue reports on July 23 and July 30, 2026; each
archived report is content-hashed at retrieval so an auditor can confirm the
file we diffed is the file the ISO published. Queue data describes requests to
interconnect, not built generation, and a queue position is not a guarantee a
project will be constructed. Nothing on this page is legal, engineering,
investment, or financial advice, and these are our own service terms — not a
government fee or filing charge. If a future correction changes any count on
this page, the correction will be dated and the original left visible.