The data center fight in Lyon County, Kansas
Lyon County has an active data center moratorium on this tracker. 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
Resolution 12-26: 6-month pause on new data center and battery energy storage projects, unanimous, running through Jan 22, 2027, to let the county strengthen zoning rules. A companion Resolution 13-26 pauses utility-scale solar through Dec 1, 2026. Unincorporated areas only — it does not reach Emporia's Flint Hills Digital Campus. Outlets split on the vote date between Thu Jul 23 and Fri Jul 24; Jul 23 is the Thursday
Source
read 2026-08-23
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
- Data center moratorium ordinance passes unanimously in Lyon County
- Data center moratorium ordinance passes unanimously in Lyon County
- Lyon County Commissioners vote to allow new data center north of Yerington
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 Kansas.
- Model CBA clauses — copy-paste language communities have actually won.
- Kansas briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Elsewhere in Kansas
- Shawnee County — Enactedexpires 2027-02-17
- Emporia — Proposedterm not documented
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.