Weekly Briefing: Data Centers

New York supplied the week’s clearest policy break. Governor Kathy Hochul imposed a one-year pause on state environmental reviews for proposed data centers above 50 megawatts while directing the Department of Public Service to develop a standardized impact assessment and permitting process. As WIRED reported, the action is narrower than legislation built around a 20-megawatt threshold, but its significance lies in its scale. A debate previously handled project by project is now being treated as a statewide infrastructure question.

That distinction matters because local governments are being asked to judge consequences that rarely remain local. A single project can affect regional generation, transmission investment, water systems and electricity rates, yet the available tools are often zoning hearings, temporary moratoriums and court challenges. New York’s response, Maryland’s widening use of pauses, Ohio ballot initiatives and Nashville’s pending restrictions all point to the same governance gap. The emerging policy model is not necessarily a permanent ban, but a pause used to create rules that ordinary land-use processes were never designed to supply.

Opposition also acquired organizational and electoral weight. Reuters documented a coordinated protest effort spanning at least 125 U.S. locations, while reporting from Maryland showed data center disputes influencing county primaries. Sunbury voters will consider a charter amendment limiting facilities above 25 megawatts, and Springfield organizers pursued a related restriction. These are different mechanisms, but together they show resistance moving beyond public-comment meetings into elections, ballot measures and shared national messaging.

The week also clarified that much of the resistance is directed at the terms and pace of development rather than at data centers in the abstract. Polling reported by Axios and POLITICO showed growing concern, particularly around nearby construction, utility costs and resource use. At the same time, projects in Michigan and Nashville continued to advance despite opposition. The Saline Township Stargate project proceeded after litigation and a settlement containing water and noise restrictions, farmland preservation and roughly $14 million in community benefits. The practical contest, then, is increasingly over who bears the costs and what protections are enforceable—not simply whether a facility is built.

Electricity costs are becoming the bridge between technical constraints and mass politics. Reuters reported that the White House plans to bring utilities and major developers together around a voluntary commitment intended to prevent AI-driven grid costs from reaching other customers. Wisconsin regulators, meanwhile, had already required data centers to cover the full cost of a proposed gas plant intended to support rising demand. The direction is becoming clearer: political acceptance will increasingly depend on project-specific responsibility for generation, grid upgrades and reserved capacity. What remains unclear is whether voluntary promises can substitute for binding utility rules.

The xAI buildout around Memphis and Southaven remains the sharpest warning about what happens when speed outruns conventional infrastructure. Reporting from Reuters described dozens of gas turbines installed for Colossus 2 amid a dispute over federal air permits; residents separately sued over noise and vibrations, while the NAACP and environmental lawyers pursued Clean Air Act claims. This is more than an isolated compliance fight. It illustrates how projects unable to secure grid power on their preferred timetable can transfer risk into onsite generation, neighborhood exposure and litigation.

Water concerns are following a similar path from general anxiety toward specific policy design. University of Colorado Boulder researchers, covered by Axios, found states experimenting with reporting requirements, potable-water limits, technology incentives and water-rights conditions. The Atlantic also highlighted how limited disclosure makes facility comparisons difficult and how lower direct water use can require more electricity. Research on immersion cooling above 700 watts per chip underscores the engineering pressure behind these choices, but it does not yet establish a market-wide deployment shift. The larger lesson is that cooling, power and permitting can no longer be evaluated separately.