The data center fight in Prince George's County, Maryland
As of October 1, 2026, Prince George's County, Maryland has a data center moratorium in force (action taken Jul 7, 2026; documented end date 2028-07-07).
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
2-year pause on hyperscale data centers — the longest in Maryland. Bars the planning department from considering applications until the council passes regulations. Three members abstained; one voted no
SourceNews
read 2026-08-04
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
- Prince George's County Council debates impact of data centers
- Prince George's County Council passes 2-year moratorium on new data centers
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 2 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 Maryland.
- Model CBA clauses — copy-paste language communities have actually won.
- Maryland briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Maryland
- Chesapeake Beach (20 mi) — Enactedno end date — permanent
- Calvert County (25 mi) — Enactedexpires 2027-02-28
- Montgomery County (28 mi) — Enactedexpires 2028-01-28
- Howard County (29 mi) — Enactedexpires 2027-11-02
- Baltimore City (34 mi) — Enactedexpires 2027-06-16
- Talbot County (37 mi) — Proposedterm not documented
- Baltimore County (42 mi) — Enactedexpires 2027-01-01
- Queen Anne's County (45 mi) — Enactedexpires 2027-07-29
All 21 tracked actions in Maryland 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.