Community briefing

Statewide data center action in Ohio

Ohio has a rejected 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

Rejectedstatus
2026action taken
Statelevel

Proposed constitutional amendment to ban data centers >25 MW failed to qualify — collected ~70,000 of 413,488 required signatures. Backers plan to try again for 2027 ballot

Source
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.

What to do next

Generate a full action pack →

Elsewhere in Ohio

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.