The backlash has a number now
Tracking from Heatmap News puts the count of local laws restricting or banning data centers at more than 530 nationwide, with nearly 190 of those ordinances passed since June 1, 2026 alone. New York remains the only state with a statewide moratorium, but the local level activity is where the real friction sits: counties and municipalities across Michigan, Indiana, Texas, Arizona, Wisconsin, and Virginia have all passed restrictions this year, and the overwhelming majority of the 530 total have come in 2026 specifically, not accumulated gradually over prior years.
Peter Freed, founding partner at Near Horizon Group and former director of energy strategy at Meta, describes the pace as accelerating, though he is careful to note the country is not near a breaking point yet. His read on the practical effect is more useful than the raw count: developers are increasingly abandoning efforts in communities that pass restrictions and shifting attention elsewhere, which means the 530 figure understates the real chilling effect on where hyperscalers are willing to even propose a project in the first place.
The cancellation rate is the number that should worry procurement
More than 50 data center projects have been canceled in 2026, more than double the total for all of 2025, with eight cancellations in July alone. Among contested proposals specifically, projects that draw organized local opposition, the cancellation rate has climbed to roughly 50 percent, up from a historical rate closer to 40 percent. The variance by state is stark: Michigan's contested projects are being canceled at a 71 percent rate, Indiana's at 56 percent, while Texas, still seen as the most permissive major market, sits at 17 percent.
Meta CFO Susan Li has publicly described the infrastructure building environment as dynamic and uncertain, corporate language that understates what the numbers show: even the largest, best capitalized developers are losing sited projects to local opposition at a rate that would have been unusual two years ago. Amazon, Microsoft, and Google have each withdrawn major proposed projects this year, in Arizona, Wisconsin, and Indiana respectively, evidence that scale and capital are not sufficient to guarantee a project clears local approval.
What the opposition is actually litigating
An August analysis from law firm Arnold and Porter maps the legal fronts beyond zoning votes. Active cases include environmental citizen suits under the Clean Air Act and Clean Water Act, disputes over emissions permitting for on site gas turbines, groundwater contamination claims, and common law nuisance suits over noise and vibration from cooling and generator equipment. In Mississippi, NAACP v. X.AI Corp targets Clean Air Act emissions violations, while a separate Haley v. X.AI Corp case is a noise and vibration class action with more than 10,000 members. In Oregon, Pearson v. Amazon Data Services resulted in a 20.5 million dollar settlement over water contamination claims.
The pattern across these cases is that litigation is no longer following failed zoning votes, it is running in parallel with them, and increasingly starting before a project is even fully sited. That shift means legal risk has moved earlier in the development timeline, from a post hoc challenge to an approved project into a pre construction variable that affects financing, insurance, and timeline from the day a site is selected.
Why this belongs on the CTO's desk, not just legal's
Technology leaders evaluating colocation contracts, build to suit arrangements, or dedicated capacity commitments have historically treated site selection risk as the developer's problem to manage. That assumption no longer holds when cancellation rates are approaching 50 percent for contested projects and litigation timelines routinely add a year or more to delivery. A capacity commitment tied to a specific under construction facility carries real delivery risk that deserves the same scrutiny procurement gives to a vendor's financial stability.
Holly Davis, a county commissioner quoted in the Heatmap reporting, put the local politics bluntly: the people are not okay with this, and clearly some, if not all, of the commissioners are also not okay with this. That sentiment is showing up in election cycles too, with Michigan Senate candidate Abdul El-Sayed noting that data centers and AI now come up in nearly every conversation he has on the campaign trail. Local opposition to data centers has become mainstream political material, not a fringe concern, and that trajectory does not reverse quickly.
The diligence checklist this creates
Before signing a multi year capacity commitment tied to a facility that is not yet operational, procurement and infrastructure teams should ask the provider directly what local ordinances apply to the site, whether any organized opposition or litigation has already surfaced, and what contractual protections exist if delivery slips due to a permitting fight or a canceled permit. A facility in a jurisdiction with an active moratorium debate or a pending nuisance suit carries a materially different delivery timeline risk than one in a jurisdiction with no local opposition on record.
None of this argues against continued data center investment, which remains necessary and is not slowing at the national level. It argues for treating local regulatory and litigation risk as a standard, quantified input to site and vendor selection, the same way currency risk or supply chain risk already gets modeled for other capital commitments. The 530 law count is not a ceiling. It is a trend line, and the enterprises locking in capacity commitments today should be underwriting where that trend line goes over the life of their contract, not just where it sits this month.
