The data center fight in Springfield, Missouri
As of October 1, 2026, Springfield, Missouri has a data center moratorium in force (action taken Jun 29, 2026; documented end date 2026-11-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
120-day administrative delay, 8-0. Expires Nov 17 or when council passes a two-reading bill. Public input sessions to follow
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
- Springfield data center town hall pushes for accountability on development
- Developer behind Springfield data center plan sues city | Exclusive
- Springfield seeks input on data centers with 2 engagement sessions amid 120-day moratorium
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 3 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 Missouri.
- Model CBA clauses — copy-paste language communities have actually won.
- Missouri briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Missouri
- Webster County (23 mi) — Enactedexpires 2026-12-16
- Camdenton (62 mi) — Enactedexpires 2027-05-05
- Neosho (64 mi) — Enactedexpires 2027-07-07
- Peculiar (122 mi) — Enactedno end date — permanent
- Columbia (130 mi) — Enactedfixed term, end date not recorded
- Oak Grove (131 mi) — Enactedexpires 2027-08-05
- Jackson County (136 mi) — Enactedexpires 2026-12-19
- Independence (143 mi) — Enactedexpires 2027-01-02
All 18 tracked actions in Missouri 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.