Budget Amendments Water Rules Weakened by the Governor

Virginia’s new data center water rules are a first step, but they leave a dangerous gap for Prince William County. The budget amendments were intended to protect groundwater and drinking-water supplies from fast-growing data center demand, especially where evaporative cooling can consume large volumes of water during hot, dry periods. Yet Governor Abigail Spanberger’s final language weakened the strongest protections by allowing continued use of evaporative cooling when paired with other efficiency measures, rather than requiring truly water-minimizing systems. The final package also left Prince William out of the Fauquier and Loudoun groundwater management determination, even though all three share the fragile Culpeper Basin fractured-rock system. That distinction matters for the Potomac River watershed, the Occoquan Reservoir, and for Prince William County, where the data center pipeline is now larger and more consequential than Loudoun County’s future buildout.

What the groundwater risks are

Data centers create water risk because many facilities cool servers by evaporating water. Evaporated water is consumed, not returned to the river or aquifer for reuse. During normal conditions this may appear manageable, but during droughts and peak summer heat the same systems can sharply increase demand exactly when water supplies are most stressed. Regional water experts at the ICPRB have warned that data center consumptive use in the Washington metropolitan area could grow from about 8% of total consumptive use in 2025 to 25% by 2035, and that peak-day water demand can rise substantially during hot weather. The risk is not only total annual use; it is the cumulative impact of many large facilities drawing from shared public systems, aquifers, and watersheds at the same time.

• Groundwater depletion: Heavy withdrawals can reduce aquifer levels faster than they recharge, especially in areas already facing long-term groundwater decline or seasonal limits. Increased impervious surfaces reduces recharge.
• Drought vulnerability: Evaporative cooling demand is highest during hot, dry periods, when residents, farms, streams, and public utilities also need reliable water.
• Water-quality concerns: Cooling systems can produce concentrated discharge, the blowdown, that may contain salts, metals, treatment chemicals, or other contaminants that wastewater systems cannot manage.
• Cumulative impacts: A single facility may not appear decisive, but clusters of facilities can overwhelm planning assumptions when many are approved before regional water limits are fully understood.

Why groundwater protection is important

Groundwater protection is essential because aquifers are slow to recover and are a shared public resource. Once groundwater levels decline, the consequences can last for years or decades: drinking-water wells can become less reliable, utilities may face higher treatment and supply costs, streams can lose baseflow, and communities may be forced into expensive infrastructure decisions after the damage is already visible. For Northern Virginia, the issue is especially serious because data centers are concentrated in the Potomac basin, which supplies drinking water to millions of people and supports the Washington metropolitan region. Protection must happen before permitting decisions lock in decades of water demand.

• Prevention is cheaper than correction: It is far less costly to require water-saving cooling systems up front than to retrofit facilities or expand water infrastructure after shortages emerge.
• Water is a public necessity: Drinking water, agriculture, fire protection, streams, and household use should not compete with avoidable industrial consumption during drought.
• Transparency is necessary: Without clear reporting of data center water use, local governments and residents cannot evaluate whether approvals are sustainable.

What the budget amendments tried to do

The original budget language attempted to create Virginia’s first targeted guardrails for data center water consumption. It directed the Department of Environmental Quality to define “Cooling Water Scarcity Areas” by July 1, 2027, where evaporating water for cooling could reduce the quality or quantity of water available for other beneficial uses. In those areas, data centers would have to minimize water use for cooling by relying on air cooling, closed-loop systems, recycled water, stormwater, or similarly efficient technologies to the maximum extent practicable. The budget also created special rules for the Eastern Virginia Groundwater Management Area, requiring new data centers seeking certain air permits after January 1, 2027, to use air cooling, 100% recycled water or stormwater, or a closed-loop system.

In plain terms, the amendments tried to do four things:

First, they tried to identify places where cooling-related water consumption could create scarcity. Second, they tried to move new facilities toward water-saving cooling technologies before new demand became permanent. Third, they tried to protect the most vulnerable groundwater region in eastern Virginia with a clearer baseline standard. Fourth, they began to address the lack of public data by requiring more transparency around data center water sales and use.

How Governor Spanberger weakened the protections

