40 of 41 Ballot Contests Went Against Data Center Growth

By Amara Osei

Voters favored limits on data-center development in 40 of 41 local ballot contests held on November 3, 2026, Ballotpedia reported. Voters approved 27 measures that restricted development or expressed opposition to it. The result converts a set of neighborhood disputes into a planning variable for anyone who buys cloud capacity.

What did the ballot box produce?

The measures split into binding bans, advisory questions and process changes that force large projects back to voters. The reported bans landed in California, Florida, Ohio, Kansas and Maine — coastal suburbs, Midwestern farm towns and small New England communities alike. No single region owns the backlash.

The scoreboard:

• 41 local data-center contests held
• 40 contests where voters favored limits
• 27 measures approved limiting development or expressing opposition
• 5 full bans: 1 California, 1 Florida, 3 Ohio
• 12 partial bans: 3 Kansas, 1 Maine, 8 Ohio

Ohio did most of the restriction work. Any operator with an Ohio pipeline should treat local approval as no longer assumable.

How do full and partial bans differ in practice?

A full ban closes the use category inside the jurisdiction. A partial ban targets size, power draw or project type, leaving room for a small edge facility while blocking the multi-building campus. For cloud customers, partial bans matter more: they reshape what gets built, not just where, and push developers toward smaller, distributed footprints. The source record does not break down size thresholds in each partial ban.

What do Grove City and Janesville change?

Grove City, Ohio, passed Issue 28, which requires voter approval for developments using more than 50 acres, 20 megawatts of electricity, or 500,000 gallons of water per day. The text never says "data center." It regulates inputs — acreage, power, water — so a developer cannot rename a project to escape it. At 20 megawatts, the trigger sits low enough to send most large builds to the ballot, and other towns can copy the three-part test without rewriting their zoning codes.

Janesville, Wisconsin, took a project-specific route: voter approval is required for development at a proposed GM/JATCO data-center site if the project cost exceeds $450 million. The gate is money, tied to one named site.

Both measures move the final decision from planning boards to the general electorate. Boards weigh traffic studies; voters weigh the headline.

Which councils acted after the election?

• Edmond, Oklahoma — extended a data-center moratorium 5-0 on November 9, 2026; it now runs through June 30, 2027.
• Boise, Idaho — Mayor Lauren McLean proposed a moratorium on mega data centers within city limits on November 6, 2026. Proposed, not adopted; the council must still act.
• Memphis, Tennessee — on November 9, 2026, the council continued discussing zoning rules and referred part of the proposal to the Planning and Zoning Commission.
• Concord Township, Pennsylvania — unanimously approved an ordinance on November 4, 2026: data centers permitted in light-industrial areas on sites of at least 12 acres, with a 900-foot setback from residences, nursing facilities and schools.
• Millburn Township, New Jersey — Ordinance 2783-26 prohibits data centers, as defined in DRZ-301, in all zoning districts.
• Evanston, Illinois — a one-year temporary moratorium bars entitlement applications for data-center permits.

Greene Township, Pennsylvania, proposes a 200-foot setback from neighboring homes, residential districts or community buildings, 100 feet from other properties and a 60-foot height cap. Hazle Township's draft amendment would permit data centers in an I-1 industrial district within one-half mile of high-voltage lines north of Route 924 and east of Interstate 81. The gap between 200 feet and Concord's 900 feet shows the latitude each town holds.

A ban demands a legal challenge or a move; a moratorium demands patience and a calendar. Both slow build schedules.

What do the surveys say about public opinion?

Michigan State University's Institute for Public Policy and Social Research found in its 2026 State of the State Survey: "In a survey of Michigan residents, 70% were opposed to constructing data centers in their community: 52% were strongly opposed and 18% somewhat opposed." The same survey found 83% of respondents said local governments should have at least some authority over permitting — 52% said a lot, 31% at least a little.

The University of Michigan's Center for Local, State, and Urban Policy reported: "Among Michigan local officials, 55% believed residents in their jurisdictions would strongly oppose new large-scale data-center development, while only 2% believed residents would support it." The same survey found 60% of local officials opposed state authority over local planning and zoning for data centers, against 20% in favor.

When 70% of surveyed residents oppose a local facility and only 2% of officials expect support, a limiting measure starts with a built-in majority. State capitols courting data-center investment will meet officials who want to keep their zoning pen.

What changes for cloud capacity and FinOps?

No source links these ordinances to cloud price changes yet. The channel to watch is lead time: a slipped expansion means rerouted demand or tighter quotas on scarce instance types. The most exposed markets combine thin grid headroom with heavy local scrutiny; earlier reporting put 13 GW of AI capacity behind a Texas moratorium push and Norway's grid pause at 4,200 MW.

FinOps teams gain a supply-side argument: Kubernetes clusters analyzed earlier this year averaged 8% CPU and 5% GPU use. Reclaiming idle capacity requires no council vote. Practical steps:

• Audit GPU and CPU utilization before requesting reserved capacity
• Negotiate commitments with region-change flexibility clauses
• Track which workloads require a specific metro and which run anywhere
• Build a second-region plan for production systems tied to a constrained market

Federal permitting reform addresses environmental review and interconnection; it does not override a township's zoning map. A federal fast lane still ends at a local parcel.

Local politics now sits inside the cloud supply chain — treat zoning as a first-class capacity-planning input alongside power prices and hardware lead times.