The data center fight in Pulaski County, Arkansas
Pulaski County 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
Multiple attempts failed: a May 26 vote appeared to pass but a tally error voided it (didn't reach the 10-vote two-thirds threshold); a revised version was explicitly voted down 10-3 on Jul 28. County now pursuing regulations instead
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.
Recent news
4 stories tracked since 2026-08-13 across 4 outlets. 4× A community is pushing back on a nearby data center. Most recent: “Pulaski County Planning Board postpones recommendations on proposed data center regulations” (The Arkansas Democrat-Gazette, 2026-08-13).
- Pulaski County Planning Board postpones recommendations on proposed data center regulations
- Pulaski County Planning Board postpones recommendations on proposed data center regulations
- Pulaski County holds public hearing on data center regulations
- Pulaski County planning board postpones look at data center proposal
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 4 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 Arkansas.
- Model CBA clauses — copy-paste language communities have actually won.
- Arkansas briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Elsewhere in Arkansas
- Little Rock — Rejected
- Independence County — Enactedexpires 2031-08-11
- Russellville — Enactedexpires 2027-01-31
- Union County — Enactedexpires 2027-07-09
- Carroll County — Enactedexpires 2027-06-17
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.