The data center fight in Superior, Wisconsin
As of October 1, 2026, Superior, Wisconsin has a data center moratorium in force (action taken Jun 17, 2026; documented end date 2027-06-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
1-year moratorium, unanimous. City lacks zoning definitions for data center sizes. Planning commission reviewing zoning and infrastructure recommendations
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 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
- Sawyer County (74 mi) — Enactedfixed term, end date not recorded
- Polk County (88 mi) — Proposedterm not documented
- Chippewa County (121 mi) — Enactedfixed term, end date not recorded
- St. Croix County (122 mi) — Enactedexpires 2027-09-01
- Oneida County (141 mi) — Enactedexpires 2027-08-19
- Marathon County (167 mi) — Enactedterm not documented
- La Crosse County (202 mi) — Enactedexpires 2027-12-18
- Monroe County (205 mi) — Enactedexpires 2028-01-21
All 35 tracked actions in Wisconsin 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.