The strongest version of the policy would have pushed data centers away from highly consumptive evaporative cooling in water-stressed areas. Governor Spanberger’s amendment weakened that standard by allowing evaporative cooling to continue if it is used “in conjunction with” other water-efficient methods. That change matters because a hybrid system can still evaporate large amounts of water during the hottest parts of the year. In practice, it lets operators claim efficiency while preserving the very cooling method that creates the greatest consumptive water risk.

The amendment also leaves a timing problem. DEQ does not have to define Cooling Water Scarcity Areas until July 2027, and the broader compliance date extends to 2032. That creates a permitting window in which projects can move forward before scarcity boundaries, enforceable standards, and cumulative water impacts are fully resolved. For communities facing rapid data center growth, delay functions like a loophole.

Why Prince William County faces added risk compared with Loudoun County

Prince William County faces a sharper forward-looking risk because its data center pipeline is expanding while Loudoun County is becoming more constrained. Loudoun remains the global data center hub, with reports describing roughly 200 operating data centers and a large existing footprint. But Loudoun has tightened zoning and has fewer suitable parcels left for by-right development. By contrast, Prince William has positioned large areas for data center growth and has major projects already approved, under construction, or proposed.

This omission is especially serious because the Culpeper Basin is a fractured-rock basin, not a broad, layered coastal plain aquifer like the Potomac system. In the Potomac aquifer, water is stored and moves through more continuous sediment layers; in the Culpeper Basin, water availability depends on irregular fractures in hard rock. That makes supply more localized, less productive, harder to model, and more vulnerable to well interference. Pumping from one high-capacity well can lower water levels in nearby fractures, reduce yields in neighboring wells, or intercept groundwater that would otherwise discharge to streams as baseflow. More future buildout pressure: Prince William has been reported to have at least 44 existing data center buildings totaling about 8.3 million square feet, with enough approved, under-construction, or otherwise active projects to potentially exceed 80 million square feet. That would surpass Loudoun’s projected buildout ceiling of about 40 million square feet in the next decade.

• More pipeline uncertainty: Other regional reporting has described Prince William as having dozens of planned data centers, including about 23 million square feet across roughly 1,500 acres, while Loudoun already has a mature base and a more restrictive approval environment.
• Left out of the Fauquier/Loudoun groundwater review: Prince William was omitted from the budget language directing DEQ to evaluate whether western Loudoun and Fauquier need a Groundwater Management Area, even though western Prince William lies in the same fragile Culpeper Basin fractured-rock system. That omission treats groundwater as if it stopped at county lines, when fractured-rock aquifers move through connected cracks, faults, joints, and weathered zones across the basin.
•  Unmonitored and unmanaged withdrawals: Because Prince William was left out, large data centers could rely on groundwater without the same basin-wide monitoring, withdrawal accounting, or management review being considered for Loudoun and Fauquier. In a fractured-rock basin that is far less productive and less predictable than the layered Potomac aquifer, that creates direct risk for private wells, community wells, and the groundwater-fed baseflow that sustains streams and rivers feeding the Occoquan Reservoir.
• Potomac watershed exposure: Rapid growth in Prince William would add demand in the Potomac basin, where regional studies already identify data center water use as a growing concern during drought and peak summer demand.

The bottom line

The budget amendments recognized the right problem: data centers can place serious cumulative stress on groundwater, public water systems, and the Potomac watershed, especially when evaporative cooling expands during drought and heat. But the final language does not go far enough. By permitting hybrid evaporative cooling, delaying enforceable scarcity designations, and leaving Prince William out of the Fauquier/Loudoun groundwater management determination, Governor Spanberger’s amendments weakened the standard at the moment Virginia needed a clear statewide rule. Prince William County is especially exposed because it has a larger future pipeline than Loudoun County, sits in the same fragile Culpeper Basin fractured-rock system, and could allow data centers to draw unmonitored and unmanaged groundwater that endangers private wells, community wells, and the baseflow of streams and rivers feeding the Occoquan Reservoir.

Grid Emergency Exposes Northern Virginia’s Data Center Planning Failure

The Mid-Atlantic’s power emergency is not simply a heat-wave story. It is the predictable result of allowing electricity demand from data centers to surge while retiring or constraining dispatchable fossil-fuel generation without building enough reliable replacement capacity. Now, as dangerous heat drives residents to depend on air conditioning, officials are being forced into an impossible tradeoff: keep the power on to prevent heat-related deaths, or protect communities from the air pollution produced by emergency fossil-fuel and diesel backup generation.

