explainx.ai350K+ learn from us
TrendingAI News TodayExplainx for Business
Pricing
explainx.ai

Upskill in AI — 16 free pathways, live workshops & bootcamps, and 50+ courses from practitioners. Plus the skills, tools, and MCP servers to practice on.

follow us

follow on google

Add explainx.ai as a preferred source

corporate training

support@explainx.ai

get started

Find your pathTake Free Evaluation

community

Join the community

learn

mind: share how you thinkpathways — start freeworkshopsbootcampscoursescompare Explainxcertificationsmock testsexplainx universitycorporate traininglearn skills & mcp

discover

skillsmcp serversexplainx mcpestacktoolsmdx readeragentsllmsdesignsdictionarypeopleagi trackerfelony benchranks

company

aboutvisionmissionteaminstructorsteach on explainxpartnershipscommunityhackathonscareers

content

daily AI newsstate of AI — live resultsblogreleasespromptsgeneratorsresource libraryfor LLMsexplainx.ai kids

solutions

all solutionsdeveloper upskillingmarketing upskillingproduct manager upskillingleadership upskilling

newsletter · weekly

Get AI news, tools, and insights in your inbox.

supportcontactprivacytermsdata rightshow we create contentsubmission guidelines

© 2026 AISOLO Technologies Pvt Ltd

explainx.ai

On this page

  • TL;DR from reported findings
  • Why hyperscale emissions differ from laptop inference
  • Policy and siting implications
  • What the study does not resolve
  • Connecting study numbers to your cloud bill
  • Checklist for climate-conscious ML teams
  • How this compares to corporate net-zero pledges
  • How to read the primary source
  • Interconnection queues and the fossil reality
  • Methodology questions serious readers should ask
  • Regional siting examples already in our corpus
  • What hyperscalers may do next
  • Media and policy reactions to watch
  • Related reading
  • Inference versus training: different carbon stories
  • Denmark comparison: how to use it responsibly
  • Water, noise, and secondary siting fights
  • Community and labor angles
← Back to blog

explainx / blog

US Hyperscale Data Centers: Harvard Study Flags Fossil Power Share

Data Centers, Climate, AI Infrastructure, Energy, Research

Part of AI Chips and Infrastructure

A Harvard study in Nature Sustainability finds over half of electricity at 403 US hyperscale data centers came from gas and coal, with 25.7M t CO2 in one year.

Nov 18, 2026·8 min read·Yash Thakker
add explainx.ai
go deep
US Hyperscale Data Centers: Harvard Study Flags Fossil Power Share

A Harvard team publishing in Nature Sustainability estimates that 403 US hyperscale data centers emitted about 25.7 million metric tons of CO2 between May 2024 and April 2025, with more than half of their electricity from gas and coal, according to coverage of the peer-reviewed paper on November 18, 2026. Reporters compare that one-year total to more than Denmark’s annual emissions and warn that roughly 2,000 additional hyperscale sites in planning could set back climate targets without siting and grid reforms.

This is not a vendor press release. It is infrastructure accountability for teams treating GPU clusters as morally neutral once a renewable PPA slide ships. explainx.ai has tracked AI climate paradox themes, Google Wyoming gas fuel cells, and PJM fast energization fights where grid physics meets AI demand.

TL;DR from reported findings

The study, "Assessing the Carbon Emissions and Energy Consumption of US Hyperscale Data Centers", used satellite imagery to identify the 403 facilities, per the EurekAlert news release.

table · 2 cols
MetricReported value (May 2024–Apr 2025 window)
Facilities studied403 US hyperscale data centers
Estimated CO2~25.7 million metric tons
Fossil share of power~54% from gas and coal (per coverage of the paper)
Planned additional sites~2,000 (authors’ warning)
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

Hyperscale data center electricity drawn from regional power grid mixHyperscale data center electricity drawn from regional power grid mix

Why hyperscale emissions differ from laptop inference

Hyperscale sites run 24/7 at megawatt scales. A local RTX Spark box in our November 18 RTX desktop post shifts some workloads off cloud, but training frontiers still concentrate in campus-scale halls.

Harvard’s contribution, per coverage, is granular attribution: not only sector-wide grid averages, but large facilities whose contract structures may decouple legal renewable claims from physical power flows. That debate already appears in Amazon Ohio voter fights and South Korea budget for chips.

