The data center fight in Wells, Nevada
As of September 27, 2026, Wells, Nevada has a data center moratorium in force (action taken Jun 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
Small rural city (Elko County) approved moratorium on data center approvals pending staff recommendations
SourceRoundup
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.
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 Nevada.
- Model CBA clauses — copy-paste language communities have actually won.
- Nevada briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Nevada
- Humboldt County (93 mi) — Enactedexpires 2027-07-13
- White Pine County (140 mi) — Enactedexpires 2027-01-18
- Fallon Paiute-Shoshone Tribe (187 mi) — Enactedno end date — permanent
- Pyramid Lake Paiute Tribe (200 mi) — Enactedno end date — permanent
- Reno (230 mi) — Enactedexpires 2027-08-31
- Nye County (339 mi) — Enactedno fixed end — runs until a condition is met
- Nye County (Pahrump) (339 mi) — Enactedno end date — permanent
- Henderson (354 mi) — Rejectedterm not documented
All 9 tracked actions in Nevada 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.