On June 30, the U.S. Department of Energy issued two emergency orders authorizing PJM Interconnection to take extraordinary steps to stabilize the grid through July 3. One order directs PJM to dispatch specified generating units as needed to maintain reliability. The other allows PJM, working with utilities and transmission owners, to call on backup generation resources before or during the most severe emergency stage, when firm power interruptions may otherwise be necessary.

The orders are framed as emergency tools, but the emergency itself has been years in the making. PJM’s region includes the nation’s densest concentration of data centers, especially in Northern Virginia, where power demand has grown faster than planners, regulators, utilities and developers have matched with dependable supply. At the same time, the region has leaned into the retirement or restricted operation of fossil-fuel plants without ensuring that clean replacements, transmission upgrades, storage and demand-response programs would arrive fast enough.

PJM had already warned that summer peak demand is its central reliability test, and that extreme temperatures could require demand-response resources to reduce load. But this week’s emergency makes clear that voluntary reductions and paper reserves are not enough when a heat wave collides with data-center growth, delayed infrastructure and a shrinking margin for error.

The public-health dilemma is stark. Rolling blackouts during extreme heat can be deadly, especially for elderly residents, people with medical needs and families without safe cooling options. But avoiding blackouts by running thousands of diesel engines near homes, schools and vulnerable communities creates its own health threat, adding nitrogen oxides, fine particulate matter and other pollutants to the air at precisely the moment when heat can worsen respiratory and cardiovascular risks.

The capacity problem is no longer theoretical. The December 2025 PJM power auction failed to secure enough firm power to meet the targeted reserve margin, leaving the grid on track for a 14.8% margin rather than the 20% target for the 2027/2028 delivery year. That shortfall has pushed PJM, regulators and utilities toward a stopgap strategy that treats large customers—especially data centers—not only as power consumers, but as emergency power sources of last resort.

Those measures may help keep the lights on, but they also reveal a troubling reality: Northern Virginia could become a de facto diesel power plant whenever the grid is under stress. That outcome conflicts with the spirit of Virginia’s clean-energy goals and shifts pollution burdens onto communities that never consented to become the backup power source for the digital economy.

The planning gap is especially serious because Virginia regulators have acknowledged that they have not performed cumulative air-quality modeling for these data-center generator clusters. Permitting individual engines one facility at a time is not the same as understanding what happens when thousands of engines operate across the same region during the same emergency.

If PJM declares a grid stress event, generator zones in places such as Ashburn and Gainesville could effectively become primary power sources for data centers. In that scenario, residents could face the simultaneous risks of extreme heat, grid instability and concentrated diesel exhaust—an untenable bargain created by years of under-planning.

The sharp lesson is that reliability and public health cannot be planned separately. A region cannot invite explosive data-center growth, retire or restrict reliable generation, delay transmission and clean-capacity buildout, and then expect emergency diesel to solve the problem without consequences. The current crisis is not an act of nature. It is a failure of foresight, and residents are being asked to breathe the consequences while depending on the same emergency measures to survive the heat.

Groundwater: What It Is

Groundwater

Groundwater is freshwater stored underground in the tiny pores, cracks, and open spaces within soil, sand, and rock. It represents the vast majority (95%) of Earth’s available liquid freshwater—far more than the water visible in lakes and rivers.

A common myth is that groundwater usually exists as underground rivers or cavernous lakes. In most places, it behaves more like water held in a giant underground sponge, saturating the porous materials beneath our feet.

 
Underground Anatomy

• A cross-section of the ground reveals several layers, each defined by how it stores and transmits water:
• The Unsaturated Zone: This is the top layer of earth closest to the surface. The spaces between dirt and rock here contain mostly air, with some moisture that feeds plant roots.
• The Water Table: The boundary where the unsaturated zone ends and the fully saturated ground begins. Depending on local geology and rainfall, the water table may be near the surface or hundreds of feet below it. In parts of Prince William County, it can be relatively shallow.
• The Saturated Zone: Located beneath the water table, this is the region where every single crevice, crack, and pore is completely filled with water. This trapped water is what we call groundwater.

What Is an Aquifer

