Forbes reported on July 10, 2026 that a Meta AI data center has been linked to rare bacteria detected in a city’s water system — a striking escalation of the long-running debate over how much water AI data centers consume, into a question about what they may put back. The headline alone frames the story; the publicly circulated material does not name the city, identify the bacteria, or explain the mechanism of the alleged link.

The report lands as Meta and its hyperscale peers are in the middle of the largest data center construction wave in history, much of it cooled — directly or indirectly — with municipal water.

Executive Summary

According to Forbes, a Meta data center built to serve the company’s artificial-intelligence workloads has been connected to the presence of a rare bacteria in the water system of a nearby city. If substantiated, this would mark a significant shift in the data center water debate: for years the argument has centered on quantity — how many millions of gallons evaporative cooling draws from local supplies — while this story raises a quality and public-health dimension.

Why it matters: water is the quiet dependency of the AI buildout. Many large data centers use evaporative cooling, in which water absorbs server heat and is partially evaporated away, because it is dramatically more energy-efficient than pure air-based cooling. That efficiency comes with entanglement — data centers become major customers of, and in some configurations discharge back into, the same municipal systems that serve residents.

Important caveat up front: ‘linked’ is doing heavy lifting in this headline. The available material does not establish causation, name a health authority’s finding, or describe Meta’s response. This article analyzes the stakes while flagging exactly what remains unverified.

When the Water Debate Becomes a Public-Health Story

Data center water use has been a community flashpoint for several years, but the framing has been almost entirely volumetric: how many gallons per day, whether aquifers or reservoirs can sustain it, and whether households pay more as a result. A bacteria-in-the-water-system story changes the emotional and regulatory register entirely. Volume disputes are negotiated in rate cases and zoning hearings; contamination questions summon health departments, environmental regulators, and — fairly or not — a much deeper reservoir of public anxiety.

Mechanically, there are plausible pathways for a large industrial water user to interact with a municipal system’s water quality: heavy draws can change pressure and flow patterns in distribution pipes, warm discharge or blowdown water (the mineral-concentrated water periodically flushed from cooling systems) must be treated and returned somewhere, and large open-loop cooling towers are themselves known habitats for waterborne bacteria such as Legionella. To be clear, none of these mechanisms is confirmed in this case — the source material does not say which, if any, applies. But they explain why a ‘link’ claim is at least technically conceivable rather than absurd on its face.

What ‘Linked’ Does and Does Not Establish

The scrutiny has to run in every direction. For the reporting: what evidence supports the link — sampling data, a utility investigation, a health-department finding, or expert inference? Correlation between a new industrial water customer and a new detection is not causation; municipal systems detect unusual organisms for many reasons, including aging pipes, source-water changes, and improved testing. For Meta: what water does the facility draw, what does it discharge, under what permit, and what monitoring does it publish? For the utility and local officials: what does the testing history show before and after the facility came online, and has anyone actually been harmed?

The honest answer, based on what has circulated publicly, is that we cannot yet distinguish between three very different stories: a genuine contamination pathway traced to the facility, a coincidental detection amplified by the data center’s high profile, or something in between — for example, system stress that made an existing problem visible. Each has radically different implications, and readers should hold all three open until primary documents surface.

The Economics of Water in the AI Buildout

Hyperscalers use water because physics and economics reward it. Evaporative cooling can cut a facility’s cooling energy dramatically compared with mechanical chillers, lowering both operating cost and the grid capacity a site must secure — often the binding constraint on AI campuses measured in hundreds of megawatts. The industry’s own metric, water usage effectiveness (WUE), exists precisely because operators know the trade-off is real: save electrons, spend water.

That calculus is shifting. Direct-to-chip liquid cooling and closed-loop systems — which recirculate a fixed volume of water or coolant rather than continuously evaporating fresh supply — are increasingly standard for dense AI hardware, and several operators have announced designs that consume little or no water for cooling. A public-health controversy, even an ultimately unproven one, accelerates that shift by adding reputational and permitting risk to the cost side of the evaporative-cooling ledger. Communities negotiating with data center developers now have one more reason to demand closed-loop designs, discharge transparency, and independent water-quality monitoring as conditions of approval.

