The Data-Center Pause Has Climbed From County Boards to Congress
In eighteen months the instrument went from a township's 180-day pause to a governor freezing an interconnection queue and a bill in both chambers of Congress. Each rung up the ladder is harder to route around than the one below it.
If you have been managing data-center siting risk the way this industry learned to manage it — jurisdiction by jurisdiction, board by board — you have been solving the 2024 version of the problem.
Watch what the instrument has done in eighteen months. It started as a township pause. It is now a bill in both chambers of Congress, and in Texas it is a letter that stopped roughly a quarter of a trillion watts of interconnection requests in their tracks.
Each rung up that ladder is harder to route around than the one below it. A county you can trade for a neighbouring county. A grid operator you cannot.
Rung one: the local pause
This is the layer everyone knows. A township adopts a 180-day moratorium while it writes an ordinance. A county freezes acceptance of applications. Michigan alone reached 51 cities and townships covering about 1,500 square miles, and Maryland reached 13 counties. It is disruptive, it is survivable, and it is geographically escapable — which is exactly why it stopped being the whole story.
Rung two: the state executive
On August 3, 2026, Governor Greg Abbott wrote to the chairman of the Public Utility Commission of Texas and the chief executive of ERCOT directing a "comprehensive verification and audit of all data centers advancing through ERCOT's interconnection process," to occur before any additional data centers are approved to move forward. Projects found in violation of PUCT, ERCOT or state-law requirements "must be denied connection to the Texas grid."
The letter put the scale plainly: ERCOT is weighing roughly 474 gigawatts of interconnection requests, about ninety percent of them data centers. (Houston Public Media, August 3, 2026; Texas Tribune)
ERCOT's response is the part to read, because it is the primary record and it is unambiguous. In market notice M-A080326-01, "Update Regarding Batch Zero Timelines and Processes," issued August 3, 2026, ERCOT stated it "will not notify each Interconnecting Distribution Service Provider and Transmission Service Provider of how any Large Load is classified in the Batch Zero Interconnection Study by August 7, 2026," citing the Governor's letter directing it to "conduct a verification process before advancing any data center Large Loads through the interconnection process." ERCOT said it would seek a good-cause exception from the PUCT ahead of the commission's August 20, 2026 open meeting. (ERCOT Market Notice M-A080326-01)
No ordinance. No hearing. No vote. One letter, and the queue stopped.
Rung three: Congress
On March 25, 2026, Senator Bernie Sanders announced the Artificial Intelligence Data Center Moratorium Act, which would impose a federal moratorium on AI data centers until national safeguards are in place — safeguards the sponsors frame around consumer energy costs, environmental harm, worker displacement and civil rights. The bill would also bar U.S. exports of AI computing infrastructure to countries without comparable safeguards. (Office of Senator Bernie Sanders)
Representative Alexandria Ocasio-Cortez introduced the House companion on June 24, 2026, which would hold the pause in place "until Congress passes comprehensive legislation to address the economic, environmental, and safety impacts of artificial intelligence." (Office of Representative Ocasio-Cortez)
Neither bill is close to law, and a federal moratorium on a buildout this economically entrenched is a long shot in any Congress. That is not the point. The point is that the idea has finished travelling. It is no longer something a frustrated township does; it is a national legislative position with named cosponsors, and it gives every county board in America language to borrow.
What our data does and does not see
SitePath county data-center records, as published. Counts county-level records only, so municipal and township action is undercounted.
View as table
| Category | Value |
|---|---|
| Georgia | 10 counties |
| North Carolina | 7 counties |
| Michigan | 7 counties |
| Maryland | 3 counties |
| Colorado | 2 counties |
| Iowa | 2 counties |
| Wisconsin | 2 counties |
| Idaho | 1 counties |
| Indiana | 1 counties |
| Kentucky | 1 counties |
Our county records capture rung one well and rungs two and three not at all. That is a structural limitation worth stating plainly: a county-level dataset can tell you that Georgia and Michigan are tightening, and it cannot tell you that the binding constraint in Texas is now an audit at the grid operator. On the day Abbott's letter landed, Texas held 100 data-center county records in our dataset and not one of them in a restrictive posture — because by every land-use measure, that is true. It was also, that morning, beside the point.
What it means
Diligence has to cover three layers now, not one. Zoning posture, state executive and regulatory action, and federal legislative risk. A site can be clean on the first and stopped on the second.
Speed at the grid layer is the scarce asset. Roughly 474 GW of requests sit behind a Texas process expected to run months. If you hold a queue position in another market, it repriced upward this month — not because anything improved there, but because the alternative got slower.
The higher the rung, the less your local relationships help. Years of goodwill with a county board is a real asset and it buys you nothing at a PUC docket. Different institution, different evidence, different advocates.
Watch which states have a lever already built. Texas did not need new legislation; the governor used an existing directive relationship with the PUCT and ERCOT. Massachusetts does not need a preemption law; the attorney general already reviews every town bylaw. The fastest-moving jurisdictions are the ones where somebody can act without waiting for a legislature.
What this analysis does not tell you
It does not predict whether the ERCOT audit clears quickly or slowly, which projects survive it, or what the PUCT decided on the good-cause request. It does not assess the federal bills' prospects, and it deliberately does not state their megawatt threshold or bill numbers: those circulate widely in secondary coverage but are not stated in the sponsors' own releases cited here, and we do not print a number we have not seen in the source. Our county records describe land-use posture only and carry no interconnection-queue status — the layer that decided this story.
Published from the SitePath editorial desk on August 21, 2026. Claims are traced to primary documents and to records already in the SitePath dataset; source links appear inline. Material the source review could not confirm has been withheld from this page rather than published with a caveat — see methodology for how SitePath sources and scores what it publishes.