Daylila

Information Technology · Monday, 17 August 2026

01 · Briefing · what happened

America's biggest grid wants the right to switch data centers off

Information Technology 6 min 20 sources

PJM has proposed pushing data centers onto their own backup generators when power runs short, after its capacity auction hit the price cap and still came up 6.8 gigawatts short.

6.8 GW

reserve PJM is short

even after prices hit the auction cap

28%

of requested power likely built

of the 1,066 gigawatts asked for

$325

per megawatt-day price cap

hit at PJM's latest capacity auction

88%

rise in Dominion's fuel costs

over five years in Virginia

At a glance

  • PJM, America's biggest grid operator, asked for the power to force data centers onto their own backup generators when electricity runs short.
  • Its latest capacity auction hit the $325 price cap and still came up 6.8 gigawatts short of the reserve it says it needs.
  • Utilities have been asked for 1,066 gigawatts of new data center power; Wood Mackenzie expects only about 28% of it to be committed.
  • Texas paused new data center approvals on 3 August, and the federal forecaster promptly cut the state's 2027 power growth from 14% to 6%.
  • Amazon's answer is its own gas plant in Texas, permitted for up to 33 million tons of carbon a year - more than any US power plant today.
  • Virginia is the first state to tax data centers on the power they draw, worth up to $600 million next year.
  • Dominion's fuel costs are up 88% in five years, and average Virginia bills could rise 13%.
  • Amazon's cloud, separately, told engineers to conserve processor time after wait times for ordinary CPU capacity exploded.

Forces in play

Grid strain High

PJM came up 6.8 gigawatts short of its reliability reserve even after prices hit the cap, which is the gap that raises blackout risk.

Local pushback Building

Virginia now taxes data centers on the power they use, and Palm Beach county voted 5-1 against expanding one near a school.

Phantom demand Steady

Wood Mackenzie expects only 28% of the 1,066 gigawatts requested to be committed, so the queue overstates what is really coming.

Build your own Building

Amazon is putting a 33-million-ton gas plant beside a Texas data center, and Alpha Compute is buying gas rights outright rather than wait for a grid connection.

In play PJM Interconnection — wants the right to curtail data centers in an emergency Amazon — building its own gas plant in Pecos County, Texas Virginia lawmakers — first in the country to tax data centers on power use Wood Mackenzie — says two-thirds of the requested power will never be built Amazon Web Services — told engineers to conserve processor time as wait times exploded

How it unfolded

  1. Late June Virginia becomes the first state to tax data centers on power use
  2. 3 Aug Texas pauses new data center approvals pending an audit
  3. 11 Aug Dominion filings show fuel costs up 88% in five years
  4. 12 Aug Wood Mackenzie: only about 28% of requested power is likely to be committed
  5. 13 Aug PJM proposes forcing data centers onto backup generators in emergencies
  6. 16 Aug IEEE Spectrum reports an explosion in wait times for AWS processor capacity

Where this points

Watch whether any PJM state actually grants the power to curtail data centers - without a state saying yes, the proposal stays a request and the 6.8-gigawatt gap runs into next summer.

Full briefing

The grid pushes back

On Thursday, PJM Interconnection proposed a framework that would force data centers to run on their own backup generators when grid supply gets dangerously low [1]. PJM is the largest grid operator in the United States. It manages electricity for 67 million people, from Washington DC to Chicago [1].

The trigger is arithmetic. PJM runs a capacity auction, the market where it pays generators years in advance to promise power on the worst days. The most recent one hit its price cap of $325 per megawatt-day [1]. Even at the cap, PJM came up about 6.8 gigawatts short of the reserve it says it needs to avoid blackouts [1]. High prices are supposed to summon new power plants. They did not summon enough.

PJM cannot actually switch anyone off. It says it would need individual state governments to agree [1]. It also proposed a registry tracking where very large power users sit and how much they draw [1]. The plan is aligned with the White House’s Ratepayer Protection Pledge, a non-binding promise to keep data center costs off household bills [1].

Demand climbs regardless. The US Energy Information Administration expects national power use to rise from a record 4,195 billion kilowatt-hours in 2025 to 4,391 billion by 2027 [2].

Two-thirds of the queue is a mirage

Utilities have been asked for 1,066 gigawatts of new data center power in the US [3]. One gigawatt is roughly what a traditional nuclear reactor produces [3]. The consultancy Wood Mackenzie now expects grid operators and utilities to commit to about 28% of that [3]. The rest, it says, is phantom projects and long-shot pitches [3].