Winners, Losers, and the Precedent That Matters

If the link is substantiated, the losers are obvious: the affected community first, then Meta’s siting pipeline, and then every operator whose pending permits get re-examined through a public-health lens. The beneficiaries would be vendors of waterless and closed-loop cooling, water-treatment and monitoring firms, and jurisdictions that wrote strong discharge and reporting requirements into their agreements and can now point to them.

If the link is not substantiated, the story still matters, because permitting battles run on narrative as much as data. The industry has often been slow to publish site-level water data, treating it as competitively sensitive; that opacity leaves a vacuum that headlines fill. The durable lesson either way is that transparency is cheaper than suspicion: operators who publish withdrawal, discharge, and monitoring data before a controversy get to argue from their own numbers rather than someone else’s framing.

Background

Meta operates one of the world’s largest data center fleets and has been expanding it aggressively to support its artificial-intelligence ambitions, with new campuses whose power demands are measured in the hundreds of megawatts and beyond. Like its hyperscale peers, the company has faced recurring community scrutiny over local resource impacts — power, land, and especially water — and, like those peers, has publicized water-restoration commitments intended to offset consumption.

Until now, the water controversy around AI infrastructure has been overwhelmingly about scarcity: whether local systems can supply large evaporative-cooling loads without straining households and agriculture. A report tying a facility to bacteria in a municipal system — whatever its ultimate substantiation — moves the debate from resource competition to public health, a categorically more sensitive terrain for operators, regulators, and residents alike.

Source: Meta AI Data Center Linked To Rare Bacteria In City’s Water System — Forbes report, July 10, 2026, connecting a Meta AI data center to a rare bacteria detection in a municipal water system.

Data Center Knowledge published a report on June 18, 2026 examining why the data center industry continues to rely on evaporative cooling — a heat-rejection method that consumes large volumes of water — even as public and regulatory backlash over water use intensifies. The piece frames the industry’s position as hesitation rather than refusal: operators broadly acknowledge the water problem but have been slow to abandon a technology that remains cheaper and more energy-efficient than the alternatives.

Executive Summary

The report’s core subject is a tension the industry has lived with for years and that the AI build-out has sharpened: evaporative cooling rejects heat by evaporating water, which makes it highly energy-efficient but water-hungry, while the main alternatives — dry (air-cooled) systems and refrigerant-based chillers — save water at the cost of higher electricity consumption, larger equipment footprints, or both. In markets where power is the scarcest commodity a data center can buy, trading water savings for a bigger electrical load is not a simple upgrade; it is a genuine engineering and economic trade-off.

That trade-off is why the headline speaks of hesitation. Operators face mounting pressure from drought-affected communities, local governments, and sustainability commitments to cut water use, and technologies such as closed-loop liquid cooling and hybrid systems are maturing. But retrofitting existing facilities is expensive, and for new builds the calculus depends heavily on local climate, water price, and power availability — variables that differ from one metro to the next. The result is an industry moving unevenly rather than uniformly, which is precisely the dynamic worth understanding for anyone siting capacity or evaluating operators’ sustainability claims.

The Water-for-Energy Trade at the Heart of Cooling

Every data center must move heat from chips to the outside world, and the physics offers no free option. Evaporative systems — cooling towers and their variants — exploit the fact that evaporating water absorbs enormous amounts of heat, which lets a facility reject heat with comparatively little electricity. Dry coolers and air-cooled chillers avoid consuming water but must push heat into the air mechanically, which takes more fan and compressor power, especially on hot days when the temperature difference working in the operator’s favor shrinks. In plain terms: saving water usually means burning more electricity, and in an era when grid connections are the binding constraint on data center growth, extra megawatts spent on cooling are megawatts not available for revenue-generating compute.

This is the economic logic the Data Center Knowledge piece points at with its framing of industry hesitation. An operator that switches a large campus from evaporative to dry cooling is not just paying for new equipment; it is accepting a permanently higher power draw — degrading power usage effectiveness, the industry’s standard efficiency metric — and potentially reducing the sellable IT capacity of a power-constrained site. Where water is cheap and power is scarce, the incumbent technology keeps winning on spreadsheets even as it loses in public opinion.

