Community briefing

The data center fight in Richmond, California

As of November 15, 2026, Richmond, California had a data center moratorium whose documented term has run out (action taken Sep 15, 2026; it ended 2026-10-30).

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

Expiredterm ran to 2026-10-30status
Sep 15, 2026action taken
Locallevel

45-day urgency interim ordinance (Gov. Code 65858). As amended, the city may accept and process applications but may not approve them or issue permits. No applications were pending. Staff said they would return before it lapses to seek an extension

SourceNews
read 2026-09-29

An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.

Recent news

5 stories tracked since 2026-10-22 across 4 outlets. 3× A community is pushing back on a nearby data center. 2× Local officials are moving to pause or block the project. Most recent: “Hundreds rally in Richmond to stop Virginia data centers” (WTVR.com, 2026-10-25).

Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 5 headlines archived.

What to do next

Build a full action pack →

Nearby in California

  • Oakland (11 mi) — Enactedfixed term, end date not recorded
  • San Francisco (12 mi) — Enactedfixed term, end date not recorded
  • Oakley (35 mi) — Enactedexpires 2027-04-14
  • Dixon (45 mi) — Enactedfixed term, end date not recorded
  • San Joaquin County (58 mi) — Proposedterm not documented
  • Morgan Hill (68 mi) — Expiredterm ran to 2026-10-10
  • Patterson (74 mi) — Enactedexpires 2027-07-15
  • Gilroy (77 mi) — Expiredterm ran to 2026-10-29

All 31 tracked actions in California are on the state page.

As of August 2026 (3m 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.

Toolkit States Tracker Search