Climate
Privacy
Bob Dylan
Drones
Data Centers
AI Governance
2026 Maine Senate Race
Data Center Pushback Hardens Into Moratoria, Lawsuits, And Rate Cases
Yesterday’s data center news was less about new capacity moving forward than about the terms under which future capacity will be allowed to move at all. The concrete developments were pauses, lawsuits, rate proceedings, and certification disputes: a proposed rural moratorium in Hamilton County, another county moratorium reported by WVLT, legal challenges in Florida and California, and a West Virginia fight over whether a 5.2 GW project must clear a state High Impact data center process.
That matters because opposition is no longer sitting outside the development process. It is entering the process itself through moratoria, rate design, water rights, noise studies, state certification rules, and federal large-load proceedings. At the same time, Reuters reported that US Energy Secretary Chris Wright urged data center supporters to push back more forcefully against critics, a reminder that the buildout is now as much a public-acceptance challenge as an engineering and financing one.
Local governments kept using temporary pauses as practical control tools. Local 3 News reported that Hamilton County Mayor Weston Wamp proposed a one-year moratorium on rural data centers while the county meets with utilities and residents about power and water demand. Separately, WVLT reported a six-month moratorium that pauses permits, zoning approvals, building approvals, utility extensions, and development agreements for new projects. These are not final data center policies, but they change project timing immediately.
The legal front widened around ordinary permitting questions that now look anything but ordinary. WUSF detailed a lawsuit over a proposed 1,300-acre AI hyperscale project near Fort Meade, where plaintiffs allege the city failed to follow a state-mandated review process and did not adequately notify affected residents. Business Insider reported on litigation tied to a proposed 330 MW Imperial Valley project seeking access to Colorado River water, with filings saying the facility would require 287 million gallons. Both cases show how noise, notice, and water sourcing can become project-level vulnerabilities after local approval.
Power access continued moving from bilateral utility negotiation into formal public process. Foley & Lardner’s review of FERC’s June 18 show-cause orders highlighted the federal push to reform how six regional grid operators handle large loads of 20 MW or more, including co-located load and behind-the-meter generation. In Montana, Montana Free Press reported that NorthWestern Energy’s proposed large-load tariff has drawn nine intervention requests, including consumer, environmental, local-government, and power-sector interests. The common issue is not whether data centers need power; it is who studies, serves, and pays for that demand.
West Virginia added a state-authority complication to the project-risk picture. The West Virginia Press Association reported that the Department of Commerce told Fundamental Data LLC its planned 5.2 GW Ridgeline complex requires High Impact data center certification and missed an application deadline, while the company argued the rule and deadlines do not apply and that microgrid certification is voluntary. For very large campuses, the entitlement path now runs through more than land, taxes, and interconnection queues.
The political temperature rose at the national level. Reuters reported that Energy Secretary Wright, speaking at an Amazon Web Services conference, urged data center backers to respond to critics and compared the fight to opposition to fracking. That same reporting noted weak public support for fast construction in polling, while Planetizen cited a Gallup finding that 75% of Americans oppose data centers near their homes. The industry’s growth case remains strong, but the public case is not yet winning by default.
Cooling technology offered a quieter but important counterpoint. The Illinois News Bureau reported on University of Illinois researchers proposing aquifer thermal energy storage for data center cooling, using underground formations to store and reuse heat. The approach could matter because cooling electricity can account for 10% to 40% of total data center energy depending on design. But the researchers identified economics, not science, as the main barrier, which is the distinction that matters for developers: useful technology still has to survive project finance.
Key Points
- Communities are moving from protest to procedure. The recurring pattern yesterday was not just residents objecting at meetings; it was residents, counties, and plaintiffs using moratoria, acoustic studies, lawsuits, and hearing records to slow or reshape projects before construction decisions become irreversible.
- Regulators are treating hyperscale load as a distinct category rather than a larger version of ordinary commercial demand. FERC’s large-load orders, Montana’s proposed two-tier tariff, and West Virginia’s High Impact certification dispute all point to a more formal separation between standard utility service and data center-scale power demand.
- Resource concerns are becoming more measurable. The Fort Meade plaintiffs commissioned an acoustical study. The Imperial Valley lawsuit attached a water requirement of 287 million gallons. Hamilton County’s proposed pause is explicitly tied to power and water planning. These details make opposition harder to dismiss as generalized unease.
- The industry’s defenders are becoming more openly political. Wright’s appeal to data center supporters suggests federal officials see public resistance as a material obstacle to AI infrastructure expansion, not just a local communications problem. The fact that Kevin O’Leary walked back claims about opponents and agreed to scale back a 40,000-acre Utah plan reinforces the point: rhetoric can collide quickly with permitting reality.
- Technical mitigation is gaining attention, but it is not yet replacing governance friction. Aquifer-based cooling, closed-loop designs, and alternative water sources may improve project viability, yet yesterday’s strongest developments were still legal, regulatory, and local-government actions.
Implications
Developers should expect to provide power, water, noise, and cost-responsibility answers earlier in the site process. Land control and economic-development promises are becoming insufficient where communities believe utility systems, aquifers, or nearby residents carry the risk.
Large-load tariffs and interconnection reforms may eventually create more predictable paths to service, but they are unlikely to mean faster approvals without new obligations. The direction of travel is toward clearer study requirements, cost-shifting protections, flexible-load treatment, and public review.
Water-constrained and agricultural regions face a sharper version of the data center siting problem. The Imperial Valley case is not simply about one project’s cooling plan; it raises the question of when water assigned for farming can be redirected to industrial compute infrastructure and who gets to decide.
Local pauses may become more common because they buy time without forcing a permanent yes-or-no decision. For counties that lack data center-specific rules, moratoria are becoming the practical bridge between surprise proposals and durable siting standards.
Public acceptance is becoming an execution risk. Polling opposition, lawsuits, and local moratoria do not stop the AI infrastructure buildout nationally, but they can change which projects move first, which jurisdictions become harder to finance, and which developers can credibly claim they have solved local impacts.
Watchpoints
Watch
Hamilton County commissioners’ July 1 consideration of the proposed rural data center moratorium and the scope of any utility or community review that follows.
Watch
Whether the six-month county moratorium reported by WVLT leads to permanent rules on noise, water use, power demand, and utility-cost exposure.
Watch
The 60-day responses to FERC’s show-cause orders, especially how PJM, SPP, and other grid operators propose to handle large-load studies, co-location, flexible service, and cost responsibility.
Watch
Montana Public Service Commission decisions on intervention requests and the structure of NorthWestern Energy’s proposed large-load tariff.
Watch
Next steps in the Fort Meade, Imperial Valley, and West Virginia disputes, particularly whether courts or agencies reverse approvals, block water access, or force certification.
Watch
Whether cooling approaches such as aquifer thermal energy storage move from research and discussion into project commitments that can affect permits or financing.
Fallout
Meaningful movement yesterday came in three long-running subjects: local control of siting, formal treatment of very large power loads, and water and cooling constraints. None of the day’s reporting showed a major new buildout breakthrough. Instead, it showed the approval environment becoming more procedural, more contested, and more dependent on resource-specific evidence.
Local Siting And Community Consent
Data center siting disputes increasingly turn on whether communities believe they had enough notice, enough operating detail, and enough protection from noise, water, and utility impacts before approvals were granted.
Fresh developments
Hamilton County’s proposed one-year rural moratorium, the six-month moratorium reported by WVLT, and the Fort Meade lawsuit all pointed in the same direction: local governments and residents are reaching for enforceable tools rather than relying only on public comment. Reuters’ reporting on Energy Secretary Wright’s call for supporters to push back against critics added a national political layer to what has often looked like a county-by-county fight.
Why we noticed
These moves matter because they affect project sequencing. A moratorium can delay a site before formal engineering or financing assumptions settle; a lawsuit can revisit whether an approval process was valid; and sustained public opposition can force developers to spend more time proving local compatibility before they can talk credibly about construction.
Watch for:
- Whether Hamilton County adopts the moratorium and how narrowly it defines rural data center projects.
- Whether local pauses become permanent siting, buffer, noise, water, or utility-disclosure rules.
- Whether the Fort Meade litigation forces a new review process or simply adds delay.
Large-Load Power Rules And Ratepayer Protection
As AI and cloud campuses ask for loads measured in tens, hundreds, or even thousands of megawatts, utilities and regulators are under pressure to decide how those customers should be studied, served, curtailed, and charged.
Fresh developments
Foley & Lardner’s analysis kept FERC’s large-load orders in focus, especially the treatment of loads of 20 MW or more and the push to avoid shifting costs onto other customers. Montana Free Press showed the same question moving through a state rate case, where NorthWestern Energy’s proposed tariff would separate 5 to 50 MW customers from loads above 50 MW and require longer commitments for the largest users. In West Virginia, the Ridgeline dispute added a certification question around a proposed 5.2 GW complex.
Why we noticed
Power access is no longer just a matter of finding a willing utility. The emerging question is whether a data center can clear the applicable tariff, certification, generation-adequacy, and cost-allocation process. That changes development risk because approvals can depend on regulators, consumer advocates, grid operators, and state agencies—not only on the developer and utility.
Watch for:
- What grid operators file in response to FERC’s orders and how they handle co-located load and flexible service.
- Whether Montana’s proposed tariff becomes a model for long-term commitments and usage floors for large loads.
- Whether West Virginia enforces High Impact certification requirements against the Ridgeline project.
Water And Cooling Strategy
Water use and cooling design are becoming central to whether data center projects are considered buildable, especially in agricultural regions, arid areas, and communities already concerned about utility and environmental burdens.
Fresh developments
Business Insider reported that Imperial Valley Computer Manufacturing sued after the Imperial Irrigation District denied access to Colorado River water for a proposed 330 MW AI data center. The project’s stated need for 287 million gallons put a hard number on a debate that often stays abstract. The Illinois News Bureau, meanwhile, reported on aquifer thermal energy storage research that could reduce cooling electricity demand and potentially use nonpotable or otherwise unsuitable groundwater sources.
Why we noticed
The contrast is useful. One story shows water rights and agricultural allocation becoming a legal obstacle to a specific project; the other shows researchers looking for ways to lower cooling burdens. Together they make clear that cooling is not a back-end engineering detail. It is increasingly part of site selection, local politics, and the financing case.
Watch for:
- Whether the Imperial Valley case clarifies who controls water reassignment from agricultural to industrial use.
- Whether developers begin attaching more specific cooling and water-reuse commitments to contested proposals.
- Whether aquifer-based cooling moves beyond research into pilot projects with data center operators.
Final Thought
The useful way to read yesterday is not as an anti-data-center turn, but as a shift in where decisions are being made. The decisive questions are moving earlier: before permits, before water assignments, before interconnection terms, and before communities accept that an AI campus belongs on ordinary industrial terms.