When an underground geological formation holds enough water and is permeable enough to allow that water to move, it is called an aquifer. Aquifers are typically composed of gravel, sand, sandstone, or fractured limestone.

 

• Porosity vs. Permeability: To be a good aquifer, rock needs high porosity (plenty of empty space to hold water) and high permeability (those spaces must be interconnected so water can flow through them). Clay, for example, is porous but has very low permeability, meaning water gets trapped and cannot flow.
• Slow-Moving Flow: Groundwater does not rush like a surface stream. It creeps through pore spaces and fractures, often moving only inches or feet per day. Because of this slow movement, water in deep aquifers may remain underground for thousands of years. In the Piedmont section of Prince William County, groundwater is often much younger—ranging from months to roughly a decade.

The Recharge and Discharge Cycle

Groundwater is an active, shifting stage of the global hydrologic (water) cycle:

• Recharge: Rain and melting snow soak into the ground, and some of that water travels downward to the water table. The portion that survives plant uptake, evaporation, and shallow soil storage is called recharge. Forest loss and impervious surfaces—such as roads, buildings, patios, and even compacted suburban lawns—reduce the amount of water that can recharge groundwater.
• Discharge: Groundwater naturally moves from higher-pressure areas toward lower-pressure areas. Where the land surface intersects the water table, groundwater can emerge as springs or seep into wetlands, lakes, and streams. This groundwater contribution, known as baseflow, helps sustain streams and rivers during dry periods.

More Thoughts on the Budget Item 366 #2c

Item 366 #2c also directs DEQ to study groundwater conditions in western Loudoun and Fauquier Counties and report back by December 31, 2026. The key parts are that DEQ must evaluate groundwater levels and quality, assess current and future withdrawals, consider whether a Groundwater Management Area is needed, and recommend any statutory or regulatory changes needed to protect existing residents and commercial users. In plain English, the amendment asks DEQ to decide whether groundwater in those areas is under enough stress to justify stronger state oversight.

The problem is that the language is written around county boundaries, not around the actual groundwater system. The Culpeper Basin does not stop at the Loudoun–Fauquier line. It extends into Prince William County, and the same fractured-rock formations, recharge areas, streams, and groundwater pathways can cross political borders. By naming only Loudoun and Fauquier, Item 366 #2c leaves out a major part of the same hydrogeologic system.

Prince William was left out because the amendment was drafted around political advocacy, not groundwater science. The Loudoun and Fauquier delegations succeeded in getting their counties named, but the Prince William delegation failed to insist that Prince William be included even though the same Culpeper Basin extends into the county. That omission matters. It shows that the delegations involved did not fully understand—or did not adequately account for—the nature of groundwater as a connected, hidden, slow-moving system that crosses county lines.

That political failure creates a serious scientific problem. It will be very difficult to evaluate only the Loudoun and Fauquier portions of the Culpeper Basin while excluding Prince William, because groundwater does not flow according to county lines. In fractured-rock systems, water moves through connected cracks, faults, bedding planes, and weathered zones. One area may serve as a recharge zone, another as a discharge zone, and pumping in one jurisdiction may affect water levels or stream baseflow in another. If Prince William is outside the study area, DEQ may be forced to analyze only part of the system while leaving out a connected portion that could influence the results.

Separating the Culpeper Basin into county-sized pieces is especially difficult because fractured-rock groundwater is already hard to map. Unlike a surface reservoir, the water is hidden underground and moves unevenly through geologic pathways that may not be obvious from the surface. A well in Loudoun or Fauquier may respond differently from a nearby well in Prince William, not because the aquifer is separate, but because the fractures connecting them are complex. Without a basin-wide monitoring network, it is hard to know whether water-level changes are local, regional, seasonal, or caused by withdrawals elsewhere.

The practical consequence is that Item 366 #2c may identify risks in Loudoun and Fauquier while missing or underestimating risks in Prince William. It may also make it harder to determine whether groundwater stress is coming from within the studied counties or from connected development and pumping outside the study boundary. For that reason, the study should be expanded to include the Prince William portion of the Culpeper Basin, or at minimum require DEQ to evaluate the basin as one connected groundwater system rather than three separate political jurisdictions.

 

Culpeper Basin Loophole in the Budget Amendment

