The data center fight in Yakima County, Washington
As of October 1, 2026, Yakima County, Washington has a data center moratorium in force (action taken Aug 12, 2026; documented end date 2027-02-12).
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
6-month moratorium in unincorporated areas, unanimous. Studying economic, health, agricultural, and water impacts
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
- Yakima County considers moratorium on data centers as community voices concerns
- Yakima County commissioners pass six-month data center moratorium
- Yakima County commissioners consider temporary moratorium on data centers
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 3 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 Washington.
- Model CBA clauses — copy-paste language communities have actually won.
- Washington briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Washington
- Kittitas County (37 mi) — Enactedexpires 2027-02-12
- Cle Elum (46 mi) — Enactedexpires 2027-01-31
- Moses Lake (69 mi) — Enactedfixed term, end date not recorded
- Pasco (72 mi) — Enactedexpires 2027-01-20
- Pierce County (82 mi) — Enactedexpires 2027-08-25
- Federal Way (98 mi) — Enactedexpires 2027-07-07
- Renton (101 mi) — Enactedexpires 2027-08-17
- Burien (105 mi) — Enactedexpires 2027-06-29
All 19 tracked actions in Washington are on the state page.
As of August 2026 (2m ago) · 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.