When the Servers Move In

A Field Guide for Residents and Advocates Confronting Hyperscale Data Center Development

Why this deserves your attention

Hyperscale data centers, the term of art for the massive, multi-hundred-megawatt server complexes built by companies like Amazon, Google, Meta, Microsoft, and xAI, are now being deployed faster than the regulatory frameworks designed to oversee industrial development can adapt. The combined infrastructure spending of just four companies, Amazon, Google, Meta, and Microsoft, was projected to exceed $320 billion in 2025, more than double their spending two years prior.¹

That speed advantage matters. When developers move faster than the rule-writers, the rules get bent. Sometimes that bending takes the form of a creative reading of a permitting statute. Sometimes it takes the form of a contractor doing something the host community explicitly told them not to do. Sometimes it takes the form of a public records lawsuit aimed at preventing taxpayers from learning how much of their drinking water is being used to cool somebody else’s servers.

What follows is a survey of documented cases, drawn from court filings, regulatory rulings, and investigative reporting, that establish the pattern. Residents, local officials, and advocates evaluating a proposal in their own community should know what’s happened elsewhere, because the playbooks travel.

---

Case 1: xAI Colossus (Memphis, TN, and Southaven, MS)

The most aggressive recent case involves Elon Musk’s xAI, which operates the Colossus supercomputer cluster that powers the Grok chatbot.

To meet computational demand, xAI installed gas-fired turbines on-site and near its data center sites rather than waiting for utility interconnection or building a permitted power plant. At the Colossus 1 site in South Memphis, aerial photography commissioned by the Southern Environmental Law Center documented 35 methane gas turbines, more than double the 15 the facility was permitted to operate.² At the Colossus 2 site, where 27 turbines were installed across the state line in Southaven, Mississippi, the combined potential output reached 495 megawatts, the equivalent of a conventional power plant.³

The legal theory underpinning this approach exploited a local rule allowing generators to operate for up to 364 days without a permit, paired with an aggressive interpretation of federal Clean Air Act exemptions.⁴ In January 2026, the U.S. Environmental Protection Agency issued updated guidance clarifying that large methane gas turbines like xAI’s require Clean Air Act construction and air permits, explicitly closing the loophole xAI had been exploiting.⁴

The pollution figures are not small. According to court filings, the 33 unpermitted turbines at the Southaven plant have the potential to emit 2,508 tons of smog-forming nitrogen oxides, 236 tons of fine particulate matter, and significant quantities of formaldehyde and carbon monoxide each year, likely making the facility the largest industrial source of NOx in greater Memphis, a region already failing federal smog standards.⁵ The Southaven turbines sit roughly half a mile from homes and a mile from an elementary school.⁶

Earthjustice and SELC, representing the NAACP, filed Clean Air Act enforcement litigation in federal court in early 2026 and subsequently requested a preliminary injunction after xAI added six additional large turbines despite the pending case. ⁵⁶

The takeaway for residents: When a developer claims a piece of equipment is “temporary,” “emergency,” or “interim” to justify deferring full permitting, that claim deserves immediate scrutiny, including a clear written timeline, written permit applications already in process, and an enforcement mechanism if the timeline slips.

---

Case 2: Google in The Dalles, Oregon

This is the most documented case of a hyperscale operator using public records suppression to keep environmental impact data away from the community.

When The Oregonian/OregonLive requested records on Google’s local water use, the city of The Dalles refused, asserting the data was a “trade secret” under Oregon disclosure law. After the Wasco County district attorney sided with the newspaper and ordered disclosure, the city took the unusual step of suing the newspaper to block release.⁷ Google paid the city’s legal bills under a confidentiality pact in which the company agreed to reimburse all legal expenses incurred protecting its asserted trade secrets, an arrangement experts described as unprecedented, with invoices reportedly exceeding $215,000.⁸

The case settled in late 2022 after a thirteen-month fight. After the data's release, the newspaper reported that Google’s water use had nearly tripled over five years, with its data centers consuming more than a quarter of the city's total water.⁷ As of 2026, Google reportedly accounts for roughly 40 percent of total water usage in The Dalles, and federal legislation is pending that would cede federal public land to expand the city’s reservoir, which a coalition of environmental groups argues is functionally a water grab to feed Google’s expanding data center footprint, with possible impacts on Indigenous treaty rights and endangered salmon.⁹

The takeaway for residents: If a developer is unwilling to disclose its water consumption, electricity consumption, or chemical inventory, or if local officials sign nondisclosure agreements that prevent them from sharing such information with the public, assume the numbers are larger than what would be politically tolerable if disclosed.