Item 366 #7c  in the newly approved Virginia Budget gives Virginia a new framework for regulating water-intensive data center cooling, but its most important weakness may be what it does not clearly cover: the unmonitored Culpeper groundwater basin. The amendment focuses heavily on the Eastern Virginia Groundwater Management Area and on future “Cooling Water Scarcity Areas,” yet it does not appear to automatically apply the same immediate restrictions to groundwater withdrawals from the Culpeper Basin. That creates a potential loophole for large water users that can draw from groundwater outside the state’s most closely regulated areas.

What the Amendment Gets Right

The amendment’s strength is that it recognizes evaporative cooling as a regional water-supply issue, not merely a site-specific utility issue. By directing the Department of Environmental Quality (DEQ) to establish “Cooling Water Scarcity Areas,” the state can focus on places where cooling-related evaporation may reduce water available for drinking water, environmental flows, agriculture, or future growth. If applied broadly, this framework could help prevent data center development from shifting water stress from one basin to another.      

• It creates a scarcity trigger: DEQ can identify areas where cooling demand threatens the quantity or quality of available water.
• It pushes better cooling technology: Data centers in designated areas may need to use air cooling, closed-loop systems, recycled water, or stormwater to the maximum extent practicable.
• It recognizes shared water impacts: The amendment acknowledges that water withdrawals, wastewater reuse, and evaporative loss can affect communities beyond the project site.
• It gives regulators a future pathway: Even if a basin is not immediately covered, DEQ may later designate it as a scarcity area if the evidence supports intervention.

The Culpeper Basin Loophole

The central problem is that the amendment’s strictest groundwater language is tied to the Eastern Virginia Groundwater Management Area. The Culpeper Basin is different. If it remains outside that formal management structure and lacks robust monitoring, then large groundwater withdrawals (which are not seen) may not trigger the same immediate restrictions, even if they support water-intensive cooling or industrial development.

•  No automatic January 2027 restriction: Facilities using Culpeper Basin groundwater are not subject to the same immediate “zero potable water” standard that applies inside the Eastern Virginia Groundwater Management Area.
• Weak evidence base: Without a groundwater monitoring network, if withdrawals are not closely monitored, DEQ may have difficulty proving that cooling-related demand is causing or likely to cause scarcity.
• Incentive to relocate water demand: Developers may have a reason to favor groundwater sources that are less visible or less regulated than surface-water systems.
•  Delayed regulatory response: DEQ may need years of rulemaking, monitoring, and basin analysis before the Culpeper Basin can be brought under scarcity-area restrictions. Unless the law is amended.

Why the Loophole Matters

The loophole matters because water stress is not limited to basins that are already monitored. If a data center or industrial user can rely on an under-monitored aquifer, the state may not see the full impact until wells decline, nearby users experience supply problems, or streams connected to groundwater lose baseflow. In that situation, the amendment could become reactive rather than preventive.

• Monitoring comes before enforcement: Without withdrawal data, groundwater levels, and basin-specific modeling, DEQ may lack the record needed to designate the area as water-scarce.
• Groundwater impacts can be delayed: Aquifer depletion may not appear immediately, which makes it easier for withdrawals to grow before the risk is formally recognized.
• Surface-water rules may miss groundwater stress: A facility that does not draw directly from the Potomac or Occoquan systems can still affect regional water availability through groundwater pumping.
• The amendment may shift pressure inland: If surface-water corridors face tighter scrutiny, less-regulated groundwater basins could become attractive alternatives for water-intensive projects.

Connection to Northern Virginia Water Conflicts

The Culpeper Basin issue should be understood alongside the region’s existing disputes over the Potomac River, the Occoquan Reservoir, and UOSA wastewater flows. The amendment gives DEQ a clearer path to regulate evaporative cooling where surface-water scarcity can be demonstrated, but groundwater use outside established management areas may remain harder to control. This creates an uneven regulatory landscape: surface-water-dependent projects may face scrutiny sooner, while groundwater-dependent projects may avoid comparable review until monitoring catches up.

That uneven treatment could distort development decisions. If Loudoun, Prince William, or nearby jurisdictions face future scarcity-area limits tied to Potomac or Occoquan impacts, developers may look toward less-monitored groundwater basins as a workaround. The result would not necessarily reduce total water demand; it could simply move the demand into aquifers where impacts are less visible and harder to quantify.

