• Google says long-term contracts with five utilities—Entergy Arkansas, Minnesota Power, DTE Energy, Indiana Michigan Power and Tennessee Valley Authority—now include 1 GW of data-center demand-response capacity. Reuters described up to 1 GW of demand as available for curtailment during peak periods.
  • The number measures an enrolled control option, not energy already saved. Google can limit or shift only eligible portions of machine-learning workloads at certain sites and times. Dispatch dates, duration, requested and delivered megawatts, service effects and verified customer savings for the five-utility portfolio are not disclosed.

The milestone is contractual capacity, not a delivered cut

Google's 19 March disclosure says it integrated 1 GW of demand-response capacity into long-term energy contracts. Reuters reported that the contracts make up to 1 GW of data-center demand available for curtailment when system demand is exceptionally high. Neither statement says utilities have called the full amount.

A complete operating record would identify each event, the utility request, the counterfactual baseline, megawatts promised and delivered, duration, recovery load and settlement. None of those portfolio-wide figures is public, so 1 GW should not be reported as electricity already reduced, a blackout avoided or a saving delivered.

Control reaches selected workloads, not every data-center service

Google says it can limit or shift a portion of machine-learning workloads. Its earlier programme moved non-urgent compute such as some YouTube video processing, while reliability requirements constrain Search, Maps and Cloud services in essential industries. Flexibility is available only at certain locations and periods.

The August 2025 disclosure provides the clearest operating precedent: an Omaha Public Power District demonstration reduced ML-associated demand during three grid events. Google then announced agreements with Indiana Michigan Power and Tennessee Valley Authority before adding the other three utilities. The demonstration does not establish the later portfolio's response rate.

Five utility agreements have different local structures

The March milestone groups Entergy Arkansas, Minnesota Power and DTE Energy with the two earlier utilities, but it does not publish how the 1 GW is divided. Minnesota Power's separate agreement for a planned Hermantown center also covers 300 MW of wind and 400 MW of battery storage and says the parties will identify flexibility opportunities.

DTE Energy separately describes contracts for a planned 1 GW data center in Van Buren Township. That facility load is not Google's portfolio-wide demand-response figure. DTE's estimate of nearly $1.7 billion in affordability benefits over the contract life is forward-looking and is not a measured saving from curtailment.

Grid benefits remain a claim to be tested

Demand response can help a utility meet peaks, plan reserves and bridge the period before generation, storage or transmission arrives. Google argues that flexibility can improve reliability and affordability; those are plausible mechanisms, but the five contracts alone do not prove fewer outages, lower bills, less fossil generation or faster interconnection.

Results depend on when a utility can call the resource, which workloads qualify, how baselines and rebound are measured, and whether new data-center load exceeds the flexible portion. Regulators and utilities also control tariffs, resource plans, settlements and customer protections.

What the evidence supports now

The defensible statement is that Google has contracted a sizeable demand-side option across five U.S. utilities and has previously demonstrated limited ML-load reductions during three events. It is incorrect to convert that option into a record of continuous automated curtailment or verified system outcomes.

The next useful disclosure is an event ledger: called and delivered MW, duration, location, workload class, recovery load, availability, non-performance and independently reviewed bill and reliability effects.

What to watch next

  • Utility or regulator filings allocating the 1 GW among the five contracts.
  • Event-level requested, committed and delivered MW with duration and baselines.
  • Which ML workloads can move without affecting Search, Maps, Cloud or other services.
  • Rebound demand after a curtailed or shifted workload is restored.
  • Interconnection dates and whether flexibility is temporary or permanent.
  • Measured bill, reliability, emissions and capacity effects rather than company forecasts.

Sources

  • Reuters, 19 March 2026: five utilities and up to 1 GW of data-center demand available for peak-period curtailment
  • Google, 19 March 2026: 1 GW integrated into contracts, partial ML-workload control and explicit site and flexibility limits
  • Google, 4 August 2025: initial Indiana Michigan Power and Tennessee Valley Authority agreements and the three-event Omaha demonstration
  • Minnesota Power, 3 March 2026: Hermantown service agreement, 300 MW wind, 400 MW storage and prospective flexibility work
  • DTE Energy, 30 April 2026: separate planned 1 GW Van Buren data center, filed contracts and forward-looking affordability estimate