Interconnection Queues: What Moved Since the Last Reading

The newest row in this data is from August 23, 2026. Each grid carries its own "data through" date because the collector does not reach all six on the same day, and a grid that went quiet must not read as a grid that emptied out.

Across the 4 grids read within the last two days, 6,691 projects are listed for a combined 1,222,574 MW. 2 grids have not returned a row in over two days: ERCOT (last row 2026-07-30, 24 days ago), MISO (last row 2026-08-06, 17 days ago). Their figures above are the last reading we hold, not a current one, and their movement columns compare two readings from back then.

Why most of the movement columns are zero

1 of 6 grids moved against their own previous reading. Interconnection queues are republished on a slow cycle — some monthly, some when a study window closes — so a queue can go weeks with the same projects in the same stages.

The file itself is a poor guide to this. On several grids the queue file's bytes differ every single day while the projects inside are identical, because the spreadsheet carries a generation timestamp. The last column above ignores the file and fingerprints the queue: which project ids are listed, what stage each is in, and how big each is. It only moves when one of those does.

What the movement columns actually mean

Each column says what the operator's own published file did, not what the project did.

The largest single movers by name

MISO — largest id appearing for the first time in its 2026-08-06 reading: R5096 (AECC Dell East - Blytheville Elm St 161 kV), capacity not published in the queue file.

A name here is the name the grid operator published. We do not correct it, resolve it to a developer, or look up who owns it. Where a queue file leaves the capacity blank we say so rather than printing a zero, because 2,813 of the listed projects across all six grids carry no published capacity at all and a zero would fold them in with the genuinely tiny ones.

Where these numbers come from

Each grid publishes a queue file — a spreadsheet or a table — listing the projects waiting to connect. The clock fetches those files, stores the bytes with a hash, and writes one row per project per day. Nothing is edited afterwards, so any reading on this page can be rebuilt.

• Source: the interconnection queue file each grid operator publishes, fetched directly.

• Comparison: for each grid, the two most recent days that grid returned rows — printed above as its own "data through" date.

• Freshness on this page is the newest project row in the store. It is not the collector's run log: on August 23, 2026 that log reports every grid it asked for as collected and error-free, while ERCOT and MISO last returned data days earlier — the run stopped asking for them, so a green run and a dark grid are the same picture.

This page is rewritten from the source clock and keeps the same url every time. Data through 2026-08-23. Row hash 31476e50d036b3c136d281db83fbae27ae8dc593af7475ebf404790c29a2bedc. Machine-readable copies: CSV · JSON.

Something here look wrong? Reply to any page on this site with the row and the date and we will recheck it against the seal.