Statewide data center action in Virginia
As of September 27, 2026, Virginia has a data center moratorium in force (action taken Nov 25, 2025).
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
SCC final order in Dominion's biennial review (PUR-2025-00058) creates rate class GS-5 for customers demanding 25 MW or more — in practice data centers — effective Jan 1, 2027. GS-5 customers sign long-term contracts (reported as 14 years) with minimum demand charges covering at least 85% of contracted transmission and distribution demand and 60% of generation demand, so a campus that under-uses its reservation still pays for the grid built for it. The same order cut Dominion's base-rate ask: residential bills rise $11.24/month in 2026 (23.7% less than requested) and $2.36 in 2027
SourceOfficial
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
- 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 Virginia.
- Model CBA clauses — copy-paste language communities have actually won.
- Virginia briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Virginia
- Virginia (statewide pause request) (1 mi) — Rejectedterm not documented
- Virginia (2026 General Assembly package) (1 mi) — Enactedno end date — permanent
- Spotsylvania County (47 mi) — Enactedno end date — permanent
- Fluvanna County (50 mi) — Expiredterm ran to 2026-01-31
- Stafford County (61 mi) — Enactedno end date — permanent
- Virginia (data center power tax) (67 mi) — Enactedno end date — permanent
- Culpeper County (71 mi) — Enactedno end date — permanent
- Suffolk (73 mi) — Proposedterm not documented
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.