---

Case 3: Meta in Newton County, Georgia

In Mansfield, Georgia, Meta built a $750 million data center adjacent to a rural residential area. After construction began in 2018, multiple nearby households reported well water failures and severe sediment buildup that damaged appliances. A home located roughly 1,000 feet from the site reported spending around $5,000 on water-related repairs and replacements. ^{10 11}

Meta commissioned an independent groundwater study that concluded there was no connection between the data center and the residents’ problems.¹⁰ But the structural problem the case illustrates is not whether Meta’s specific facility caused these specific wells to fail. It is that the regulatory regime did not require pre-construction hydrologic baseline studies sufficient to either prevent the impact or definitively attribute it after the fact. By the time damage is documented, the burden of proof has shifted to people without the resources to commission their own hydrogeological investigations.

The takeaway for residents: Demand a pre-construction baseline hydrologic study, a monitoring well program, and a written remedy mechanism, including replacement-well construction at the developer's cost, before land disturbance begins. Demand it in the development agreement, not after.

---

Case 4: AWS data centers in Prince William County, Virginia

The “Great Oak” cluster of Amazon data centers outside Manassas has produced documented resident noise complaints for three-plus years. The continuous low-frequency roar emitted by the facilities has been the subject of an ongoing, repeatedly delayed effort by Prince William County to revise its noise ordinance. ¹³

Two enforcement problems compound the situation. First, Virginia law allows only criminal penalties, not civil fines, for industrial operations in industrially-zoned areas, complicating practical enforcement.¹³ Second, the state caps civil penalties for noise ordinance violations at $500 after the first offense, an amount stakeholders argue is wholly insufficient to alter the behavior of multibillion-dollar operators.¹⁴ The technical fight over the ordinance has itself become contested: in late 2025, the county’s deputy executive added six decibels to each octave band relative to the consultant’s proposed limits, an adjustment a resident representative described as a quadrupling of noise energy and a 50 percent increase in perceived noise.¹⁴

In a separate but related development, in April 2026, the Virginia Court of Appeals invalidated three major Prince William rezoning ordinances covering nearly 23 million square feet of proposed data center development, ruling the Board of Supervisors had failed to follow state and local advertising requirements for the public hearing. The court rendered the ordinances “void ab initio” and affirmed that neighboring landowners had standing because they faced “particularized harm,” including increased noise, light pollution, and potential property-value decreases. ¹⁵

The takeaway for residents: Before approval, demand pre-construction and post-construction noise studies using both A-weighted and C-weighted (or octave-band) measurement standards; the A-weighted decibel scale systematically under-represents the low-frequency rumble data centers actually produce. Demand that civil penalties be structured in the development agreement to be meaningful relative to the operator’s revenue.

---

Case 5: CyrusOne in Chandler, Arizona

Chandler, Arizona, offers the longest-running cautionary example. CyrusOne’s data center campus has been the subject of resident noise complaints since at least 2018. The city manager sent successive letters to the company’s CEO stating it was “likely in violation of local sound ordinances” and demanding remediation; the company promised sound attenuation packages by October 2018, but residents continued to report no measurable improvement.¹⁶ By 2021, the city had reversed course and was actively considering a code amendment prohibiting any new data centers anywhere in Chandler, and the city’s vice mayor stated bluntly that data centers no longer made sense for Chandler. ¹⁷

Heatmap reporting indicates noise is the single most common issue in data center conflicts nationally; at least a third of all such conflicts involve noise complaints, and noise is the number one reason for opposition in cases where projects were ultimately canceled. Local officials are increasingly hearing complaints about infrasound, a sub-audible, low-frequency rumble produced by HVAC systems, cooling fans, and rotational on-site generation such as gas turbines, that conventional A-weighted ordinances are not designed to measure.¹⁸

The takeaway for residents: Once a data center is built, retroactive noise mitigation has a poor track record. The leverage point is before the certificate of occupancy, not after.

---

Case 6: Project Blue in Tucson, Arizona

The Tucson case is fresh and instructive because it shows the playbook continuing after a community successfully says no.

In August 2025, the Tucson City Council voted unanimously to reject annexation of a proposed hyperscale data center site near the Pima County Fairgrounds, a project nicknamed “Project Blue,” initially linked to Amazon Web Services and developed by Beale Infrastructure. The vote followed a public outcry once residents learned the initial cooling plan would have consumed reclaimed water equivalent to the annual supply for more than 3,000 homes.¹⁹ Council members explicitly cited the use of nondisclosure agreements as a sticking point: residents and even some elected officials did not know who the ultimate customer would be or what resources the project would consume.²⁰

