The data center fight in Sedgwick County, Kansas
As of September 27, 2026, Sedgwick County, Kansas has a data center moratorium in force (action taken Jan 15, 2026; documented end date 2026-12-24).
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
Interim development control on data center applications, first adopted January 2026 and extended three times — to Jun 11, to Sep 11, and on Sep 2, 2026 (unanimous) through Dec 24, 2026 — while planning staff write zoning rules; commission checkpoint Dec 2
SourceNews
read 2026-09-04
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
- Sedgwick County extends moratorium on data centers again while it works on rules for them
- Sedgwick County commissioners to consider data center moratorium extension
- Sedgwick Co. considering extending data center 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 Kansas.
- Model CBA clauses — copy-paste language communities have actually won.
- Kansas briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Kansas
- Wichita (0 mi) — Expiredterm ran to 2026-09-10
- Harvey County (25 mi) — Enactedexpires 2028-12-31
- El Dorado (28 mi) — Enactedexpires 2026-11-30
- South Hutchinson (40 mi) — Enactedexpires 2027-05-26
- Kingman County (44 mi) — Enactedterm not documented
- McPherson County (50 mi) — Enactedno end date — permanent
- Kansas (SB 531) (66 mi) — Proposedterm not documented
- Lyon County (80 mi) — Enactedexpires 2027-01-22
All 19 tracked actions in Kansas 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.