Why the Backlash Is Getting Harder to Price at Zero

For most of the industry’s history, water was effectively an afterthought in site selection — abundant, inexpensive, and invisible to the public. That has changed. Data center water consumption has become a recurring flashpoint in drought-prone regions, a subject of local permitting fights, and a standard line of questioning for journalists and community groups evaluating new projects. Operators now routinely publish water usage effectiveness figures and, in some cases, commit to becoming “water positive” — replenishing more water than they consume.

The practical consequence is that water carries a growing shadow price beyond the utility bill: longer permitting timelines, conditions attached to approvals, reputational exposure, and in the worst case the loss of a site altogether. The report’s premise — that the industry hesitates rather than transitions — suggests that many operators still judge those risks manageable relative to the hard costs of switching. Whether that judgment holds depends largely on how regulators and communities act next, which varies enormously by jurisdiction.

The Alternatives Are Real, but Not Drop-In

The transition options are well understood in engineering terms. Dry cooling eliminates onsite water evaporation at the cost of energy and space. Hybrid systems run dry most of the year and evaporate water only during peak heat, cutting consumption substantially without the full energy penalty. Direct-to-chip liquid cooling and immersion cooling — increasingly common in AI deployments because high-density chips demand them — move heat in closed loops that consume little or no water onsite, though the heat still has to be rejected somewhere, and that final stage can itself be wet or dry. None of these is a simple swap for an operating facility: cooling infrastructure is capital-intensive, deeply integrated with a building’s design, and typically replaced on decade-plus cycles.

That replacement cycle is the quiet variable in the whole debate. The realistic path for the industry is less about retrofitting the installed base and more about what gets designed into the enormous wave of new construction now underway. If new AI-era facilities standardize on low-water designs where climate and economics allow, the fleet’s water profile shifts over years, not quarters. If they default to evaporative cooling because power constraints dominate, the backlash the report describes is likely to intensify.

Winners, Losers, and the Siting Chessboard

The cooling transition redistributes advantage. Cooler, water-rich regions gain appeal because they make both wet and dry cooling cheaper; hot, arid markets that boomed on cheap land and power face the sharpest version of the water-versus-energy dilemma. Vendors of hybrid and liquid cooling systems benefit from every tightening of water rules. Utilities and municipalities gain leverage, since water service is becoming a negotiated element of large deals rather than a formality. And operators that invested early in low-water designs acquire a permitting and public-relations asset that is difficult for laggards to replicate quickly. Buyers of colocation and cloud capacity should read cooling architecture as a proxy for siting risk: a facility’s water dependence is now part of its long-term cost and continuity profile.

Background

Cooling is one of the two great resource demands of data centers, alongside electricity: every watt a server consumes becomes heat that must be removed. For decades, evaporative cooling towers have been a workhorse of large-scale heat rejection across many industries because evaporating water is thermodynamically cheap. Data centers adopted the approach widely as the industry scaled through the cloud era, and it helped drive the sector’s headline efficiency gains. The AI construction boom that accelerated through the mid-2020s raised the stakes on both sides of the equation — far denser computing produces far more heat, while the communities hosting these facilities have grown increasingly vocal about local water and power impacts. Trade publication Data Center Knowledge, which published the report discussed here, has tracked this cooling debate as one of the defining infrastructure questions of the AI build-out.

Source: Evaporative Cooling in Data Centers: Why the Industry Hesitates to Move On — Data Center Knowledge report, June 18, 2026, on the economics slowing the industry’s shift away from water-intensive cooling.

Ars Technica reported on May 10, 2026 that a data center drew roughly 30 million gallons of water — and that the consumption went undetected for months. The headline alone frames the story: the issue is not only the volume, which is significant but not unheard of for a large facility, but the fact that no one — apparently neither the operator’s oversight processes nor the local water authority — flagged it while it was happening.

Executive Summary