Policy and siting implications

When utilities fast-track data center interconnect, as in PJM one-year energization, regulators ask whether ratepayers fund transformer upgrades for AI tenants. A fossil-heavy fraction strengthens opposition in energy protest counties.

Builders choosing AWS, Azure, or GCP regions should pair latency tables with emissions dashboards. Blackstone and Amazon claims show how finance narratives race ahead of disclosure.

What the study does not resolve

Coverage does not replace facility-level power purchase agreements with open telemetry. RECs, hourly matching, and on-site gas each need separate accounting — our Wyoming Google post walks one gas-with-capture design.

Nor does the paper allocate blame between legacy cloud and new AI-only builds; hyperscale is a shared asset class.

Connecting study numbers to your cloud bill

Hyperscale emissions scale with megawatt-hours, not parameter counts. A 70B fine-tune on clean-grid spot GPUs can beat a dense 400B job on coal-heavy reserved capacity if you measure Scope 2 honestly. Carbon-aware orchestrators in Kubernetes and Slurm exist; few teams wire them to finance KPIs.

Colocation buyers should request substation name, balancing authority, and historical heat rate before signing 10-year leases. Marketing REC purchases without hourly matching will face harder questions after this Nature Sustainability cycle.

Students training course models on university clusters inherit the campus grid — often fossil-heavy in US Midwest despite green campus pledges. Faculty should disclose grid zone in syllabus ethics sections the same way they disclose dataset licenses.

Checklist for climate-conscious ML teams

  1. Ask your provider for location-based emissions, not only market-based certificates.
  2. Schedule heavy jobs when grid carbon intensity is lower if your orchestrator supports it.
  3. Right-size training: our higher-scoring models merge-rate study shows quality per GPU hour beats vanity scale.
  4. Watch local bans — Spacex Starbase permit fights show permitting is political, not only engineering.

How this compares to corporate net-zero pledges

Hyperscalers routinely announce 100% renewable targets while building in counties where nighttime grid mix still burns gas. The Harvard framing, as reported, pressures disclosure that matches physics, not marketing slides alone.

Carbon-aware scheduling in Sage science agents and Nemotron science tools does not fix training clusters; it helps inference teams shift load. Training still dominates embodied carbon for frontier runs.

Lawmakers may cite this study in data-center moratoria like those in Ohio voter battles. AI labs should expect siting hearings to request hourly emissions, not annual averages.

How to read the primary source

The DOI path is Nature Sustainability s41893-024-01398-w. Journal pages may block bots; use an institutional login or author PDF when available.

We cite reported statistics from outlets summarizing the paper on November 18, 2026; if the PDF differs, trust the PDF and we will update this page the same week.

Data center renewable energy mix versus fossil baseload on the gridData center renewable energy mix versus fossil baseload on the grid

Interconnection queues and the fossil reality

Utilities approve new hyperscale feeders faster when economic development offices promise tax revenue. PJM one-year energization shows grid operators bending timelines for AI load. When new lines still terminate in gas-heavy balancing authorities, PUE 1.1 halls still emit.

On-site gas fuel cells, like Google Wyoming, shift combustion location but not chemistry. Researchers counting lifecycle emissions may treat fuel cells differently than grid imports — read the paper’s methods before you quote a single national average.

Geothermal pilots such as Google Quaise Oregon are the engineering response this study implicitly demands. They take years; GPU demand takes quarters.

Methodology questions serious readers should ask

Peer-reviewed facility-level work should answer:

  • How were 403 sites selected — only self-reported hyperscale, or registry matched?
  • Which emission factor tables converted MWh to CO2 — eGRID year version matters.
  • Did researchers attribute renewable certificates to physical flows or market-based accounting?
  • What share of load was inference versus general cloud?

Until you read the PDF, treat outlet summaries as directional. explainx.ai will update the FAQ if author tables differ from November 18 headlines.

Regional siting examples already in our corpus

table · 3 cols
RegionStory we coveredFossil angle
WyomingGoogle fuel cellsOn-site gas
OhioAmazon $17BGrid fights
OregonQuaise geothermalGeothermal bet
TexasStarbase permitsPermit politics

