The data center fight in Dixon, California
As of October 11, 2026, Dixon, California has a data center moratorium in force (action taken Sep 30, 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
45-day interim urgency ordinance on approval of new land use applications for data centers, adopted unanimously at a special meeting Sep 30, 2026 (the city's agenda lists the item; the vote is from press). Press says battery storage is also covered; the agenda title says data centers only. Ordinance number and effective date not found.
SourceOfficial
read 2026-10-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 California.
- Model CBA clauses — copy-paste language communities have actually won.
- California briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in California
- Oakley (32 mi) — Enactedexpires 2027-04-14
- San Joaquin County (45 mi) — Proposedterm not documented
- Richmond (45 mi) — Enactedexpires soon — 2026-10-30
- Oakland (51 mi) — Enactedfixed term, end date not recorded
- Calaveras County (64 mi) — Expiredterm ran to 2026-10-09
- Patterson (77 mi) — Enactedexpires 2027-07-15
- Morgan Hill (92 mi) — Expiredterm ran to 2026-10-10
- Gilroy (100 mi) — Enactedexpires soon — 2026-10-29
All 28 tracked actions in California 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.