AI

Google Finland data centres: Muhos and Otanmäki sites compared

(today) · 4 min read · By Future Technology · Edited by Nath Connell

Key takeaways

  • Google cleared 816 acres near Muhos without authorisation and roughly 500 acres near Otanmäki, and has been ordered to stop work
  • Locals report wolves entering villages, brown streams, noise and displaced rare birds
  • IT and procurement teams should treat site permitting and regulatory compliance as a real supply risk when choosing where to place AI workloads

Anyone planning AI capacity in the Nordics now has a question that has little to do with GPUs: which of Google's two troubled Finnish sites is the bigger risk to a timeline, and what does a regulator's stop-work order mean for customers relying on that capacity? The two projects, near Muhos and Otanmäki, are both under orders to cease development, but they are not identical problems.

The contenders

Google's Finland country manager has apologised for unauthorised forest clearings near Muhos, where 816 acres of forest have become an expanse of mud. Separately, the company has been told to stop work at a site 55 miles southeast of the village of Otanmäki, where it has cleared roughly 500 acres of forest. The Finnish Licensing and Supervision Authority (LVV) issued the order covering both locations.

The American search and AI giant is racing to build new AI data centres in Finland, and critics say it has ridden roughshod over regulations in the hurry. A representative of the Finnish Association for Nature Conservation (SLL) told The Guardian that Google's flouting of environmental policy has been unprecedented and clear. A Google spokesperson said: "We will fully comply with LVV's requests in this matter."

Local reports add a human dimension. Anni Ranta, 53, whose family has lived in Otanmäki for generations, said: "We had wolves coming into the village because all the wild animals moved out of the forest." Residents also cite construction and factory noise, streams turning brown and rare birds being pushed out.

Head-to-head comparison

FeatureMuhosOtanmäki
Forest cleared816 acres, now mudRoughly 500 acres
Regulatory statusLVV order to stop developmentLVV order to stop development
Google's responseCountry manager apologised for unauthorised clearingsSpokesperson says Google will fully comply with LVV
Local impact reported816 acres of forest turned to mudWolves entering the village, brown streams, noise, displaced rare birds
Community concernEnvironmental damage and anger over regulationWildlife safety, plus one resident's fear of Russian aggression

Where Muhos is the bigger problem

Scale is the headline. At 816 acres, Muhos represents the larger area of lost forest, and it is the site where Google has publicly admitted fault through its Finland country manager.

For enterprise buyers, that matters. Any capacity plans tied to Muhos should be treated as the most exposed to delay.

Where Otanmäki is the bigger problem

The reporting describes wildlife pressure reaching inhabited places, with wolves moving into the village, and a litany of daily nuisances: noise, discoloured streams and the displacement of rare birds. These are the kinds of grievances that sustain local opposition and feed into planning disputes long after a stop-work order is lifted.

There is also a security argument, raised by Ranta, who fears that US-owned data centres will make Finland a juicier target for Russian aggression. That is one resident's concern rather than an established assessment, but it shows that opposition is not limited to environmentalists. Community consent, in other words, is part of the risk.

The verdict

Neither is a safe bet for near-term capacity.

The practical recommendation for IT and procurement teams, in the US and UK alike, is to avoid anchoring AI deployment schedules to any single Finnish site until the LVV orders are resolved. US firms consuming Google's cloud and AI services should ask their account teams whether any committed capacity depends on these builds, and whether alternative regions are contractually available. UK organisations, which would look to the ICO for data protection questions and not for planning matters, should likewise check where their workloads are hosted and whether their business continuity plans survive a delay in a Nordic region.

Google is presumably hoping the touted business benefits of the data centres will sway the government and regulators. Until that is decided, the safest plan is diversification, and the case for scrutinising a provider's permitting record alongside its price and performance has rarely been clearer. For readers following the broader hardware race that drives this demand, our look at Nvidia's push into PC chips shows how much compute appetite sits behind builds like these, and the geopolitics of AI chips explains why location and politics matter in chip deals.

Key takeaways

  • Google cleared 816 acres near Muhos without authorisation and roughly 500 acres near Otanmäki, and LVV has ordered work to stop at both.
  • Muhos is larger and involves an admitted breach; Otanmäki involves wildlife and community harm.
  • Google says it will fully comply, but timelines for the Finnish AI capacity are now uncertain.
  • IT teams should check where their cloud and AI workloads depend on these builds and keep alternatives ready.

Watch for LVV's next steps and whether Google secures retroactive approval. That outcome will signal how strictly Finland, and by extension other jurisdictions, will police the rush to build AI infrastructure.

More from Future Technology