Community briefing

The data center fight in Cleveland, Ohio

As of September 27, 2026, Cleveland, Ohio has a data center moratorium in force (action taken Jul 15, 2026; documented end date 2026-10-16).

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

Enactedexpires soon — 2026-10-16status
Jul 15, 2026action taken
Locallevel

Emergency Ordinance File #556-2026, 3-month moratorium on new standalone data center permits and certificates of occupancy. Passed 14-1. Does not apply to server rooms in multi-tenant buildings. Council may extend up to 3 additional months. Cleveland currently has zero hyperscale standalone data centers

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.

Recent news

6 stories tracked since 2026-08-12 across 4 outlets. 5× A community is pushing back on a nearby data center. 1× Local officials are moving to pause or block the project. Most recent: “Cleveland residents speak out on proposed data centers during first public hearing” (WKYC, 2026-09-25).

Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 6 headlines archived.

What to do next

Build a full action pack →

Nearby in Ohio

  • Berea (12 mi) — Enactedexpires 2027-06-15
  • Avon Lake (18 mi) — Enactedexpires 2027-06-22
  • Twinsburg (18 mi) — Enactedfixed term, end date not recorded
  • Avon (18 mi) — Enactedexpires 2027-04-14
  • Grafton (25 mi) — Enactedexpires 2031-05-19
  • Painesville Township (27 mi) — Enactedfixed term, end date not recorded
  • Kent (30 mi) — Enactedexpires 2027-04-15
  • Tallmadge (31 mi) — Enactedexpires soon — 2026-10-10

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.

Toolkit States Tracker Search