The data center fight in Milford, Utah
As of September 27, 2026, Milford, Utah has a data center moratorium in force (action taken Jun 16, 2026; documented end date 2026-12-13).
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
Ordinance 04-2026: 180-day moratorium on data centers, data center power plants, and solar energy facilities; 5-0 unanimous. Council determined data centers are not appropriate land use within city limits
SourceOfficial
read 2026-09-11
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
What to do next
- Questions to ask at the hearing — force specific answers onto the record.
- Estimate the impact — electricity, water, and rate pressure for any facility size in Utah.
- Model CBA clauses — copy-paste language communities have actually won.
- Utah briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Utah
- Iron County (50 mi) — Enactedexpires soon — 2026-11-22
- Wayne County (74 mi) — Enactedexpires 2027-01-17
- Grand County (188 mi) — Enactedexpires 2027-01-03
- Clearfield (195 mi) — Enactedexpires 2027-03-07
- Box Elder County (221 mi) — Enactedexpires 2026-12-07
- Cache County (238 mi) — Enactedexpires 2026-12-20
- Logan (239 mi) — Enactedexpires 2026-12-27
All 8 tracked actions in Utah are on the state page.
As of August 2026 · 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.