What the Amendment Does Not Yet Solve

The amendment does not appear to automatically close the Culpeper Basin loophole. It creates a regulatory pathway, but it does not by itself guarantee basin-wide monitoring, require immediate groundwater withdrawal limits outside the Eastern Virginia Groundwater Management Area, or impose the same standards on every data center that relies on groundwater.

To close the gap, DEQ would likely need to build a stronger factual record for the Culpeper Basin. That means measuring withdrawals, tracking groundwater levels, assessing connections between groundwater and surface-water systems, and determining whether cooling-related use could reduce water available for other beneficial purposes. Without that record, the amendment’s strongest tools may remain difficult to apply.

• It does not automatically regulate every groundwater basin. Areas outside existing groundwater management structures may require separate designation or rulemaking.
• It does not solve the monitoring problem. If the Culpeper Basin lacks sufficient data, enforcement may lag behind actual water demand.
• It does not prevent strategic siting. Developers may still seek locations where groundwater access is easier and regulatory scrutiny is lower.
• It does not guarantee immediate conservation. The amendment depends on DEQ action, technical evidence, and future implementation decisions.

Bottom Line

The budget amendment is a useful step because it gives Virginia a way to restrict water-intensive cooling where scarcity can be shown. But its biggest weakness may be the Culpeper Basin loophole: if groundwater withdrawals from that basin are not monitored and are not automatically covered by the amendment’s strictest provisions, large water users may be able to avoid the very scrutiny the amendment is meant to create. For the amendment to work as a true water-protection measure, DEQ will need authority, data, and political will to treat under-monitored groundwater basins as potential scarcity areas before overuse becomes irreversible. Or, the Culpeper Basin must be designated as a Groundwater Protection Area under an amendment of the law.

What the Ads Aren’t Telling You About Data Centers

The Hydrological Forecast is from the ICPRB, the water use data is from PW Water

A rebuttal to the industry’s polished pitch in Northern Virginia

If you’ve turned on a television in Northern Virginia lately, you’ve probably seen the glossy ads from Virginia Connects and other industry-backed campaigns. The message is soothing and simple: data centers are quiet neighbors, modest users of local resources, and generous contributors to schools, roads, and jobs.

That message is also incomplete. The ads ask residents to imagine “the cloud” as weightless, green, and nearly invisible. But here in Data Center Alley, the cloud has a physical footprint: transmission lines, substations, backup diesel generators, water withdrawals, stormwater runoff, and rising pressure on household utility bills. This is a rebuttal to the sales pitch and a reminder that Virginians deserve the whole story before being asked to subsidize the next wave of growth.

Claim 1: “Data centers barely use water.”

One of the industry’s favorite talking points is that many data centers do not use water for cooling “96% of the time.” That sounds reassuring until you look at what the number leaves out. It measures duration, not impact. In other words, it focuses on how many hours a facility may avoid evaporative cooling, while downplaying what happens during the hottest, driest, highest-demand hours of the year.

In Virginia’s climate, outside air may handle cooling much of the year. (It was real cold last winter.) But when temperatures climb in the summer and demand peaks, evaporative systems can consume large volumes of water precisely when rivers, reservoirs, and residents are under the greatest stress. The public deserves to know not just whether a facility uses water, but how much it uses during peak summer conditions, and that number is over 10% and growing.

The ads also tend to focus narrowly on onsite cooling. That leaves out the water consumed indirectly through electricity generation which is reported to be 90% of a data center’s water footprint. A data center that draws enormous power from the grid shifts part of its water footprint to power plants that cool turbines and equipment. Calling that “water free” is not transparency- it is accounting by omission.

Claim 2: “Water-positive pledges solve the problem.”

Major tech companies often point to “water positive” goals as proof that they are part of the solution. But water is not like carbon dioxide. A gallon saved in another watershed does not refill the Potomac, the Occoquan, or a local reservoir during a Virginia heatwave. The Interstate Commission on the Potomac River Basin (ICPRB) projects that by 2040 summer water use by data centers already in the pipeline with increase demand by 80 million gallons of water a day.

That geographic mismatch matters. If a facility’s local operations stress a local water supply, then the mitigation must be local, measurable, enforceable, and timed to the same season of demand. Otherwise, “water positive” becomes a public-relations phrase rather than a real safeguard for Virginia communities.

