The data center fight in Cincinnati, Ohio
As of September 27, 2026, Cincinnati, Ohio has a data center moratorium in force (action taken Feb 11, 2026; documented end date 2027-02-11).
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 Overlay #89 on data centers across six zoning districts (~22,000 parcels). Originally 3 months, extended Apr 1 for 9 additional months. Gives Planning Dept time to draft permanent zoning classification for data centers, which were previously unclassified and treated as indoor storage
SourceOfficial
read 2026-09-06
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
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 Ohio.
- Model CBA clauses — copy-paste language communities have actually won.
- Ohio briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Ohio
- Pierce Township (12 mi) — Enactedexpires soon — 2026-10-09
- Butler County (24 mi) — Enactedexpires 2026-12-16
- Williamsburg (25 mi) — Enactedexpires 2027-03-13
- Washington Township (Butler Co.) (27 mi) — Enactedexpires 2027-04-16
- Blanchester (31 mi) — Enactedexpires 2028-03-12
- Mount Orab (32 mi) — Expiredterm ran to 2026-08-30
- Sprigg Township (53 mi) — Enactedexpires 2027-02-24
- Yellow Springs (59 mi) — Enactedexpires 2027-05-18
All 62 tracked actions in Ohio 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.