Harvard’s national rollup does not replace county fights; it fuels them.

What hyperscalers may do next

Expect more hourly-matching PPA announcements, nuclear colocation headlines, and liquid cooling capex — data-center liquid cooling interconnection stories already tie thermal to queue time.

Model labs may publish training-job carbon labels the way Model Cards publish licenses. Buyers should demand region + kWh metadata in API billing exports. Without kWh, carbon claims in vendor RFPs remain unauditable marketing.

Media and policy reactions to watch

Expect state attorneys general to cite Harvard figures in moratorium briefs. ISO/RTO comments may reference Denmark comparison rhetoric. Corporate sustainability officers will reissue hourly matching pledges.

AI labs should prepare facility-level GHG inventories for customers asking Scope 3 questions about training jobs. InclusionMed benchmarks show sector-specific ESG pressure; hyperscale is next.

Related reading

  • AI and climate change paradox
  • Google Wyoming gas fuel cells
  • PJM fast energization
  • Amazon Ohio data center bans
  • Google Quaise geothermal Oregon
  • RTX Spark local desktops
  • Nvidia Q3 zero China DC outlook

Inference versus training: different carbon stories

Training a frontier model concentrates weeks of GPU max power in one campus. Inference spreads smaller wattage across millions of requests but runs forever. Harvard’s facility-year accounting captures both when hyperscale halls host mixed workloads.

Teams publishing “green AI” should separate training emissions (job-specific) from serving emissions (product-specific). GPT-6.2 launch coverage discusses API scale without facility attribution — fill that gap in your ESG appendix.

Denmark comparison: how to use it responsibly

Outlets compare 25.7 million metric tons to Denmark’s national total as shock value. Denmark is small and already decarbonizing power; US hyperscale sits inside a much larger, mixed grid. The comparison illustrates scale, not 1:1 policy equivalence.

Advocates may misuse the line; engineers should translate it into Marginal Operating Emissions Rate for each substation you actually interconnect.

Water, noise, and secondary siting fights

Fossil share is not the only opposition lever. Water cooling withdrawals and generator noise dominate local hearings even when corporate slides show solar fields. Pair this climate study with permit posts above when you site new racks.

Community and labor angles

Data-center opposition increasingly alliances climate groups with water and noise activists. Amazon Ohio is a template for local ballot fights. Harvard statistics give advocates national citable numbers — expect them in comment dockets.

For ML engineers: when you choose a region for fine-tuning, log grid zone alongside loss curves. Future customers will ask why you picked a fossil-heavy balancer when a cleaner zone was ten milliseconds slower. That audit trail starts before the Nature paper lands on your CFO’s desk, not after the next state moratorium headline.

Bottom line: treat hyperscale grid mix as a first-class SLO next to latency and price. The Harvard rollup gives advocates and CFOs a shared number; your job is to map it to regions you actually train in.

Emission totals and fossil shares follow November 18, 2026 coverage of the Nature Sustainability paper unless the published tables differ.

Spotted something out of date? Let us know.
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

  • ✓ Free
  • ✓ One email a day, no spam
  • ✓ Unsubscribe anytime
Yash Thakker

Written by

Yash Thakker

Yash is an AI expert with over 300K learners. Join his workshops →

View Yash Thakker in People in AI →

Related posts

Oct 31, 2026

Sierra Club: AI Data Centers Could Add 42% to US Power Emissions by 2030

A Sierra Club analysis, first reported by Bloomberg, says data-center demand could push US power-sector emissions to 2.1 billion metric tons by 2030, erasing about 15 years of cuts. The numbers are reported second-hand and describe a high-impact scenario, not a forecast.

Nov 18, 2026

SpaceX Starbase: Texas TCEQ Air Permit for Boca Chica Gas Turbines and AI Campus

Regulators issued an air pollution permit Monday for SpaceX's planned gas-fired power and supercompute site at Boca Chica. Filings describe about 748 MW of turbines and SIC codes for data processing.

Nov 17, 2026

Google Quaise Deal: $500M Oregon Geothermal for AI Power

Google agreed to buy 50 megawatts from Quaise Energy's Project Obsidian superhot rock geothermal plant in central Oregon in a 15-year deal valued above $500 million, with delivery targeted from June 2030.