The same problem applies to offset-style projects that sound impressive in an advertisement but do little to address the specific burden placed on local residents. Virginians should ask a simple question: does the promised benefit happen here, when we need it, and at a scale that matches the impact?

Claim 3: “Dry cooling makes the resource problem disappear.”

Dry cooling can reduce direct water use, but it does not make the problem vanish. It often shifts the burden from water to electricity. Mechanical air-cooled systems rely on large fans and chillers, and those systems have to work hardest during the same heat waves when families are running air conditioners and the grid is under maximum strain.

So, when an ad suggests that a facility is environmentally benign because it uses less water, residents should ask the follow-up question: how much additional electricity does that choice require, and who pays for the generation, transmission, and reliability upgrades needed to support it?

Claim 4: “Efficiency gains will offset AI growth.”

The industry’s older efficiency story was built around conventional cloud computing. The AI boom changes the equation. High-density AI racks can draw far more power than traditional server racks, and they generate heat that is harder to manage with ordinary air cooling.

That means yesterday’s efficiency talking points cannot be used to wave away tomorrow’s load growth. If AI facilities require dramatically more power per square foot, the public should see updated, project-specific projections—not broad assurances built on the technology mix of the past.

Claim 5: “Backup generators are only for emergencies.”

Data centers are often promoted as clean, high-tech infrastructure, but many rely on large fleets of diesel backup generators. The industry describes these generators as rarely used, but their role has becomes more complicated. When the grid is strained and large customers are asked to reduce load or island themselves from the system. The grid is using them as additional power in their reserve calculations.

That raises a basic public-health question: if diesel engines are part of the reliability plan for a region packed with data centers, how are emissions monitored, limited, and disclosed to nearby communities? Residents should not have to accept unexamined pollution risks as the hidden cost of keeping the cloud online.

Demand-response payments and emergency operations also deserve scrutiny. If large facilities are compensated for reducing demand during crises caused in part by rapid load growth they brought, then regulators should ensure that ratepayers are not paying twice: once for the infrastructure buildout and again for temporary relief when that infrastructure proves insufficient.

Claim 6: “Data centers pay their own way.”

The ads emphasize tax revenue, but the cost side of the ledger is just as important. New substations, transmission lines, generation capacity, water infrastructure, road improvements, and emergency services are not free. When growth is fast enough, the question is not whether data centers pay something. The question is whether they pay the full marginal cost of the new infrastructure they require.

·         The ad version: Data centers generate tax revenue and support public services.

·         The missing context: Rapid load growth can require expensive new infrastructure, and those costs can place risk on households and small businesses unless regulators create strong protections.

That is why the debate over high-load rate classes and cost allocation matters. These policies are not anti-technology; they are basic consumer protection. If a facility needs enormous new grid capacity, ordinary residents should not be left carrying the financial risk if demand forecasts change or speculative projects fail to materialize.

Don’t Let Advertising Substitute for Accountability

The data center industry is not wrong that digital infrastructure matters. It does. But importance is not a blank check. Northern Virginia can support technology without accepting secrecy, weak siting rules, vague offsets, hidden water impacts, or utility bills that rise to finance private growth.

So, the next time a polished TV ad tells you that data centers are quiet, clean, and cost-free neighbors, remember what the ad leaves out. Ask for local water data. Ask who pays for the next transmission line. Ask how diesel emissions are monitored. Ask whether “water positive” means anything in our watershed. Ask whether the companies profiting from AI expansion are paying the full cost of the infrastructure they require. Virginia does not need more slogans. It needs transparency, enforceable standards, and a growth policy that protects residents first.

Cascading Failures in DC Water's Pipes

For decades, DC Water postponed maintenance and pipe replacement across its water and sewer systems. Improvements under George Hawkins helped, but they were not enough to prevent today’s cascading failures. Before his tenure, DC Water replaced about 0.3% of its pipe network each year; Hawkins raised that rate to 1.0% annually.

Still, replacing pipes on a 100-year cycle when many are rated for only 75 years created a growing replacement deficit. That shortfall is now producing major emergencies, including the January 2026 collapse of the Potomac Interceptor, which was reportedly only 64 years old.