Beale subsequently announced it would proceed anyway, using an air-cooled design, purchased the land from Pima County through a subsidiary company, and began site preparation.¹⁹ In early May 2026, the city discovered that Beale’s contractor, Ames Construction, had obtained a temporary construction water meter inside Tucson Water’s service area and was trucking the water out of that area to the Project Blue site for dust control. The city manager revoked the meter, demanded restitution of two acre-feet of water credits, and issued a letter stating: “To be absolutely clear — the city of Tucson does not support the development of Project Blue. The city of Tucson will not provide any city resource, including our water supply, to be used for Project Blue.”²¹²²

The episode triggered a procedural reform: Tucson now requires construction water meter applications to identify where the water will actually be used, not merely where it will be drawn.²³ That reform exists because a contractor exploited the gap.

The takeaway for residents: A community vote against a project is not the end of the story. Monitor land sales, watch for subsidiary-company assignments, and demand that conditions on resource use survive the project’s reorganization into a different ownership or operational structure.

---

Case 7: AWS and Talen Energy at Susquehanna

The final case is structurally different from the others. There is no environmental harm in the traditional sense. There is, however, a sophisticated effort to bypass federal rate regulation, which would shift infrastructure costs from a single hyperscale customer onto regional ratepayers.

Amazon Web Services purchased a 960-megawatt data center campus co-located with Talen Energy’s Susquehanna nuclear plant in Pennsylvania for $650 million. The arrangement would have AWS draw power “behind the meter”, directly from the generator, bypassing the grid and the associated transmission charges that other large customers pay.²⁴ On a 2–1 vote in November 2024, the Federal Energy Regulatory Commission rejected the amended interconnection service agreement that would have increased the behind-the-meter connection from 300 MW to 480 MW.²⁴ In June 2025, Talen and AWS restructured the deal as a “front-of-the-meter” power purchase agreement (rising to as much as 1,920 MW by 2032) that doesn’t require FERC approval, a workaround that The Register described as routing the load through the grid in name only. ²⁵

The Susquehanna case has had national policy consequences. In Ohio, the Public Utilities Commission cited the structure as justification for approving a tariff requiring large new data center customers to pay for a minimum of 85 percent of subscribed electricity usage, regardless of actual consumption, for up to 12 years.²⁶ After Ohio adopted these provisions, data center service requests in the state fell from 30 gigawatts to 13 gigawatts, strong empirical evidence that more than half of the stated demand in low-tariff jurisdictions is speculative, with the same projects being shopped across multiple jurisdictions.²⁷ Virginia approved a similar “GS-5” rate class in November 2025 for customers using over 25 MW.²⁸

The takeaway for residents and local officials: Demand for power at a proposed site is not the same as committed, contractually-binding load. Treat utility load projections for data center service requests with the same skepticism you would apply to any other speculative real estate proposal.

---

Cross-cutting patterns

Six patterns emerge consistently across these cases.

The “temporary equipment” exploit. xAI is the most aggressive example, but designations like “temporary,” “emergency,” “construction-phase,” or “pilot” recur across the industry as devices for delaying or evading full permitting. EPA’s January 2026 guidance closing the gas turbine loophole was responsive to xAI specifically but applies broadly.

Public records suppression. The Dalles–Google episode is the most extreme case, but nondisclosure agreements covering project identity, water use, electricity contracts, and tax abatements are routine across jurisdictions. Of the 36 states offering sales-and-use tax exemptions for data centers, only 11 disclose which companies receive them. Texas spent roughly $1 billion subsidizing data centers in FY 2025 and reports company names but no project-level subsidy amounts, no job creation data, and not even project locations. Virginia abates nearly $1 billion in state and local sales and use tax revenue annually, but does not disclose which companies benefit.²⁹

Speculative load multipliers. The Ohio data, requests dropping from 30 GW to 13 GW after a tariff change, establishes that a large fraction of stated demand in low-friction jurisdictions is speculative. Load projections produced by utilities or developers to justify infrastructure investments should be treated with corresponding skepticism, because the same project is often being submitted in multiple jurisdictions simultaneously.

Weak noise enforcement. Most jurisdictions have weak civil penalty structures; Virginia’s $500 cap is typical, and most use A-weighted decibel standards that systematically under-measure the low-frequency noise data centers actually produce. The Prince William fight over octave-band levels is the clearest example of this becoming politically contested.

