Local governments across several states are pausing new data-center development while they review zoning, infrastructure and environmental concerns. The restrictions vary by community: a temporary moratorium can stop new applications or approvals without permanently banning the facilities.

Where communities have acted

In Michigan, at least 52 communities had enacted data-center moratoriums by June 29, according to reporting by Michigan Public. That dated tally illustrates the breadth of local action; it is not a current nationwide count or a measure of projects canceled.

Charlotte, North Carolina, approved a 150-day moratorium on June 8. The city says it runs through November 5 and gives a task force time to prepare policy recommendations. Projects with complete applications submitted before the pause, or with prior approvals, can proceed under the city’s stated exceptions.

What Charlotte’s pause changes

Charlotte divides its pause into two stages. The first 75 days, through August 22, were allocated to research and impact analysis. The remaining period, August 23 through November 5, allows proposed code or policy changes to proceed through the legislative process, including a public hearing and council vote if changes are warranted.

The distinction matters for residents watching construction near their homes: Charlotte says existing facilities may keep operating, and exempt projects may continue development. A moratorium can therefore coexist with visible construction. It does not mean every data-center project has been canceled.

Ohio communities have taken similar steps. Clayton’s official legislative register records a July 16 resolution establishing a 365-day pause on accepting and processing applications for data-processing centers. In Wisconsin, Shawano County’s planning department identifies a data-center moratorium approved at its June 24 board meeting.

Reading the local record

The local records show why a single headline number can obscure the details: adoption dates, covered facilities, exemptions and expiration dates differ. This article reports documented examples rather than treating the four-state estimates in the original X post as a verified total.

To assess a proposed project, readers should check the actual local measure: which applications it covers, which projects are exempt, when it expires and what rules would replace it. A dated count of moratoriums cannot answer those project-level questions. The linked city and county records provide a starting point for that review.