
Share
Two Virginia grid incidents exposed a design flaw baked into decades-old data center power stacks. Fixing it means rethinking where voltage conversion, energy storage, and protection logic actually live, not just building more turbines.
On July 22, 2026, a transmission line fault in Ashburn, Virginia knocked more than 3 gigawatts of load off the grid in seconds. This wasn't a one-off. Two years earlier, a single failed surge arrester dropped roughly 60 Virginia facilities and 1,500 megawatts at once. Ashburn happens to host the world's largest data center cluster, so when something breaks there, it breaks at scale.
Everyone's talking about the supply side of AI power: more turbines, more solar, more transmission capacity. Fair enough, the grid does need more electrons. But these outages weren't generation failures. They were architecture failures. And a massive wave of new gigawatt-scale interconnections is about to land on that same fragile architecture. Nobody in the stack seems to own the fix.
Here's the core issue: the grid was engineered around predictable, well-behaved loads. Steel mills. Refineries. Houses drawing power at dinnertime. Different magnitudes, sure, but similar behavior: smooth draws, occasional hiccups, graceful recovery.
AI data centers don't play by those rules. A single AI campus can swing 70% of its load in milliseconds mid-training run, then yank itself offline the instant something upstream looks unstable, all to protect billions of dollars in compute. Each facility acting this way in isolation is a rational, defensible engineering decision. Thousands of them doing it simultaneously at gigawatt scale is a systemic problem the grid was never built to absorb, and the next generation of AI campuses is being planned at exactly that scale.
The standard data center power stack hasn't fundamentally changed in decades: medium-voltage power comes in, transformers step it down, low-voltage UPS units condition it, and it finally reaches the racks. That design cracks in three specific places once you push it to AI scale.
None of this is sloppy engineering. It's careful, deliberate engineering that the load profile has simply outgrown.
The fix isn't one silver-bullet component. It's three coordinated moves.

Move it up: shift from 480 volts to medium voltage, 13.8 kilovolts and higher, which is the voltage tier large sites already draw from the grid anyway. Move it out: relocate power conditioning from inside the data hall to modular enclosures near the substation, so the building itself only holds compute and the cooling that keeps it running. Move it into the path: replace a battery that watches and reacts with a system that every electron physically runs through, continuously. There's nothing left to detect and nothing to switch, because nothing was ever routed around it in the first place.
Three upgrades that sound straightforward on paper. In practice, they rewrite nearly every downstream line item in the design.
When thousands of GPUs spin up together under this architecture, the system absorbs the swing internally and hands the grid a flat, boring load profile. When a disturbance hits from the grid side, the equipment behind the barrier never even notices. A difficult grid neighbor turns into a predictable one, and when the utility actually needs help balancing load, that same facility becomes genuinely useful instead of a liability.
Interconnection gets simpler too. The utility only has to certify one medium-voltage box instead of untangling an entire lineup of transformers, UPS units, chillers, pumps, and switchgear behind it. Engineers can swap GPU generations without triggering a fresh interconnection study. That shaves real months off permitting timelines.
Inside the fence, former UPS rooms become usable compute or cooling space, so density per construction dollar climbs. And the economics genuinely flip: equipment that runs at medium voltage, sits outdoors, and stores its own energy can qualify for tax credits and earn revenue through grid programs like peak shaving and demand response. Backup power stops being a sunk insurance cost and starts actually paying for itself.
Early in 2026, a full-scale version of this system was tested at the National Laboratory of the Rockies, a U.S. Department of Energy facility and reportedly the only site in the Western Hemisphere that can replicate real grid faults and AI-scale load swings concurrently in the same test loop. The system was hit from both directions at once: realistic AI load profiles on the compute side at full medium voltage, and grid faults, including a full zero-voltage event, on the utility side. Neither side flinched. The system cleared the large-load voltage ride-through requirements set by the Electric Reliability Council of Texas (ERCOT) with room to spare.
Those ride-through rules exist precisely because grid operators no longer take gigawatt-scale facilities on faith, and more of them are arriving every quarter. Most of the industry still treats these compliance requirements as hurdles to clear after the fact. A medium-voltage, inline architecture clears them by default, as a byproduct of how it's built rather than a bolted-on feature.
Much of what looks like a grid capacity problem in the AI buildout is actually sitting inside the fence, in equipment that was sized decades ago for a load profile that no longer exists. Shift the right pieces up in voltage, out of the building, and into the power path, and a facility that's currently a grid liability becomes a grid asset instead. Density goes up, permitting time comes down, and backup power finally earns its keep instead of sitting idle. The industry hasn't settled on a name for this layer yet, sometimes called a medium-voltage AI UPS, but the naming matters far less than the underlying choice every operator is now facing: build the next wave of AI factories as a strain on the grid, or build them as reinforcement for it.
Tags
Original Sources
Powering AI is an architecture problem
↗ https://www.technologyreview.com/2026/09/10/1141649/powering-ai-is-an-architecture-problem
About the author
Kai built ML infrastructure at a Bay Area startup before developing an obsession with transformer architectures and inference optimisation that eventually pulled him out of product work entirely. A stint at a compute research lab sharpened his instinct for what actually matters in a model release versus what is marketing. He writes from the inside — from the perspective of someone who has debugged the systems he is describing at three in the morning. He is allergic to hype and instinctively drawn to the unglamorous plumbing questions that everyone else skips over.
More from The Engineer →This Week's Edition
11 September 2026
33 articles
Related Articles
Related Articles
More Stories
© 2026 Cedar & Bloom. All rights reserved.