The report describes a data center that “guzzled” about 30 million gallons of water while the draw went unnoticed for months. For scale, 30 million gallons is roughly 45 Olympic-size swimming pools, or about a year’s supply for several hundred typical U.S. households. Data centers commonly use water for evaporative cooling — spraying or trickling water so that its evaporation carries away server heat — which is energy-efficient but consumptive: much of the water leaves as vapor rather than returning to the system.

Why it matters: the industry is under growing scrutiny over water in drought-prone regions, and the standard defense is that usage is metered, permitted, and disclosed to the relevant utility. An episode in which tens of millions of gallons flow without timely detection undercuts that assurance and strengthens the case — made by regulators and communities alike — for real-time submetering, faster reconciliation between withdrawals and billing, and public reporting of facility-level water use.

How Tens of Millions of Gallons Go Missing From View

Water is easy to lose track of in a way electricity is not. Power draw is metered continuously because it is billed continuously, and grid operators watch load in real time. Water billing, by contrast, often runs on monthly or quarterly meter reads, estimated bills, and manual reconciliation — and large industrial users sometimes draw from wells or dedicated lines that sit outside a municipality’s ordinary consumption dashboards. A facility running evaporative cooling around the clock can therefore accumulate an enormous draw between the moments anyone actually looks at the numbers.

The headline’s claim that “nobody noticed for months” is consistent with that structural lag rather than requiring any bad intent. But intent is not the point: a monitoring regime that only surfaces a 30-million-gallon draw after the fact is not a monitoring regime in any meaningful sense. The same volume flowing through a leak, a stuck valve, or an unauthorized connection would have gone equally unnoticed.

The Volume Is Ordinary; the Blindness Is the Story

Thirty million gallons over several months is within the range that large evaporatively cooled data centers can plausibly consume — big hyperscale campuses can use hundreds of thousands of gallons on a hot day. So the fair reading is not that this facility was uniquely thirsty, but that a routine level of industrial water use ran without effective oversight. That distinction matters for how the industry should respond: the fix is measurement and disclosure, not necessarily a smaller pipe.

It also matters for the public debate. Data center water use is frequently discussed in aggregate estimates precisely because facility-level figures are scarce — operators often treat water contracts as confidential, and utilities have historically honored that. Every incident like this one shifts the burden of proof: if the numbers are unremarkable, operators strengthen their own position by publishing them; if the numbers only emerge when something goes wrong, skepticism is the rational default.

What Good Looks Like: Metering, WUE, and Utility Practice

The remedies are unglamorous and well understood. Continuous submetering at the facility intake, with telemetry to both the operator and the water utility, turns months of invisibility into hours. Publishing water usage effectiveness (WUE — liters of water consumed per kilowatt-hour of IT load, the water analogue of the PUE efficiency metric) lets outsiders compare facilities on a common basis. Utilities, for their part, can set anomaly thresholds on large industrial accounts the way credit-card issuers flag unusual spending — an established technique that simply has not been standard practice for water.

There are trade-offs worth being honest about. Cutting water use usually means air-cooled or closed-loop systems, which consume more electricity — shifting the environmental burden from watershed to grid. Communities and operators may reasonably choose evaporative cooling in water-rich regions. But that choice is only defensible when the water is measured, permitted, and disclosed. Transparency is the precondition for the trade-off being legitimate, and this episode is a case study in what happens when it is absent.

Background

Data center water use has become one of the industry’s most contested environmental questions, alongside electricity demand. As AI and cloud growth drive construction of ever-larger campuses, communities from the American Southwest to Europe have pushed back on facilities sited in water-stressed regions, and operators have responded with a mix of efficiency pledges, “water positive” commitments, and — less often — actual facility-level disclosure. Unlike power, which is continuously metered and increasingly reported, water has historically been governed by opaque utility contracts and infrequent meter reads, leaving both regulators and the public reliant on aggregate estimates rather than measured data. Incidents in which large draws surface only after the fact have repeatedly reset that debate.

Source: Data center guzzled 30 million gallons of water, and nobody noticed for months — Ars Technica report, published May 10, 2026, on a data center whose months-long, 30-million-gallon water draw went undetected.