That queue is what everyone plans against, which is why questioning it moves real numbers. Texas paused new data center approvals on 3 August pending an audit [2]. The EIA promptly cut its forecast for Texas electricity growth in 2027 from 14% to 6% [2].

So build your own power

If the grid cannot say yes fast enough, the answer is to stop asking. Amazon is investing in a gas plant at its Pecos County data center in Texas [4]. Regulatory records show it would be permitted to release up to 33 million tons of carbon dioxide a year, more than any other power plant in the country [4]. Amazon says the site is “powered by new on-site generation that won’t raise electricity costs for Texas families” [4].

It will burn that gas the inefficient way. The plant relies on simple-cycle turbines, which throw away the waste heat [5]. Grid plants usually add a second steam turbine to capture that heat and emit less for the same power [5]. Even at half its permitted level, the Amazon plant would out-pollute 78 average US gas plants, on EPA figures [5]. The reason is speed. There is a years-long backlog for turbine orders and parts, so developers take what they can get, says Britt Burt of the energy research firm Industrial Info Resources [5].

Others are buying the fuel outright. Alpha Compute signed a binding term sheet for Pennsylvania land and about 1,800 acres of Marcellus gas rights, for $55 million [6]. It hopes to run a 200-megawatt campus there by the third quarter of next year [6]. Heron Power will spend $100 million turning a 286,000-square-foot warehouse south of San Jose into a transformer factory [7]. Its 5-megawatt units are the unglamorous hardware that connects a very large load to a grid; mass production is planned for late 2027 [7].

Elsewhere the shortage reads as an opening. Eskom’s chair says the South African utility has “power that we cannot sell” now that years of blackouts have ended, and is courting data centers [8]. In Europe, Mistral is pre-selling capacity it has not built yet. Multi-year enterprise commitments will underwrite 200 megawatts by the end of 2027 and a full gigawatt by 2030, the company says [9].

Who pays

Virginia became the first state to tax data centers on the electricity they consume, in late June [10]. State senator L. Louise Lucas expects up to $600 million in the coming year [10]. “How do we let the wealthiest companies in human history come to the commonwealth,” she said, “and not play by the same rules as everyone else?” [10]

The bills are already moving. Dominion’s fuel costs in Virginia are up 88% in five years, to a forecast $4.35 billion through June 2027 [11]. The utility now buys 23% of its supply on PJM’s wholesale market, up from 14% in 2021 [11]. Average monthly bills could rise as much as 13%, to $195 from $173 [11].

Local votes are turning too. Palm Beach county commissioners voted 5-1 last month to deny an expansion of a large data center [12]. It was proposed about 1,200 feet from an elementary school, and the hearing ran more than 12 hours [12].

The macro picture is stranger. Build-out spending is pushing up prices for electricity, chips, software and data center space, while corporate adoption stays uneven, which complicates the Federal Reserve’s inflation call [13]. The predicted job losses have not arrived either. Employment in the occupations most exposed is “largely stable”, Stanford’s Erika McEntarfer told the Guardian [14].

Also moving

Judge Donato gave Google one week to make third-party app stores easy to find and install inside Google Play, calling the current flow unacceptable [15]. Apple, facing the same kind of order, proposed taking 5% to 15% of purchases made through outside payment links, down from the 12% to 27% Epic called non-compliance [16]. The Ninth Circuit refused to halt the states’ social-media addiction case against Meta, ruling that Section 230 is a defense at trial rather than immunity from being sued [17]. Cisco guided fiscal 2027 revenue above estimates on AI networking demand; its shares rose 3% after hours and are up more than 56% this year [18]. And a public television station lost access to 50 terabytes covering 70 years of broadcast history after its cloud storage vendor dissolved [19].

The bottleneck nobody was watching

The under-covered story of the week is a chip nobody has been arguing about. Amazon Web Services told engineers to conserve processor cycles “at all costs” after an explosion in wait times for ordinary CPU server capacity, IEEE Spectrum reported [20].

CPUs are the general-purpose processors that run normal software; GPUs are the parallel chips that run AI models. Two years of shortage talk has been about GPUs and memory. But agents do not just think, they act, and acting runs on the CPU. AMD’s Madhu Rangarajan says seven of the eight stages in a realistic agent pipeline run entirely on the CPU [20]. Intel’s Souvik Kundu and researchers at Georgia Tech found each chip sits idle waiting on the other [20]. The GPU waits during tool calls; the CPU waits during model inference. Rescheduling the two can cut total time by up to 1.8 times under sustained load, they found [20]. One OpenAI model fired off as many as 300 actions an hour [20].

