The data center fight in Rochester Hills, Michigan
As of October 1, 2026, Rochester Hills, Michigan has a data center moratorium in force (action taken Extended Aug 2026; documented end date 2027-03-15).
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
180-day moratorium adopted Mar 2026, extended through mid-Mar 2027; studying noise, vibration, light pollution, water, electricity demand
SourceNews
read 2026-08-13
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 1 headline 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
- Pontiac (7 mi) — Expiredterm ran to 2026-07-21
- Sterling Heights (8 mi) — Enactedexpires 2027-02-04
- Orion Township (10 mi) — Enactedexpires 2026-12-17
- Village of Romeo (12 mi) — Enactedterm not documented
- Lenox Township (12 mi) — Expiredterm ran to 2026-06-02
- Washington Township (Macomb Co.) (12 mi) — Enactedexpires soon — 2026-11-23
- Waterford Township (13 mi) — Enactedexpires soon — 2026-10-01
- Springfield Township (18 mi) — Enactedfixed term, end date not recorded
All 64 tracked actions in Michigan are on the state page.
As of August 2026 (2m 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.