Climate
Privacy
Bob Dylan
Drones
Data Centers
AI Governance
2026 Maine Senate Race
Moratoria Put a 176MW Long Island Project in Limbo
Yesterday brought a clearer view of what the recent wave of data center controls does in practice. A proposed $1 billion, 176MW campus in Yaphank is now caught between New York’s one-year pause on large new facilities and Brookhaven’s 18-month moratorium. The state action was announced earlier; the clearest new development was its project-level consequence.
That does not amount to a broad construction retreat. Michigan’s $16 billion Stargate campus remains under construction despite litigation and opposition, while Google is still defending expansion plans in Chesterfield County. What increasingly separates moving projects from stalled ones is not demand for compute, but where they sit in the approval cycle and how specific their commitments are.
Datacenter Dynamics reported that Wildflower’s proposed 549,000-square-foot Long Island facility is in limbo under overlapping state and town pauses. The project’s planned 176MW load places it well above New York’s 50MW threshold, while Brookhaven is separately rewriting its rules for digital infrastructure. For developers, this is the practical risk of layered government review: clearing one jurisdiction may not keep a schedule intact when another is still writing its standards.
Google held two open houses for roughly 600 people in Chesterfield County, Virginia, where one campus is under construction and two more are proposed. Axios found that residents remained dissatisfied with the information available on approval status and ultimate water demand, while criticism of nondisclosure agreements continued. A coalition plans to deliver a petition with more than 2,000 signatures. The important point is not simply that opposition persists, but that engagement without decision-grade disclosure may do little to reduce it.
Ohio’s local campaigns continued moving beyond public comment. Cleveland.com reported that Sunbury residents secured a November charter vote on banning large data centers, part of a wider collection of local referendums, moratoria and recall efforts. Capacity thresholds—often aimed at facilities above 25MW—are allowing opponents to target hyperscale loads without opposing all technology development.
Pennsylvania’s policy response is becoming more concrete, although still incomplete. The Allegheny Front reported that budget provisions add scrutiny of electricity-demand forecasts, annual energy and water reporting, and consideration of advanced transmission technology. A separate House-passed bill would let municipalities impose temporary application pauses, but the Senate has not acted. The direction is toward measurable obligations and more local preparation, not a settled statewide regime.
Key Points
- State and local moratoria can compound rather than substitute for one another. The Yaphank proposal faces both a statewide environmental-permitting pause and a separate municipal rulemaking clock, making regulatory sequencing a site-development variable in its own right.
- Public engagement is becoming a test of specificity. Chesterfield residents asked about water demand, electricity costs, noise, air quality and the actual approval path; Google’s open houses did not resolve the central disclosure complaints. Communities increasingly appear to judge the process by whether it produces verifiable project details, not by the number of meetings held.
- Projects with advanced legal and development positions can still move. In Michigan, construction continues after a consent judgment added roughly $14 million in community benefits, water and noise restrictions, and land-preservation commitments. The settlement has not ended litigation, but it demonstrates how enforceable conditions can preserve a project pathway that ordinary rezoning did not.
- Infrastructure design is beginning to answer one part of the siting dispute. NVIDIA says its Rubin systems will use hotter closed-loop liquid cooling that can rely more heavily on dry coolers and avoid evaporative cooling components. If performance matches the design claims, that could reduce water and fan-noise exposure. It does not, however, reduce the underlying electricity load that is driving grid and cost concerns.
Implications
Early-stage site diligence now needs to account for moratorium exposure, application-completeness rules and overlapping state and municipal timelines alongside land, power and financing. A technically viable site can become unusable on the required schedule before any utility constraint is resolved.
Developers will have more difficulty relying on general assurances about closed-loop cooling, ratepayer protection or community benefits. The Chesterfield response and Pennsylvania’s reporting requirements both point toward a demand for project-specific numbers and commitments that can survive public and regulatory review.
The emerging policy model is broader than a ban. Pennsylvania is considering temporary pauses, reporting, incentive conditions and transmission review, while New York is studying differentiated power charges and self-supply requirements. These approaches could eventually create clearer development pathways, but during rulemaking they add uncertainty.
Cooling technology may improve the local water case for new AI facilities, especially where evaporative systems are politically or physically difficult. It is not a substitute for credible plans covering generation, interconnection, transmission costs and the allocation of risk to other customers.
Watchpoints
Watch
Whether Wildflower’s Yaphank application qualifies for any protection based on its existing status, and how Brookhaven treats the proposal while its local moratorium remains in force.
Watch
Chesterfield County’s response to the planned petition and whether Google provides firmer figures on water demand, electricity effects and the approval timetable.
Watch
Bridgeport Borough’s July 21 hearing on proposed definitions, conditional uses and development standards for data center campuses.
Watch
Whether Pennsylvania’s Senate advances municipal moratorium authority or the proposed GRID standards tying tax benefits to energy, water, workforce and community requirements.
Watch
New York’s forthcoming Community Investment Framework and the state’s work on higher electricity charges, self-supplied power and grid funding for large facilities.
Fallout
Meaningful movement centered on three long-running subjects: moratoria began affecting a specific project schedule, local opposition continued to move into formal political channels, and policymakers and technology suppliers offered more concrete—if still incomplete—answers on power, water and accountability.
Moratoria Become a Direct Schedule Risk
Temporary pauses are being used to prevent large projects from advancing while governments write rules for power demand, water use, environmental effects and community protections. Their significance depends heavily on thresholds, exemptions and whether existing applications are considered complete.
Fresh developments
Wildflower’s planned 176MW campus near Yaphank became the clearest example of the consequences. New York’s one-year pause applies to large new facilities, while Brookhaven’s separate 18-month moratorium runs through January 2028. Even if one process resumes, the other may continue to constrain the project.
Why we noticed
The overlap changes how sites should be valued. Regulatory timing is no longer merely a permitting estimate added after site selection; it can determine whether land control, financing assumptions and anticipated power delivery remain useful.
Watch for:
- Clarification of the Yaphank application’s status under state permitting rules.
- Brookhaven’s eventual standards for location, design, energy, water, noise and infrastructure capacity.
- Whether overlapping moratoria become common in other states with strong municipal land-use authority.
Local Approval Becomes a Continuing Political Process
Data center approvals increasingly face political and legal exposure before, during and after conventional zoning review. Open houses, petitions, ballot measures and negotiated court settlements are becoming part of the development pathway.
Fresh developments
In Chesterfield County, Google’s open houses drew substantial attendance but did not settle questions about water demand, approval progress or confidential negotiations. In Ohio, Sunbury’s proposed ban advanced to a November charter vote. Michigan supplied the counterpoint: an advanced project is still building after a court-approved agreement imposed operating restrictions and community benefits.
Why we noticed
These cases show that community response is not a single-stage obstacle. It can delay early proposals, rewrite local law or continue through litigation after construction begins. Developers therefore need public-process, electoral and legal strategies that extend beyond the initial entitlement vote.
Watch for:
- Whether Sunbury’s capacity-based restriction becomes a model for other Ohio municipalities.
- Further legal action over the Saline Township consent judgment.
- Whether Chesterfield moves toward additional hearings, conditions or disclosure requirements.
Power, Water and Incentives Move Toward Measurable Conditions
Governments are increasingly trying to convert broad concerns about resource use and subsidies into reporting requirements, development standards and conditions for receiving public benefits. Equipment design is also changing in response to water and cooling constraints.
Fresh developments
The Allegheny Front documented Pennsylvania measures covering annual energy and water reporting, electricity-demand forecasting and review of advanced transmission options. Proposed GRID standards would link the state’s 6% sales tax exemption to requirements covering energy procurement, community engagement, environmental protections and water planning. Separately, NVIDIA described a hotter liquid-cooling architecture intended to reduce reliance on chillers and evaporative cooling.
Why we noticed
Policy and engineering are beginning to converge on the same question: can operators document and reduce the infrastructure burden they create? Better cooling can narrow water and noise concerns, but public acceptance will still depend on who funds generation and grid expansion and whether promised operating performance is enforceable.
Watch for:
- Whether Pennsylvania makes GRID standards mandatory for retaining tax benefits.
- Implementation details for annual energy and water reporting.
- Operational evidence on water and energy performance from NVIDIA’s Rubin deployments.
Final Thought
The next phase of the buildout will be shaped less by whether communities broadly favor data centers than by whether individual projects arrive with power, water, cost and operating assumptions concrete enough to survive rules being written around them.