🔍 Read the full analysis: Why Data Centers Lost 46 Of 47 Local Ballot Votes—and What That Means on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
A public tracker listed 47 local measures related to data centers on Nov. 3 ballots across 10 states. As of Nov. 5, unofficial results showed the restrictive outcome winning or leading in 46; the measures ranged from outright bans to advisory questions and temporary pauses.
Voters in 10 states weighed 47 local ballot measures related to data centers on Nov. 3, and the restrictive side won or was leading in 46 of them, according to the public Data Centers on the Ballot tracker. The results are unofficial, six counts were still underway as of Nov. 5, and the measures covered very different decisions—from outright bans to advisory questions—so the tally does not mean voters rejected the same policy everywhere.
The tracker, built by polling and data firm Redbud Consulting, grouped measures by whether their restrictive or permissive outcome was ahead. At 12:30 p.m. Eastern on Nov. 5, it listed 47 measures, with 41 election-night counts complete and six still counting. Across them, the tracker recorded 260,177 votes; 72.8% were cast for the outcome it categorized as “Restrict.” The tracker says its results are not certified.
One clear example came in Hubbard, Ohio, where voters were asked whether data centers of any size should be banned within city limits. The unofficial count was 2,622 yes to 802 no, or 76.6% in favor of the ban. In Wilmington, Ohio, voters overturned four council decisions rezoning rural land for data centers. In Boulder City, Nevada, voters rejected a proposal to open city-owned desert land to data centers: 2,064 voted yes and 4,947 voted no, according to the unofficial count cited by the tracker.
The reported total changed after election night. The tracker showed 45 measures at 6:16 a.m. Eastern on Nov. 4, with results posted for 40; it later added a nonbinding question in Belvidere, New Jersey, and a charter amendment in Piqua, Ohio. Ballotpedia had listed 41 measures before the vote, using a different count that included fewer Maine, Kansas and New Jersey measures. The different totals reflect differing definitions of what qualifies as a data-center ballot measure, not necessarily a disagreement about results.
Infographic 01 · Data centers on the ballot
Where “45 measures” comes from
One public tracker did the counting. Its numbers grew as results and late additions came in. We checked seven results against official election sites.
local ballot measures on data centers went against them on unofficial counts, 5 Nov 2026, 12:30 p.m. ET. The one exception: Harwood, North Dakota.
- 3 NovBallotpedia: 41 measuresListed before the vote · 10 states
- 4 Nov, 6:16 a.m.Tracker: 45 measures40 with results · 39 against data centers, 1 for
- 4 NovHeadlines: “45 measures”33 won, 6 leading, 1 lost, 5 not reported
- 5 Nov, 12:30 p.m.Tracker: 47 measuresAll with results · 46 against, 1 for · 6 still counting
- Emporia, KSban over 10 MW · Lyon County4,346 : 2,891
- Americus, KSban · Lyon County274 : 127
- El Dorado, KSten-year ban · Butler County2,972 : 1,183
- Ottawa, KSban over 25 MW · Franklin County2,882 : 1,129
- Edgewater, FLcharter ban · Volusia County7,875 : 2,328
- Boulder City, NVallow data centers? · Clark County2,064 : 4,947
- Harwood, NDreview rules · ND Secretary of State105 : 325
Yes : No, unofficial. All seven match the tracker to the vote.
- Ballotpedia lists 4 Maine measures, the tracker 8; Kansas 3 vs 4; New Jersey 1 vs 2. That is the gap from 41 to 47.
- The tracker added Belvidere (NJ) and Piqua (OH) after the first reports, so 45 became 47.
- 404 Media’s “40+ races in 13 states” also counts recalls and candidate races.
- Wilmington, Ohio alone accounts for 4 measures: one vote per rezoned parcel.
Sources: Data Centers on the Ballot (Redbud Consulting), 5 Nov 2026, 12:30 p.m. ET · Ballotpedia, 3 Nov 2026 · official results of Lyon, Butler and Franklin County (KS), Volusia County (FL), Clark County (NV), North Dakota Secretary of State. Nothing is certified yet.
Powered by Thorsten Meyer AI
Local Approval Is a Project Risk
The results point to a local permitting and siting challenge for data-center developers, particularly where residents can directly limit land use, facility size or future approvals. A community vote may add a new hurdle to a project even when state or regional policy is supportive. For residents, the measures offer a way to influence decisions that can shape local land use and public infrastructure.
The tracker’s combined vote share suggests a broad advantage for restrictive outcomes among the measures it counted, but it does not establish why voters chose them. The source describes a recurring policy tension: opponents cite water and energy use, while supporters point to jobs and tax revenue. Those are reported concerns, not findings that every project will have the same effects or that voters rejected data centers for one common reason.
The practical consequences also depend on the measure. Some votes can block or constrain development; others only advise officials or require another public vote. Many measures concern future projects rather than facilities already under construction. Developers therefore face a patchwork of local rules, and the headline figure should not be read as a single nationwide ban or a direct count of projects canceled.
Products Worth Considering