Cost-shifting onto ratepayers. The AEP Ohio and Dominion Virginia rate cases both responded to documented evidence that hyperscale load is shifting transmission and generation infrastructure costs onto residential and small-business customers. Even with new tariff protections, analyses suggest a substantial fraction of grid upgrade costs may still fall on ordinary ratepayers.²⁸

Project survival through reorganization. The Project Blue case demonstrates that a community vote against a project does not necessarily end it. Subsidiary-company purchases, design pivots (from water-cooled to air-cooled), and contractor-level rule violations are all viable paths to keep a project moving after a political setback.

---

What residents and advocates should watch for

If a hyperscale data center is being proposed in your community, the following questions are worth asking, and the answers are worth getting in writing, before approval, in the development agreement itself:

1. Power. Where exactly does the electricity come from? Is the operator planning any onsite generation, including “temporary” or “backup” generation? If yes, on what permitting basis? Who pays for the transmission upgrades necessary to serve the load, and on what enforceable schedule?

2. Water. What is the projected daily and annual water consumption, both for cooling and for construction? Where does it come from, and what happens to it after use? Is the operator willing to commit to a pre-construction baseline hydrologic study and a monitoring well program with developer-funded remedy obligations?

3. Noise. Will pre-construction and post-construction acoustic studies be required, using both A-weighted and low-frequency-sensitive measurement standards? What are the civil penalties for violations, and are they meaningfully proportional to the operator’s revenue?

4. Air. What emissions does the operator anticipate from cooling systems, generators, or any onsite generation? Is the local airshed already in nonattainment for any criteria pollutant?

5. Transparency. Has the developer required public officials to sign nondisclosure agreements? Is the ultimate end-user customer publicly identified? Are tax abatements, electricity rate discounts, and any other public subsidies fully disclosed?

6. Continuity. Do the conditions on resource use, monitoring, and enforcement survive a change of ownership or operational reorganization? Do they survive an “as-of-right” design change (e.g., water-cooled to air-cooled) that may dramatically increase electricity consumption or air emissions?

None of these questions is unreasonable; they are the same questions any responsible community would ask of any large industrial development. The reason they need to be asked explicitly, in writing, and to have their answers verified before approval is that the body of evidence now indicates that hyperscale data center operators and the contractors and consultants who work for them frequently do not volunteer this information.

The pattern is not universal. There are responsible operators and good-faith projects. But the pattern is consistent enough that residents and advocates should treat the burden of proof as resting on the developer, not on the community.

---

Footnotes

1. American Economic Liberties Project, “New Brief Offers Roadmap for States to Fight Back Against Big Tech’s Secret Data Center Subsidy Deals,” November 2025. https://www.economicliberties.us/press-release/new-brief-offers-roadmap-for-states-to-fight-back-against-big-techs-secret-data-center-subsidy-deals/

2. Dan Swinhoe, “xAI doubles number of onsite gas turbines at Memphis data center in violation of permit limits,” Data Center Dynamics, March 31, 2026. https://www.datacenterdynamics.com/en/news/xai-doubles-number-of-onsite-gas-turbines-at-memphis-data-center-in-violation-of-permit-limits/

3. Southern Environmental Law Center, “xAI built an illegal power plant to power its data center,” updated April 14, 2026. https://www.selc.org/news/xai-built-an-illegal-power-plant-to-power-its-data-center/

4. TechSpot, “EPA shuts down xAI’s off-grid turbine loophole at Colossus data center in Memphis,” January 19, 2026. https://www.techspot.com/news/110971-epa-shuts-down-xai-off-grid-turbine-loophole.html

5. Earthjustice, “NAACP Asks Court for Emergency Action to Stop Illegal Air Pollution from xAI’s Data Center Power Plant,” May 2026. https://earthjustice.org/press/2026/naacp-asks-court-for-emergency-action-to-stop-illegal-air-pollution-from-xais-data-center-power-plant

6. Earthjustice, “Illegal Pollution from Data Center Power Plants Shouldn’t Harm Our Communities. We’re Suing xAI.” https://earthjustice.org/case/xai-illegal-gas-power-plant-data-center-colossus

7. Reporters Committee for Freedom of the Press, “Oregon’s city of The Dalles agrees to reveal Google’s local water usage.” https://www.rcfp.org/dalles-google-oregonian-settlement/

8. Sarah Frier, “An Oregon city hoped Google would save its economy. Years later, some residents call the tech giant ‘Voldemort,’” Fortune, June 2023. https://fortune.com/longform/google-data-center-the-dalles-oregon-water-dispute/

9. Sierra Magazine, “Data Centers Are Hogging This Town’s Water.” https://www.sierraclub.org/sierra/data-centers-are-hogging-town-s-water