Although a 64-year-old pipe is younger than many 19th-century water mains beneath downtown Washington, D.C., concrete sewer interceptors are exposed to distinct chemical stresses.

A reinforced concrete pipe of this type typically has an engineering life of about 50 to 75 years. After six decades in service, the Potomac Interceptor had suffered severe internal corrosion from sewer gases, weakening the concrete until the 72-inch line collapsed beneath the Clara Barton Parkway.

The Replacement Rate Gap

• The “300-Year” Era: Before George Hawkins’ tenure (2009–2017), DC Water replaced roughly 0.3% of its pipes each year, implying a replacement cycle of about 300 years.
• The Hawkins Reform: Hawkins warned publicly about the danger of that pace. He tripled the replacement rate to 1% per year—a 100-year cycle—and introduced a System Availability Fee to help fund the work.
• The “Never Caught Up” Reality: Hawkins acknowledged that the utility was still making up for a century of deferred maintenance and that “the bill has come due.” Even at 1% per year, the system cannot keep pace with post-World War II pipes that typically last about 75 years.

The “Cascading Failures”

Recent high-profile infrastructure failures in 2026 show that the effects of deferred maintenance are no longer theoretical. The backlog has become a physical reliability crisis, not just a financial liability.

• Potomac Interceptor Collapse (Jan. 2026): A 72-inch sewer pipe failed in Maryland in a major event consistent with cascading infrastructure collapse. The single failure released an estimated 240–300 million gallons of raw sewage into the watershed and was attributed to deterioration in a system built in the 1960s that had exceeded its useful life.
• Systemic Fragility: The impacts are compounding. The January 2026 collapse forced DC Water to seek federal emergency aid and prompted a negligence lawsuit from the state of Maryland.
• Water Main Breaks: The system also continues to experience frequent breaks, especially during cold snaps. In early 2026, aging pipes exposed to cold river water contributed to hundreds of breaks in a single month.

In short, the “cascading failures” described here have been occurring throughout the first half of 2026.

The system’s fragility was evident in the January sewer collapse, a wave of winter water main breaks, and June emergency repairs aimed at preventing another disaster. Last winter as temperatures fell, aging mains—many rated for 75 years but in service longer—failed under thermal stress. Notable examples include:

• Georgetown (Feb. 5): A major break flooded an underground parking garage, sent water through walls, and closed nearby roads.
• Southeast DC (Feb.): A severe main break at 51st Street and Southern Avenue damaged homes and left some basements submerged. DC Water accepted liability in April
• Downtown DC (Jan. 26): A 12-inch main burst at 14th and I Streets NW, disrupting traffic in the city center.
• Routine Failures: Throughout late January and early February, crews repaired multiple 8-inch mains, including on 46th Street SE and 15th Street NW, as the system struggled with cold conditions.

3. Recent Emergency Actions (June 2026)

Failures earlier in the year shaped the utility’s actions heading into summer.

• Emergency Interceptor Repairs (June 15): Crews began emergency work to reinforce a corroded section of the Potomac Interceptor near Pennyfield Lock. Inspections found exposed rebar and significant deterioration, requiring immediate action to avoid another spill like the January collapse.
• Boil Water Advisory (June 5): Although not a pipe burst, a failure at the Fort Reno Pumping Station caused a major pressure loss and triggered a boil water advisory for 5,000 homes in Upper Northwest DC. The incident underscored the fragility of the pumps and valves that support the pipe network. 

Moving from a 300-year to a 100-year replacement cycle was a major administrative improvement, but it was still not enough to stop the system’s aging curve. Pipes rated for 75 years—especially those installed in the mid-20th century—are failing faster than the 100-year replacement schedule, producing the emergency failures seen in 2026.

DC Water’s infrastructure is old even by national standards, and catching up is not a one-time expense but a multi-decade commitment measured in billions. The median DC water pipe is 79 years old, meaning half of the city’s 1,300 miles of pipe were installed before 1936. Some mains still in service date to the 1860s. The sewer system is similarly old: roughly half of all sewer lines are more than 84 years old, and the system’s core dates to around 1810, making it among the oldest in the country.

There is no single price tag for “fixing everything” because replacement is a continuous process. Current commitments are about $1 billion per year for the next decade, and even that primarily supports the 100-year replacement-cycle catch-up. In practice, catch-up funds are often diverted to emergencies.