Climate
Privacy
Bob Dylan
Drones
Data Centers
AI Governance
2026 Maine Senate Race
Data Center Moratoriums And Grid-Cost Rules Keep Spreading
Yesterday’s data center news again centered less on new capacity than on the conditions being placed around it. Local governments, state lawmakers, utilities and investors are all trying to narrow the gap between AI buildout demand and the practical limits of power access, water disclosure, generator impacts and public cost exposure.
This continues the pattern of the past week: more decisions are moving earlier in the project cycle, before full applications, final utility commitments or construction starts.
Lodi, California backed away from a proposal to study data center viability and moved toward a possible moratorium instead. The shift followed community feedback, and the city’s electric utility said a Northern California Power Authority study would be needed to assess whether data centers would worsen transmission-line congestion.
Henderson, Nevada weighed a 180-day pause on data center permit approvals while staff studies code changes for air quality, heat generation, siting requirements and decommissioning plans. The debate came against a hard utility backdrop: NV Energy said it has received requests for 39 data center projects totaling 16,530 MW, roughly double the utility’s combined peak load capacity of 8,241 MW.
California’s regulatory fight remained unsettled. Gov. Gavin Newsom vetoed a bill requiring proposed data centers to estimate water use under penalty of perjury, while other measures advanced on grid-upgrade tariffs, CEQA exemptions, water-use estimates before business-license applications, and monthly water and fuel reporting. Imperial County’s 45-day moratorium and litigation around a 950,000-square-foot proposal kept the local dispute active.
Pennsylvania coverage tied local permitting fights to grid and cost-allocation debates. FERC activity addressed tariff justification and faster integration of large loads, PJM issued a hot-weather alert, Maryland lawmakers advanced a transmission-cost complaint at FERC, and Pennsylvania lawmakers considered data center standards, virtual power plant authorization and conditions for state tax credits.
Verse raised $54 million in Series B financing for software and on-site battery systems meant to make AI data center loads more flexible and easier to integrate with the grid. NVIDIA backed the round, and Verse is partnering with Calibrant Energy to finance and deploy battery assets.
In Ohio, the failure of House Bill 646 continued to expose a split over large data center tax incentives. The dispute centered on a sales tax exemption worth billions and on rural concerns about farmland loss, industrialization and long-term local impacts.
Key Points
- Local governments are using pauses and code reviews as a first response to uncertainty, rather than waiting for fully developed applications. Lodi, Henderson, Minneapolis and Imperial County all reflected some version of that approach.
- Utilities and regulators are moving cost responsibility into formal rules. FERC tariff work, Maryland’s complaint, California’s proposed corporate tariff and Xcel Energy’s comments in Minneapolis all point to a stronger emphasis on shielding ordinary customers from large-load costs.
- Developers and investors are beginning to finance grid-flexibility tools as a response to interconnection delays. Verse’s battery-backed load-management model is notable because it treats power access as a project-development bottleneck, not just an energy-procurement issue.
- Water and cooling questions are becoming disclosure and permitting problems, not only engineering problems. California’s bill package, Lodi’s recycled-water discussion and Nevada’s cooling limits all show local and state officials asking for more proof before projects advance.
Implications
Site control is becoming less decisive on its own. Projects increasingly need credible answers on power costs, transmission congestion, water use, backup generation, noise and local fiscal terms before they can move smoothly through approvals.
Moratoriums may slow near-term permitting, but they can also produce clearer zoning, utility and disclosure rules if jurisdictions use the pause to define standards rather than simply defer conflict.
Flexible-load and battery-backed approaches could become more important if utilities accept them as reliable tools for integrating large data center demand. For now, they remain a promising workaround that still needs regulatory and operational validation.
Watchpoints
Watch
Whether Henderson adopts the 180-day pause and how broadly any code revisions cover backup generators, heat, siting and decommissioning.
Watch
How California’s remaining data center bills fare after Newsom’s veto, especially the proposed grid-upgrade tariff and restrictions on CEQA ministerial exemptions.
Watch
What FERC, PJM and state regulators do next on large-load tariffs, transmission cost complaints and interconnection rules for data center demand.
Fallout
The strongest developments yesterday were around local siting control, power cost allocation, water disclosure and the public bargain behind data center incentives. The day did not bring a single major construction milestone; it showed more jurisdictions trying to define the terms under which large AI-related loads can connect, build and receive public support.
Local Siting Control
Local governments are increasingly deciding whether data centers advance through zoning, moratoriums, hearings, exemptions and project-specific conditions. That authority is becoming more important as projects raise concerns about electricity demand, water use, noise, diesel generators and land-use change.
Fresh developments
Lodi moved from exploring data center viability toward a possible moratorium after community pushback. Henderson considered a 180-day permit pause to study air-quality, heat, siting and decommissioning rules. Minneapolis had already approved a six-month pause with an exemption for smaller downtown projects, while Imperial County’s 45-day pause and litigation around a large proposed facility kept California’s local-control fight active. Pennsylvania coverage also described multiple municipal disputes involving zoning hearings, intervenors, noise and backup diesel generators.
Why we noticed
The pattern matters because local pauses are no longer isolated protest gestures. They are becoming a practical governance tool for cities and counties that lack clear data center rules but are being approached by developers or utilities before impacts are fully understood.
Watch for:
- Whether temporary moratoriums convert into durable zoning standards or simply extend uncertainty.
- How exemptions are written for downtown conversions, smaller facilities or already-permitted projects.
- Whether developers respond with litigation where local rules block or delay projects.
Power Cost Allocation
Utilities and regulators are trying to decide how data centers should pay for the generation, transmission, reserves and reliability costs their loads require. The debate affects ratepayer protection, project economics and the speed of interconnection.
Fresh developments
Pennsylvania coverage highlighted FERC activity on tariff justification and measures to speed large-load integration, a PJM hot-weather alert, Maryland’s transmission-cost complaint at FERC, and state proposals tied to data center standards and tax-credit conditions. California lawmakers advanced SB 886 to create a corporate tariff for data center-related grid upgrades. In Nevada, NV Energy’s reported 16,530 MW of data center project requests underscored how quickly proposed load can exceed existing system scale. Verse’s $54 million raise showed investors backing flexible-load and battery systems as one possible way to reduce interconnection friction.
Why we noticed
The issue is moving from broad concern about grid strain into tariff design, complaint proceedings, utility studies and private financing. That is where project feasibility will increasingly be tested: who pays, how much collateral is required, whether loads can be flexible and whether ordinary customers are protected.
Watch for:
- FERC and PJM treatment of large-load tariff justification and queue acceleration.
- Whether California’s corporate tariff proposal advances and how it defines data center responsibility for grid upgrades.
- Whether utilities credit on-site batteries and flexible operations enough to improve interconnection timelines.
Water Supply Constraints
Water is becoming a central constraint for data center siting, cooling design and public acceptance. The issue includes direct facility consumption, recycled-water options, cooling restrictions, drought exposure and public disclosure of water use.
Fresh developments
California remained the clearest test case. Newsom vetoed one water-use estimate bill, but other measures advanced that would require estimates before business-license applications and monthly reporting of water and fuel consumption. Lodi’s discussion included possible siting near wastewater facilities or White Slough to use recycled water, but the council moved toward a moratorium instead. Henderson’s debate occurred in a region with an evaporative-cooling ban, while the Southern Nevada Water Authority argued that data centers can be built without consuming more water under existing constraints.
Why we noticed
The water discussion is becoming more specific. Officials are not only asking whether data centers use too much water; they are asking what must be disclosed, what cooling systems are allowed, whether recycled water changes the equation and how water issues interact with permits and local trust.
Watch for:
- Whether California lawmakers can pass narrower water-disclosure rules after Newsom’s veto.
- How local governments treat recycled-water proposals when power and land-use concerns remain unresolved.
- Whether cooling restrictions in dry regions become a competitive advantage for lower-water designs or a constraint on project economics.
Community Benefit Bargains
Data center projects often depend on tax incentives, abatements, infrastructure commitments and promised local benefits. The bargain is under sharper scrutiny because capital investment is large, permanent employment is comparatively modest and public resource demands can be significant.
Fresh developments
Ohio’s failed House Bill 646 kept attention on the cost of data center tax exemptions, with lawmakers split over whether incentives worth billions should continue for very large corporations. Pennsylvania lawmakers considered conditions for state data center tax credits, including transparency and sustainability requirements. In Nevada, advocates debated possible fee structures to offset tax abatements. Minneapolis showed a different side of the bargain: downtown property owners are looking at data centers as a reuse option for vacant office space, while the city’s pause creates an exemption for smaller downtown projects.
Why we noticed
The incentive debate is becoming less automatic. States and cities still want investment, reuse opportunities and tax revenue, but they are increasingly attaching questions about public costs, utility burdens, land use and community impacts to any economic-development package.
Watch for:
- Whether Ohio lawmakers revisit data center tax exemptions after the bill failure.
- How Pennsylvania ties tax-credit eligibility to transparency, sustainability or grid conditions.
- Whether cities use fees, community payments or narrower exemptions to make projects more politically acceptable.
Final Thought
The day did not produce a single defining project win or rejection. It did show that more of the data center buildout is being decided before construction starts: in utility studies, tariff language, moratorium scopes and disclosure rules.