AI Data Centers Are Now Waiting on Power Lines, Not Chip Deliveries

Oracle's planned Wisconsin AI data center is delayed, and the reason is not silicon. The project is waiting on regulatory approval for a grid connection, which puts 2027 customer delivery at risk. Around the same time, more than $800 million in new capacity moved through grid or planning approvals: a 250 megawatt campus in Pyhajoki, Finland that overrode local opposition, a $270 million project in Egypt, EUR 401 million of EU funding in Poland, and EUR 80 million in France. Each of those projects depends on power infrastructure, not on chip supply.
For two years the AI infrastructure conversation has been about accelerators. That is shifting. The constraint that now decides whether a data center opens on schedule sits upstream of the server rack.
The rack outgrew the building
An AI-optimized rack now demands anywhere from 30 kilowatts to more than 100, and some deployments push past 150 kilowatts. A traditional enterprise rack draws a small fraction of that. This is not a marginal increase that can be absorbed by existing electrical rooms and cooling loops. It requires new substations, new transformer capacity, and in many cases liquid cooling plumbed into the floor.
The numbers on the electricity side are large enough to matter at a national scale. US data center consumption is around 180 terawatt hours today, and credible forecasts put it at 400 to 600 terawatt hours by 2030. That is the kind of demand growth that turns a utility into a partner with bargaining power, and turns an interconnection queue into a schedule risk.
Oracle's Wisconsin delay is the clearest illustration. The company is building for AI customers with 2027 commitments, and a transmission approval can slip by quarters without anyone at the chip vendor being able to help.
Operators are becoming energy companies
The response has been to vertically integrate. Data center operators now sign power purchase agreements, invest in generation, and in some cases build the connection themselves. The Enetron project in Finland needed a zoning override, which is what happens when a 250 megawatt load is large enough to dominate a local grid's planning.
This changes the economics of a data center in a way that is easy to miss. Historically, site selection optimized for land cost, fiber routes, and tax incentives. Power was a utility bill. Now power availability is a gate on the timeline, and the cheapest land near a population center is often the worst place to build because the grid is already loaded.
That is why the new projects cluster where they do. The Nordics have hydroelectric capacity and cool air. Egypt has cheap generation and proximity to European and Middle Eastern demand. Poland and France are using public money to make connections happen faster. The pattern is not about technology. It is about electricity and heat.
Memory turned out to be the other shortage
While the industry watched power, a second constraint tightened. High bandwidth memory has become the scarcest input in the rack. Micron's HBM4 trades at roughly 15 times the unit value of standard DRAM by weight. That is a price signal strong enough to reorder supply chains, because HBM is not a commodity that can be swapped for a cheaper part when availability is tight.
The historical imbalance is stark. Compute throughput in AI chips has grown by roughly a million times over the industry's lifetime, while memory bandwidth has grown by a factor of about 40. Accelerators can execute arithmetic far faster than memory can feed them, which is why the workarounds matter so much. FP8 and FP4 quantization halve and quarter the memory footprint of a model, and techniques like mixture-of-experts activate a small slice of parameters per token so that a model with trillions of total parameters does not need all of them resident at once.
Those techniques are not optimizations you apply if you have spare capacity. They are the reason the workloads fit at all, and they constrain which model architectures are practical to deploy. A team choosing between two models now weighs memory bandwidth per token as heavily as it weighs benchmark scores.
Memory decides which architectures ship
The memory constraint does more than limit supply. It shapes what gets built.
A model with a very large context window has to hold a large key-value cache during inference, and that cache competes with the weights for the same memory. Architectures that looked efficient on paper become impractical when the cache alone exceeds what fits on a device. This is why techniques that trade computation for memory, including paging the cache to host memory or compressing it, have moved from research curiosities to standard components.
The result is that architecture decisions increasingly follow memory availability rather than the other way around. A team that wants a longer context has to decide whether the accuracy gain justifies the memory bill, and the answer often depends on which accelerator generation it can actually obtain. Those are supply chain decisions wearing the clothes of model design.
High bandwidth memory makes this sharper because it is a specialized product with a small supplier base. Standard DRAM can be sourced widely and substituted. HBM is produced by a handful of manufacturers, comes in fixed stacks, and is allocated well in advance. A shortage does not resolve by paying more. It resolves by waiting.

Why this changes the competitive map
When chips were the constraint, the company with the best accelerator had the advantage, and buyers queued. When power and memory are the constraint, the advantage moves to whoever can secure megawatts and memory allocations, which favors firms with balance sheets, long-term utility relationships, and the patience to build generation.
That is a different set of winners. A well-capitalized cloud provider that signs a 20-year power agreement has an edge an engineering team cannot match with a better kernel. It also means geography matters again, because electricity is local and memory fabs are few.
There is a second-order effect. If interconnection queues stay long, the pressure to use existing capacity more efficiently grows. That favors techniques like quantization and speculative decoding, and it favors smaller models that can be served on hardware already installed rather than hardware that is still waiting for a substation.
What to watch
The interconnection queue. If approvals for large loads take longer next year than this year, more projects slip, and the schedule risk becomes a planning assumption rather than a surprise.
The memory price curve. HBM pricing relative to standard DRAM tells you how much of a premium buyers will pay for bandwidth. If the premium compresses, supply has caught up. If it widens, the shortage is setting more of the roadmap.
Whether operators keep buying generation. Every data center that becomes an energy company changes the utility industry's customer list. If a few large operators own meaningful generation capacity, the next round of AI capacity will be built where they can make the power rather than where the power already is.
The chip story continues, but it no longer sets the deadline. The projects that open on time in 2027 will be the ones that solved the connection and the memory allocation first, and the accelerator they ship will be the easy part.
Related articles
The Video Model Leaderboard Nobody Markets: Where the Requests Actually Go
Every week brings a new video generation ranking, and almost all of them are built the same way.
Ai2 Open-Sourced the Training Stack, Not Another Set of Weights
Weights are easy to give away and hard to learn from.
Alibaba's Qwen3.8-Max Claims It Can Code by Itself for a Fortnight
Parameter counts stopped being news a while ago. Twelve days is the number worth examining.
PixelUMM Throws Out the Two Components Every Visual AI Model Depends On
Pixel-level diffusion has been proposed before and has repeatedly run into compute.