The data center fight in Milwaukee, Wisconsin
As of September 27, 2026, Milwaukee, Wisconsin has a data center moratorium under consideration (action taken Aug 10, 2026).
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
Proposed ordinance would bar city departments from accepting or processing applications to construct, enlarge, expand, convert or occupy data centers, for one year after passage or until the zoning code is amended to regulate them, whichever comes first. Zoning Code Technical Committee endorsed it Aug 10; City Plan Commission hearing set for Sep 28, 2026. Common Council approval still required — not yet adopted
SourceNews
read 2026-09-20
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 Wisconsin.
- Model CBA clauses — copy-paste language communities have actually won.
- Wisconsin briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Wisconsin
- Dodge County (49 mi) — Enactedexpires 2028-02-10
- Sheboygan (50 mi) — Enactedexpires 2027-07-23
- Village of Cottage Grove (65 mi) — Enactedexpires 2028-01-20
- Manitowoc County (74 mi) — Enactedexpires 2027-10-29
- Town of Hampden (75 mi) — Enactedterm not documented
- Madison (75 mi) — Enactedexpires 2027-01-13
- Wisconsin (75 mi) — Proposedterm not documented
- Dane County (76 mi) — Enactedexpires 2027-12-04
All 34 tracked actions in Wisconsin 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.