The data center fight in Bell County, Kentucky
As of October 1, 2026, Bell County, Kentucky has a data center moratorium in force (action taken Jul 2, 2026; documented end date 2028-07-02).
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
2-year moratorium, passed unanimously by the fiscal court; halted a Murray Industries hyperscale project that had already begun clearing land along the Bell-Knox county line
SourceNews
read 2026-08-11
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
- Bell County passed a data center moratorium. Residents worry that work continues.
- Bell County residents pack courthouse to oppose data center construction
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 2 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 Kentucky.
- Model CBA clauses — copy-paste language communities have actually won.
- Kentucky briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Kentucky
- London (39 mi) — Enactedexpires 2028-09-30
- Clark County (91 mi) — Enactedfixed term, end date not recorded
- Winchester (92 mi) — Enactedexpires 2027-09-02
- Boyle County (94 mi) — Enactedexpires 2027-06-09
- Jessamine County (96 mi) — Enactedexpires 2027-08-04
- Nicholasville (96 mi) — Enactedfixed term, end date not recorded
- Rowan County (100 mi) — Enactedfixed term, end date not recorded
- Lexington (Fayette County) (103 mi) — Enactedexpires soon — 2026-10-31
All 29 tracked actions in Kentucky 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.