Community briefing

Statewide data center action in Virginia

As of September 27, 2026, Virginia has a data center moratorium in force (action taken Mar 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

Enactedno end date — permanentstatus
Mar 2026action taken
Statelevel

Of 61 data center bills filed in the 2026 session, 15 reached the governor. Among them: HB 1393 (Dominion to petition the SCC for rates recovering new generating-capacity costs from 25 MW+ customers), HB 284 (demand-flexibility programs for 25 MW+ customers by 2029, costs not passed to other customers), SB 339 (SCC to determine whether high-load service is subsidised by other customers), SB 336 and HB 1502 (Tier 4 backup generators; one-year standby-generator pollution study), HB 496 and SB 553 (monthly water volumes reported by water utilities; annual water consumption estimates required in rezoning and permit decisions), and HB 153 (a permit process for 100 MW+ facilities with sound assessments within 500 ft of homes and schools and locality assessments of water, agriculture and historic resources). The governor's Jul 6, 2026 release says she signed the generator, local-assessment and ratepayer measures — confirm each bill's final status on LIS before citing a number

SourceNews
read 2026-09-05

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

Build a full action pack →

Nearby in Virginia

All 14 tracked actions in Virginia are on the state page.

As of August 2026 · 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