The data center fight in Oakland, California
As of November 15, 2026, Oakland, California has a data center moratorium in force (action taken Oct 6, 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 urgency moratorium on new data centers citywide, approved 7-0, effective immediately per KTVU. Source is news (KTVU, SFist); the ordinance text was not read. No extension found as of Oct 11, 2026.
SourceNews
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.
Recent news
9 stories tracked since 2026-11-10 across 7 outlets. 9× Local officials are moving to pause or block the project. Most recent: “Oakland City Council Unanimously Extends Data Center Moratorium for a Year” (Democracy Now!, 2026-11-12).
- Oakland City Council Unanimously Extends Data Center Moratorium for a Year
- Oakland approves 10-month ban on data centers
- SF to Consider Extending Data Center Moratorium as Oakland Approves 10-Month Extension
- Oakland extends data center moratorium for one year
- Oakland Extends Data Center Moratorium to October 2027
- Oakland City Council votes unanimously to extend data center moratorium for nearly a year
- Oakland extends data center moratorium until 2027
- Oakland to vote on data center moratorium extension
- Oakland to vote on data center moratorium extension
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 9 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 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
- San Francisco (8 mi) — Enactedfixed term, end date not recorded
- Richmond (11 mi) — Expiredterm ran to 2026-10-30
- Oakley (33 mi) — Enactedexpires 2027-04-14
- Dixon (51 mi) — Enactedfixed term, end date not recorded
- San Joaquin County (55 mi) — Proposedterm not documented
- Morgan Hill (57 mi) — Expiredterm ran to 2026-10-10
- Patterson (66 mi) — Enactedexpires 2027-07-15
- Gilroy (67 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.