Interconnection queue changes in Connecticut

What this page is9,981 rows held · newest sealed read 2026-08-29

• This page is not part of the subscription. Over 79 days of collection this queue produced 1 named mover. We keep the dated copies and this page stays here, but we are not selling it, and the weekly file does not include it.
• 322 power projects in Connecticut sit in the newest copy we hold of each of these waiting lists: ISO-NE, NYISO.
• We hold 31 dated copies covering Connecticut, the first from 11 Jun 2026 and the most recent read on 29 Aug 2026, and 9,981 dated project rows inside them.
• Each operator here has its own newest copy: ISO-NE 29 Aug 2026 (321 projects); NYISO 29 Aug 2026 (1 project).
• Nothing in Connecticut changed between our newest copy and the newest copy at least a week older than it (ISO-NE 22 Aug 2026 → 29 Aug 2026; NYISO 22 Aug 2026 → 29 Aug 2026). The table above is the most recent set of moves we do hold, and every row names the two dates it sits between. We do not answer this with our last two copies any more: the newest two we hold are ISO-NE 1 day, NYISO 1 day apart, and finding nothing over one day is much weaker evidence than finding nothing over a week.
• The biggest single project in Connecticut in the newest copy is Non-controllable objective ETU to enable 2400 MW injection at 2,400 MW.

Real rows out of our sealed copies

These are rows we read out of dated copies we keep ourselves. The live source shows today only, so once a row moves, what it said before is gone from the place you would go to look.

Who published the data on this page

• Every row on this page was published by a grid operator, not by us. Written out in full, they are ISO New England and New York ISO. We keep dated copies of their public queue files; the projects, the names and the wording inside those rows are theirs.
• This file uses material published by the California ISO.
• Copyright © 2026 California Independent System Operator. All rights reserved.
• Their terms say "Most of the materials", not all. This file does not claim the Public Queue Report is inside that "Most".

What this page cannot tell you

• An ISO-NE move on this page is never a status change, and that is our fault rather than a gap in ISO-NE's file. ISO-NE does publish a status on its rows. We save the wrong column out of the file, so the status is empty on all 54,162 ISO-NE rows we hold and no page here can see a status change. We are fixing our end. Size and in-service date are read correctly and are what an ISO-NE move here is made of.
• When NYISO moves a project onto its withdrawn sheet, the in-service date disappears from the file, because that sheet has no such column. The date did not slip. We count that as the one withdrawal it is rather than a status change plus a date change, so 5 rows you might expect to see twice appear once.
• ISO-NE prints the same queue number on more than one line, so when one of those lines is dropped the project itself has not gone anywhere. We look for the queue number in the newer copy before we say a project left, which is why 2 rows that would otherwise read here as a departure are not shown. Every one of those queue numbers is still in the file today.
• The operators write the same fuel differently — Solar, SOL, SUN and S all appear for the same thing. The fuel column is our reading of their labels, not their own count, and a label we are not sure of is shown as not clear rather than guessed at.
• A move here means two dated copies of the same public file disagree. It is not a decision, an approval, or a filing. If you need to know why a project moved, the operator is the place to ask, not us. Email operations@ustechautomations.com and we will send you both dated copies so you can check ours.

More from this feed

• Up one level: Queue changesThe whole feed, its price, and how the file arrives.
• What is and is not in this feedEvery source we read for it, how often, and the ones we refuse to collect.