The data center fight in Mason, Michigan
As of September 27, 2026, Mason, Michigan had a data center moratorium whose documented term has run out (action taken Jan 6, 2026; it ended 2026-02-03).
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 267, 90-day moratorium on data center permits. Lifted Feb 3 when council adopted M-3 Technology Innovation District zoning (Ordinance 266, 5-2). Ord 266 then repealed 4-2 on Mar 16 after a 755-signature citizen referendum petition. Council adopted a citizen-initiated noise and vibration ordinance in June.
SourceNews
read 2026-09-07
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
- South of the Mason-Dixon Line, Maryland counties scramble to respond to data centers
- Residents speak out against data center at Mason City Council meeting
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 2 headlines archived.
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 Michigan.
- Model CBA clauses — copy-paste language communities have actually won.
- Michigan briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Michigan
- Meridian Township (10 mi) — Enactedexpires soon — 2026-11-19
- East Lansing (11 mi) — Enactedexpires 2027-03-17
- Lansing (12 mi) — Enactedexpires 2027-01-25
- Michigan (HB 5594-5596) (12 mi) — Proposedterm not documented
- Parma Township (15 mi) — Enactedterm not documented
- Genoa Township (25 mi) — Enactedterm not documented
- Lyndon Township (25 mi) — Enactedexpires 2027-05-22
- Sylvan Township (26 mi) — Expiredterm ran to 2026-07-22
All 64 tracked actions in Michigan 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.