42/100

Emerging evidence

ProblemPublished recordClimateProblem Space

AI datacentres plan on-site power stations on huge scale despite climate risks, research reveals

Truvace record
TRV-2026-2472raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
81b7a36ae5c2…check it

Developers of AI datacentres plan to build on-site climate-destroying gas power stations on a huge scale to meet their energy demands, research reveals. Datacentres planned across the US, the UK and mainland Europe have proposals to build fossil fuel plants on-site to create 181GW of gas-fired capacity because of delays to connect to national grids, according to the findings. This is almost four times the total peak electricity demand of Great Britain. The research by BloombergNEF says this “speed to power” will…

The problem

BloombergNEF research found AI datacentres in the US, UK and mainland Europe plan 181GW of on-site gas-fired capacity, which would emit about 345m tonnes of CO2e a year in the US if built.

What this doesn’t fix

The 345m tonne emissions figure applies only if the planned rollout happens, and developers say the gas plants will be temporary while they await grid connections.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-11

Cite this record

v1

Truvace Impact Record TRV-2026-2472, v1: “AI datacentres plan on-site power stations on huge scale despite climate risks, research reveals.” Truvace, 2026-11-11. /record/TRV-2026-2472 (accessed on the day you copy it). sha256 81b7a36ae5c2f181…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv181b7a36ae5c2…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2472 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.