The data center fight in Orangeburg County, South Carolina
As of September 27, 2026, Orangeburg County, South Carolina has a data center moratorium in force (action taken 2026-07-23; documented end date 2027-07-23).
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
County Council enacted one-year moratorium on data center construction after three readings; first reading unanimously passed at special-called meeting Jul 23.
SourceNews
read 2026-09-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
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 1 headline 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 South Carolina.
- Model CBA clauses — copy-paste language communities have actually won.
- South Carolina briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in South Carolina
- Colleton County (42 mi) — Enactedexpires 2027-01-07
- Kershaw County (60 mi) — Proposedterm not documented
- Fairfield County (64 mi) — Proposedfixed term, end date not recorded
- Newberry County (69 mi) — Enactedexpires 2027-07-16
- Jasper County (74 mi) — Proposedterm not documented
- Mount Pleasant (75 mi) — Proposedterm not documented
- Chester County (86 mi) — Enactedexpires 2027-01-21
- Chesterfield County (89 mi) — Enactedexpires 2028-01-01
All 14 tracked actions in South Carolina 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.