The data center fight in Jasper County, South Carolina
As of September 27, 2026, Jasper County, South Carolina has a data center moratorium under consideration (action taken Sep 9, 2026).
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
First reading passed for one-year moratorium on data centers, crypto mining, and data processing in unincorporated areas; two more readings required.
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
- Jasper County pauses new data centers with one-year moratorium
- Jasper County Council approves 1-year moratorium on data centers
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 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 (38 mi) — Enactedexpires 2027-01-07
- Mount Pleasant (72 mi) — Proposedterm not documented
- Orangeburg County (74 mi) — Enactedexpires 2027-07-23
- Newberry County (132 mi) — Enactedexpires 2027-07-16
- Kershaw County (134 mi) — Proposedterm not documented
- Fairfield County (136 mi) — Proposedfixed term, end date not recorded
- Greenwood County (139 mi) — Enactedexpires 2027-07-21
- Laurens County (154 mi) — Proposedterm not documented
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.