Community briefing

The data center fight in Wayne County, Utah

As of November 12, 2026, Wayne County, Utah has a data center moratorium in force (action taken Jul 21, 2026; documented end date 2027-01-17).

Status is derived, not stored — a pause with a documented end date flips to Expired on its own — and the source is right next to the claim.

Status today

Enactedexpires 2027-01-17status
Jul 21, 2026action taken
Locallevel

Resolution 2026-04: immediate 180-day moratorium on all land use applications for data centers, data center power plants (explicitly including nuclear) and supporting digital infrastructure, unanimous. County code did not address data centers at all

SourceNews
read 2026-09-05

An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.

Recent news

6 stories tracked since 2026-09-30 across 5 outlets. 4× A community is pushing back on a nearby data center. 2× Residents question property-value hits and local benefit. Most recent: “$75M data center plan scrapped in Wayne County after residents pack City Hall” (MLive.com, 2026-10-20).

Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 6 headlines archived.

What to do next

Build a full action pack →

Nearby in Utah

  • Milford (74 mi) — Enactedexpires soon — 2026-12-13
  • Iron County (92 mi) — Enactedexpires soon — 2026-11-22
  • Grand County (114 mi) — Enactedexpires soon — 2027-01-03
  • Clearfield (188 mi) — Enactedexpires 2027-03-07
  • Box Elder County (216 mi) — Enactedexpires soon — 2026-12-07
  • Cache County (230 mi) — Enactedexpires soon — 2026-12-20
  • Logan (231 mi) — Enactedexpires soon — 2026-12-27

All 8 tracked actions in Utah are on the state page.

As of August 2026 (3m ago) · changes weekly — re-check before citing

Illustrative rather than exhaustive — dozens of localities churn weekly, and this tracks the ones we have read a source for. **Each row carries its own provenance.** Rows showing a verification date link to the ordinance, the enacting body's own page, or a datable report of the vote, and were read on that date. Rows marked *unverified* came from bulk compilation and have not been checked against a primary source — the locality, the year, and the status may all be off. Verify one of those with the town clerk before citing it as precedent. **Expiry is derived, not asserted.** A row with a documented end date flips to *Expired* on its own once that date passes. A time-limited moratorium whose start date was never documented keeps showing as enacted — that is a known gap, not a claim that it is still in force. Moratoriums are also routinely extended, so an expiry date is the earliest it could have ended, not proof that it did.

Part of the U.S. data center moratorium tracker — open data, CC BY 4.0.

Toolkit States Tracker Search