If you run agents in production, the number worth tracking is how long a task waits for a processor, not how much you spend on GPUs.

02 · Lesson · why it matters

Why a system jams long before it is full

Waiting time does not climb gently as a system fills up. Past a certain point it explodes, and nothing had to break for it to happen.

How it works

  1. A shared line has a fixed speed
  2. Work arrives unevenly, in bunches
  3. Idle gaps are what let the backlog drain
  4. Fill the gaps and there is nothing left to drain in
  5. So waiting explodes near full, with nothing broken

The twist

Nothing slows down as a system fills up, yet the waiting explodes anyway - from about one job's wait at half full to nineteen at ninety-five percent.

Where you've seen this

Hospital wards

a ward run at 95% occupancy keeps people on trolleys, because there is no empty bed to absorb a bad night

Motorways

traffic collapses into stop-start well below the road's maximum, once the gaps between cars run out

A small team

the person with no free hours becomes the step everything else waits on

Airport runways

one delayed departure at peak ripples all day, because nothing is idle enough to absorb it

The catch

The arithmetic assumes work arrives unpredictably; make arrivals perfectly regular - a booked slot, a scheduled batch - and a line really can run near full with almost no queue.

Full lesson

Two shortages, one arithmetic

PJM did not lose a power station this week. Its generators still work. It simply reached the point where almost every spare megawatt is spoken for, and at that point a hot afternoon stops being weather and starts being an emergency.

Amazon Web Services did not lose any processors either. But wait times for ordinary processor capacity climbed so sharply that engineers were told to stop wasting cycles.

Two very different systems, one week apart, describing the same thing: the moment a shared resource gets close to full, the waiting goes strange.

The numbers are worse than anyone guesses

Here is the arithmetic, and it is the whole lesson.

Take a shared line where work arrives at unpredictable times. Call it half busy. On average, a new arrival waits about as long as one job takes to do. Reasonable.

Now run it at nine-tenths busy. The arrival waits about nine times the length of one job.

Run it at ninety-five percent busy, the number a good manager is proud of, and the wait is nineteen times.

Nothing got slower. The same machine, the same staff, the same speed per job. Only the fraction of time it is occupied moved, and the waiting multiplied by nineteen.

Idle time is the drain

The reason is the unevenness. Work does not arrive in a tidy stream. Cars bunch. Patients arrive three at once. Agents fire off three hundred actions in an hour and then nothing.

When a bunch arrives, a backlog forms. The only thing that clears it is the quiet stretch afterwards, when the line has capacity nobody is using.

So the idle time is not waste. It is the drain. Push how busy you run it and you are not adding output so much as removing the drain. Then the backlog that forms at four o’clock is still there at six.

That is why PJM’s answer is not more power. It is the right to switch some load off at the peak. It is buying back idle time by contract.

The number that got treated as a fact

Someone, somewhere, decided that how busy a thing is running is the measure of whether it is well run. That decision is not physics. It is a convention, and it is old enough to look like one.

It has a shape, and the shape has a beneficiary. How busy a machine is running is easy to count, and it sits on the side of the ledger the owner reads. Waiting is felt on the other side, by whoever is in the line, and it rarely gets counted at all. So the pressure runs one way, always, in every organisation that has ever measured a machine.

That is how the grid ended up here. Nobody chose blackout risk. A thousand reasonable decisions to sell one more connection added up to a system with no gaps left.

Who is standing in the line

The reader is in this arithmetic, not watching it.

A Virginia household did not order a data center. Its bill may rise 13% anyway, because the utility now buys nearly a quarter of its power on a market where the peak price is set by scarcity. That is the wait showing up as a price.

It is the same shape as an ambulance held outside a hospital running at ninety-five percent occupancy. The same as the road that jams at five although it carried the same cars at two. The same as the one colleague who never has a free hour, and so everything queues behind them.

None of those systems is broken. Each is being run the way its own scoreboard rewards.

What a full system hides

The uncomfortable part is that a system at ninety-five percent looks excellent from inside. Every meter reads busy. Nothing is obviously wrong. The failure is not in any one component. It lives in the relationship between how full the thing is and how long people wait, and no single seat sees that.

PJM can see the shortfall and cannot switch anything off. A state can switch things off and cannot see the whole grid. A household sees only a bill. Each is looking at a real thing and none of them is looking at the system.

03 · Lab · your turn

How Full Do You Run It

Set how busy a shared line runs, and feel the waiting explode long before the line is actually full.

04 · Hope · carry this

Every jam we have ever cleared was cleared by someone deciding that a little unused room was worth paying for. This week, people started reaching for that decision again.

Across the beats