Google Faces Local Protests Over 1 GW Data Center in Visakhapatnam

Construction of Google's gigawatt campus in Visakhapatnam, part of an investment plan of about $15 billion for 2026–2030, has run into resistance from local residents. They worry about the environment and about living next to a huge data center. Google is responding publicly and has built its case around three topics: electricity, water and jobs.

What we know about the project

Google announced the AI hub in Visakhapatnam in October 2025. The city sits on the Bay of Bengal coast in the state of Andhra Pradesh and is considered one of the key port hubs of eastern India. The project's named partners include AdaniConneX and Airtel, and the plans also include subsea cable infrastructure. That matters: the campus is conceived not as an ordinary cloud site but as a hub for training and inference of models, with links to international connectivity routes.

The original TechXplore report does not detail the protests: it gives no figures on how many people object, no legal steps and no specific numbers on resources. So below we rely on the project's public parameters and general patterns in the industry.

• Investment: about $15 billion, 2026–2030.
• Scale: stated gigawatt class.
• Site: Visakhapatnam, Andhra Pradesh.
• Partners: AdaniConneX, Airtel.
• Points of dispute: energy, water, jobs, environment.

Three complaints and the math behind them

Electricity. A 1 GW load running continuously comes to about 8.76 TWh per year. For a region with uneven demand and peak loads, that is a serious figure. Residents care less about an abstract kilowatt than about two practical questions: who pays for grid reinforcement, and whether tariffs will rise. The answer depends on how the power purchase contracts are structured, including those for renewable energy, and on how much of them is disclosed.

Water. The cooling design decides almost everything. Evaporative systems consume a lot of fresh water, while closed loops and air cooling use less water but more electricity. The coastal location opens up options such as desalination or seawater, but they come at a cost: high energy use and brine discharge. It is not yet publicly clear which design will be chosen or what limits on water withdrawal will be set.

Jobs. This is the typical gap in expectations. Building a campus of this size employs thousands of people, but the operational phase usually has few permanent positions: tens or hundreds per site, and some of them require narrow specialist skills. If locals are promised mass employment, the key question is at what stage and in what roles.

Why this matters beyond India

The same scenario has already played out in Northern Virginia, Arizona, Ireland and the Netherlands: growing AI load runs into limits on grids, water and land, and then into local politics. India is betting on digital infrastructure and data localization, so sites like this are strategic for it. But strategy does not cancel the conversation with the people who live next door.

For Google, this is a question of schedule and reputation. A delay in permits or in the courts pushes back the commissioning of capacity, and AI workloads do not like to wait.

What to watch next

• Data disclosure. Whether public figures on water and energy consumption appear for both the construction and operation phases.
• Energy sources. What share is covered by new generating capacity rather than by redistributing existing supply.
• Community agreements. Whether the companies put commitments on hiring, compensation and environmental monitoring into formal documents rather than press releases.
• Timeline. The effect of the protests on the schedule for the first phase.

Companies planning to place workloads in Google Cloud's Indian regions would be wise to build in schedule buffers and keep a fallback plan in case capacity comes online late. Data center investors should look at a project's water and energy design as closely as at its stated gigawatts.