Why City Councils Are Unanimously Blocking Hyperscale Data Centers

In late August 2026, city councils across the United States began drawing a hard line against the physical infrastructure of the artificial intelligence boom. Following hours of intense public outcry, municipal leaders in towns like Fredericksburg, Virginia, and Pataskala, Ohio, voted unanimously to deny zoning permits for massive, hyperscale data centers. The core issue driving this local backlash is resource consumption: these facilities require the water and electricity of a small city, and local land-use codes were never designed to regulate them.[1][2][7]

The mechanism of rejection relies on the gap between outdated municipal codes and modern digital infrastructure. A data center is a physical facility that houses IT infrastructure, servers, and computing resources for cloud service providers. Most municipalities do not have specific zoning categories for these hyperscale facilities. Instead, developers often apply under generic "communications services" or light industrial designations. When residents realize a 100-megawatt facility is planned near their neighborhoods, the battle shifts to the approval of special use permits and zoning map amendments, giving local councils the final say.[3][5][7]

The Fredericksburg vote illustrates this dynamic perfectly. On August 26, the Fredericksburg City Council voted 7-0 to deny a special use permit for the 1500 Gateway project. The developer had scaled the project down from 2.1 million to 1 million square feet and offered up to $40 million in voluntary contributions, known as proffers. Despite these financial concessions and a pledge to use air-cooled systems rather than municipal water, the council rejected the zoning amendment due to land-use incompatibility and infrastructure strain.[1]

That same week in Ohio, the Pataskala City Council unanimously rejected a site plan for a 200-megawatt facility proposed by Aligned Data Centers. The 89-acre project sat in a designated corporate park, but residents packed city hall to protest the strain on the local power grid and the proximity to residential areas. Council members ultimately cited an incomplete power plan and inadequate infrastructure guarantees as the primary reasons for denial.[2]

The sheer scale of these facilities drives the local backlash. To understand the community resistance, one must look at the "water footprint" of these developments. A water footprint measures the total volume of fresh water used to produce goods and services, accounting for both direct consumption and indirect usage throughout the supply chain.[4][6]

For a data center, the direct water footprint comes from cooling. Thousands of servers packed into racks generate enormous heat, and facilities often use evaporative cooling towers to prevent equipment failure. A large hyperscale data center can directly consume millions of gallons of water per day—evaporating it into the atmosphere rather than returning it to the local watershed.[3][5][7]

However, the indirect water footprint is often much larger. Data centers require massive amounts of electricity, and the power plants generating that electricity—whether coal, natural gas, or nuclear—rely heavily on water for their own cooling processes. When a city council evaluates a 100-megawatt data center, they are not just approving a building; they are indirectly allocating billions of gallons of regional water to support the power grid that feeds it.[4][6][7]

While developers increasingly pitch "closed-loop" cooling systems that recirculate liquid rather than evaporating fresh water on-site, these systems often require more electricity to operate. This dynamic simply shifts the resource burden from the local water aquifer to the regional power grid, which in turn relies on water-intensive power generation.[7]

Tech companies argue that these facilities are the necessary backbone of the modern digital economy, generating significant local tax revenue and construction jobs. However, the permanent job creation is often minimal—typically 30 to 50 jobs for a massive facility—leaving residents questioning the long-term return on investment for their communities.[5][7]

As local governments tighten their zoning codes, the conflict is likely to escalate to the state or federal level. Developers are already lobbying for standardized regulations that would prevent municipalities from outright banning critical digital infrastructure. Until those broader frameworks materialize, the local city council remains the primary bottleneck for the physical expansion of the AI industry.[7]