Skip to content
Rush Commerce
Field Notes3 min read

Data center backlash is now an election issue

Gallup says 7 in 10 Americans oppose an AI data center near them, and candidates in both parties are running on moratoriums. Plan your cloud regions accordingly.

Cloud region planning used to be a latency question. As of this primary season it is also a data center backlash question: candidates in both parties are campaigning on moratoriums, and the polling behind them is not close.

What actually happened

NPR reported August 8 that data centers have become a cross-party issue driving voters to candidates. The anchor number comes from Gallup: 7 in 10 Americans oppose construction of an AI data center in their local area, including 48% strongly opposed. That poll was conducted March 2–18, 2026, with a random sample of 1,000 U.S. adults.

The campaign examples cross the aisle. In Ohio, Republican gubernatorial nominee Vivek Ramaswamy released an "Ohioans-first data center pledge" calling for legislation and, until it passes, a moratorium on data center construction — saying the pace of expansion is the second-most common concern he hears after property taxes, and proposing that data center companies cover nearby residents' power bills. Ohio Democratic candidate Amy Acton had released a "conditional moratorium" plan the month before. In Michigan, Senate candidate Abdul El-Sayed held a rally in front of the OpenAI and Oracle campus in Saline Township and won his primary. In Wisconsin, Francesca Hong has campaigned on a full moratorium.

Why it matters for your business

You do not build data centers. You do depend on where the next ones land, and that decision now runs through zoning boards and statehouse races rather than a vendor's expansion roadmap. Two consequences are already actionable.

Region availability stops being a given. New capacity in a given state is a permitting outcome. If your architecture assumes a specific region — because that is where your data must sit, or where your latency budget lives — verify that assumption is portable before you need it to be. Region names hard-coded across your infrastructure are a migration project you have not scheduled.

Local energy politics touches your other bills. We are in Phoenix. The argument about grid load and rates is not an abstraction here, and it is not one for anyone operating in Texas, Ohio, Virginia or Michigan either. Commercial power is an input cost for a warehouse, a shop, or a kitchen, and it is now attached to a political fight you are not party to.

The practical move is the boring one: know which regions your workloads actually require, keep the region a variable and not a constant, and keep at least one inference path — hosted API, second cloud, or local model — that can absorb the traffic if the first one gets constrained. None of that costs much when you build it in. All of it costs a quarter when you retrofit it.

Key takeaways

  • Gallup: 7 in 10 Americans oppose an AI data center in their local area, 48% strongly opposed (March 2-18, 2026, n=1,000)
  • Candidates in both parties are running on moratoriums — Ramaswamy and Acton in Ohio, Hong in Wisconsin, El-Sayed in Michigan
  • New regional capacity is now a permitting and political outcome, not just a vendor roadmap item
  • Hard-coded cloud regions are an unscheduled migration project
  • Keep the region a variable and keep a second inference path that can absorb traffic

Infrastructure you can move is infrastructure you own. We build systems where the region, the provider, and the model are configuration — not assumptions baked into a hundred files. See how we keep stacks portable or have us audit what your deployment assumes.

Sources: NPR, Gallup.

  • #data-centers
  • #cloud-infrastructure
  • #ai-policy
  • #vendor-risk
  • #energy
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.