Apple MacBook Air 13.6-inch with M5 Chip, 16GB Memory, 512GB SSD, Sky Blue

EcoFlow Delta 3 Portable Power Station – 1024 Wh, 1800 W

Sony WH-1000XM4C (M4 2nd Gen) Wireless Noise-Cancelling Headphones, Black
As an affiliate, we earn on qualifying purchases.
What the Ballots Actually Asked
The 47 measures included 37 binding measures and 10 advisory questions, according to the source material. Their subjects included bans, size limits—often set at 25 megawatts—temporary moratoriums, zoning referendums and rules requiring public approval before certain projects proceed. A “yes” vote could mean opposite things from place to place, which is why the tracker mapped different ballot wording into its “Restrict” and “Allow” categories.
That distinction matters in interpreting the overall result. Hubbard’s question proposed a direct ban, while Boulder City’s Question 1 asked voters whether the city could make desert land available for data centers. Other ballot questions dealt with zoning decisions or future approval processes rather than whether a particular facility should operate. The tracker provides a consistent way to summarize those results, but its categories do not make the measures legally or politically interchangeable.
The source author says seven results were checked against official election sites in Kansas, Nevada, Florida and North Dakota, and that all seven matched the tracker. For the other results, the author relied on the tracker’s linked county sources and local reporting where available. The Tribune Chronicle, for example, reported Hubbard’s ban passing 76% to 24%. All figures remain unofficial until certified by the relevant election authorities.
“Nothing on the page is certified.”
— Data Centers on the Ballot tracker
Certification and Policy Effects
The Nov. 5 tally was unofficial, and six counts were still being counted. Final totals could change before certification. The source author independently checked seven results, not all 47; the remaining figures rely on the tracker and its linked sources, with local reporting used where available.
It is also unclear how many proposed projects will be delayed, changed or abandoned because of the votes. The results alone do not show whether a measure will face legal challenges, how local officials will implement it, or how developers will respond. Nor do they establish that voters across different communities shared the same reasons for supporting restrictions.
Final Counts and Local Implementation
Election officials must finish counting and certify results before the full outcome is settled. The six unfinished counts could affect individual margins, though the tracker’s broader 46-of-47 picture was based on the results available as of Nov. 5. Residents, developers and local governments will then need to determine what each approved measure requires and when it takes effect.
The next developments to watch are certified vote totals, local decisions implementing binding measures, and any legal or planning disputes tied to specific projects. Advisory questions may shape council decisions without changing rules on their own. Until those steps are clear, the ballot results show strong support for restrictions across the tracked measures, but not a uniform policy or a confirmed tally of projects affected.
Key Questions
What does the 46-of-47 figure mean?
It means the restrictive outcome won or was leading in 46 of 47 data-center-related local measures listed by the Data Centers on the Ballot tracker as of Nov. 5. The results were unofficial, and six counts were still underway.
Did voters approve the same kind of restriction everywhere?
No. The measures included outright bans, size limits, moratoriums, zoning referendums and advisory questions. Some were binding; others did not change local rules by themselves.
Where was the exception to the restrictive trend?
Harwood, North Dakota, was the one exception in the tracker’s summary. The question concerned review rules for large projects, and the unofficial count was 105 yes to 325 no.
Are the results final?
No. The tracker described its results as uncertified as of Nov. 5, and six counts were still ongoing. Election officials must certify the results.
Do the votes mean data centers already being built must close?
Not based on the information available. Many measures targeted future projects, and their legal effects vary. The source does not establish that existing facilities must close; local officials will need to interpret and implement each measure.
Source: ThorstenMeyerAI.com