10. AInvest, “Meta’s Data Center Construction Causes Water Crisis in Newton County, Georgia,” July 14, 2025. https://www.ainvest.com/news/meta-data-center-construction-water-crisis-newton-county-georgia-2507/

11. San Francisco Examiner, “Water Troubles in Newton County Due to Data Center Construction.” https://www.sfexaminer.com/their-water-taps-ran-dry-when-meta-built-next-door/article_d37b83df-16f4-5fcb-9b63-958a4d5c3a05.html

12. PPC.land, “Meta data center impacts local water supply in Newton County,” July 2025. https://ppc.land/meta-data-center-impacts-local-water-supply-in-newton-county/

13. Prince William Times, “Long-awaited effort to limit data center noise hits a snag,” October 2025. https://www.princewilliamtimes.com/news/long-awaited-effort-to-limit-data-center-noise-hits-a-snag/article_34e928bd-5fcb-48fc-8cf5-f6b232e59daa.html

14. Inside NoVA, “’A straight middle finger’: Prince William data center advisory group sounds off over noise ordinance,” September 23, 2025. https://www.insidenova.com/headlines/a-straight-middle-finger-prince-william-data-center-advisory-group-sounds-off-over-noise-ordinance/article_ffadc0a1-9183-4391-8fe6-c7e5aab018cd.html

15. Patch, “VA Appeals Court Tosses Prince William County Data Center Rezonings,” April 1, 2026. https://patch.com/virginia/woodbridge-va/va-appeals-court-tosses-prince-william-county-data-center-rezonings

16. Arizona Mirror, “Bill aims to incentivize data centers as residents plug their ears,” April 1, 2019. https://azmirror.com/2019/04/01/bill-aims-to-incentivize-data-centers-as-residents-plug-their-ears/

17. ABC15, “Chandler to consider banning data centers amid noise complaints,” November 2021. https://www.abc15.com/news/region-southeast-valley/chandler/chandler-to-consider-banning-data-centers

18. Heatmap News, “I Spent the Day At a Noisy Data Center. Here’s What I Learned.” https://heatmap.news/plus/the-fight/spotlight/data-center-noise

19. Tucson Sentinel, “Project Blue developers close on purchase of Pima County land for Tucson data center,” December 24, 2025. https://www.tucsonsentinel.com/local/report/122425_project_blue_close/

20. Boondoggle Newsletter, “The Secret Cost of Data Centers.” https://boondoggle.substack.com/p/the-secret-cost-of-data-centers

21. Tucson Sentinel, “City says Project Blue must stop using Tucson Water for data center construction,” May 2026. https://www.tucsonsentinel.com/local/report/050526_project_blue_water/city-says-project-blue-must-stop-using-tucson-water-data-center-construction/

22. AZPM News, “Project Blue developers improperly used Tucson water, city has shut it off,” May 6, 2026. https://news.azpm.org/p/azpmnews/2026/5/6/229644-project-blue-developers-improperly-used-tucson-water-city-has-shut-it-off/

23. KGUN9, “Tucson changes water access rules after Project Blue water use,” May 2026. https://www.kgun9.com/news/community-inspired-journalism/southeast-side-news/tucson-changes-water-access-rules-after-project-blue-water-use

24. Utility Dive, “FERC rejects interconnection pact for Talen-Amazon data center deal at nuclear plant,” November 4, 2024. https://www.utilitydive.com/news/ferc-interconnection-isa-talen-amazon-data-center-susquehanna-exelon/731841/

25. The Register, “Amazon, Talen Energy sidestep regulators with new power deal,” June 12, 2025. https://www.theregister.com/2025/06/12/amazon_talen_nuclear_deal/

26. POWER Magazine, “Regulator Approves AEP Ohio’s Landmark Data Center Tariff,” July 10, 2025. https://www.powermag.com/regulator-approves-aep-ohios-landmark-data-center-tariff/

27. Inside Climate News, “Virginia Regulators Approve New Dominion Rates, Assign More Costs to Data Centers,” January 2026. https://insideclimatenews.org/news/07012026/virginia-regulators-approve-new-dominion-rates/

28. American Action Forum, “Virginia’s New Data Center Electricity Rate Class,” January 2026. https://www.americanactionforum.org/insight/virginias-new-data-center-electricity-rate-class/

29. Good Jobs First, “Cloudy Data, Costly Deals: How Poorly States Disclose Data Center Subsidies,” November 2025. https://goodjobsfirst.org/cloudy-data-costly-deals-how-poorly-states-disclose-data-center-subsidies/