Your Water, Your Power, Your Money — the series. Pushing back does not make the cost disappear. It only changes the form in which the cost arrives. Tucson closed the door on Project Blue and still faces years of water-rate increases. Lake Tahoe did not build the data centers driving northern Nevada load growth and still faces the power-market consequences. Fayetteville banned new data centers after discovering an unauthorized 29-million-gallon water draw, while the existing campus continues to build. The Dalles had to fight for disclosure after Google's water use became a trade-secret battle. This is the Asymmetric Cost of Pushing Back.
In 60 Seconds
The clearest mistake an audit like this can make is to suggest that municipal denial of a data center solves the cost problem for the host community. The verified record shows the opposite. The municipalities that have successfully blocked a project still face cost increases — tracing back to the same drivers (drought, transmission scarcity, market-rate energy procurement, the broader compute build-out) even when the local project never moved a shovel.
Tucson, Arizona — After Project Blue
The Tucson City Council unanimously rejected Project Blue's annexation on August 6, 2025; Tucson Water revoked the construction meter on April 24, 2026. The project is functionally foreclosed in its original form. The verified water-rate record after the denial: a March 2026 notice of intent for four consecutive annual 3.5 percent water-rate increases through FY 2029-2030, following a four-year cycle of 5.5 percent annual increases already in place — a cumulative residential water-bill increase exceeding 35 percent over the 2023–2030 window, driven principally by drought-period Colorado River cuts and aging infrastructure. The household that organized and helped close the door on Project Blue is on the rate hook for the drought regime that Project Blue would have intensified. The reward for organizing is approximately the same rate increase the household would have faced anyway.
Lake Tahoe — The Cost of Not Pushing Back Early Enough
NV Energy, which has supplied about 75 percent of the electricity Liberty Utilities delivers to the California-side Tahoe community for decades, will end full-requirements supply by December 31, 2027. The reason in Liberty's own filing: data-center demand at the Tahoe-Reno Industrial Center and northern Nevada transmission constraints. The verified rate record: a 19 percent increase requested in 2025 for wildfire mitigation, then a further 22.6 percent increase proposed for summer 2026. 49,000 ratepayers will now compete in the Western wholesale market against PG&E, Southern California Edison, mining companies, and the data-center clusters that triggered the exit.
Fayetteville, Georgia — After the Drainage
Fayetteville banned new data-center development in all zoning districts in early 2026, in direct response to residents' discovery that QTS had drawn 29 million gallons of water through two unmetered industrial connections during a severe drought. The campus was not foreclosed: 615 acres, currently 13 buildings totaling about 6.2 million square feet, planned to grow to 16. The ban applies to new data centers; the campus that drained the water continues to build. The county imposed no fine; the retroactive bill of $147,474 was paid in full. The utility director's recorded explanation: they are our largest customer and we have to be partners — it is called customer service.
The Dalles, Oregon — The Disclosure Fight
Google's data centers in The Dalles, a city of 16,000, consumed an estimated 355 million gallons of water in 2021 — roughly a quarter of the city's total usage. When the local newspaper sought facility-level disclosure through Oregon's public records law, Google funded the city's litigation against the newspaper, arguing the data was a trade secret. The newspaper ultimately prevailed. The host city was funded by the customer to defend the customer's nondisclosure against the host city's own newspaper.
The Asymmetric Cost of Pushing Back
The institution facing pushback faces, at most, a delayed or relocated project. The household facing pushback faces, at minimum, the same rate increase it would have faced anyway, often larger — and the cost of the pushback itself (organizing, meetings, comments, counsel) is absorbed by the household with no recovery mechanism. The institution's cost is internalized into the price of the next project at the next site. The household's cost is internalized into the household. This is not an argument against pushing back; it is the unsentimental disclosure of what pushback actually costs the person who does it.