Begin with the number that settles the first question. American data center vacancy in the first half of 2026 was 1.4 percent.
That is a record low. It is the third straight year near one percent.
More than 66 gigawatts are under construction across North America, and 80.4 percent of it is already leased. Signed, before the concrete cured.
Across every primary market, under 1,500 megawatts remain available. At the rate space is being taken up, that is about six months of supply.
So whatever is happening here, nobody is sitting on empty halls.
The worry is still right. It is just aimed badly
Something in this build will go obsolete fast. That instinct is correct.
The mistake is assuming it is the building.
A data center is really two things in a trench coat. There is the shell, with its power feed, its grid connection, its cooling, its land and water rights. And there is the silicon racked inside it.
They run on completely different clocks.
| The two halves | How long it lasts | Is it scarce |
|---|---|---|
| Shell, power, interconnect | Twenty to thirty years. Concrete and copper do not improve. | Severely. Roughly 8,200 projects wait in the grid queue. Large transformers run 24 to 36 months. |
| The chips inside | A one year product cycle. Economically stale for frontier work in two or three. | Not at all. Nvidia will happily sell you more. |
You cannot overbuild a grid connection in a country with 8,200 projects already standing in line for one. You can very easily overbuy graphics cards.
The escalator
Now the number that should actually worry a builder, and it has nothing to do with vacancy.
The average server rack drew about 16 kilowatts last year. This year it draws about 27. Forecasts put the average near 40 within a few years.
Then look at what the frontier systems draw.
A Blackwell NVL72 rack pulls roughly 130 kilowatts. The Rubin generation lands between 190 and 230. The Rubin Ultra rack planned for 2027, the one called Kyber, is specified at about 600.
And air cooling stops working somewhere around 35 kilowatts a rack. Not gets expensive. Stops working.
Look at the left of that chart. The average rack, the one in the overwhelming majority of American data centers, is a sliver.
Now look at 2027.
Which buildings actually go empty
Here is the answer to the question, and it is not the new ones.
Sixty-eight percent of enterprise data centers built before 2015 cannot deliver the power density or the cooling AI work needs. They were designed around 10 kilowatt racks, in an era when that was generous.
Retrofitting them runs $50,000 to $100,000 per rack. That buys a path to somewhere between 40 and 70 kilowatts.
Which is still less than one Blackwell rack. The money does not get you to the starting line.
And here the escalator becomes a builder's problem rather than a historian's. A hall designed today around 130 kilowatt racks is state of the art. It may also be unable to take the 600 kilowatt racks shipping next year.
That is obsolescence inside a single capital cycle, and it is the real thing to engineer against.
The number that moves on paper
There is a second kind of stranding, and it shows up in an accounting line rather than in a parking lot.
Amazon, Microsoft and Google all stretched the assumed useful life of their servers from three or four years to six. On more than $300 billion of annual capital spending, that is worth roughly $18 billion a year in earnings.
Michael Burry put a figure on the gap. By his estimate the hyperscalers will understate depreciation by about $176 billion across 2026 to 2028.
The defense is real and worth stating. A chip too slow for frontier training is perfectly good for inference. And physical life genuinely does run past six years. The industry calls this the value cascade, and it is not a fiction.
But Nvidia now ships a new generation every year. Economic obsolescence for the hardest work arrives long before the silicon stops functioning.
If the cascade story is wrong, the loss does not appear as an empty building. It appears as a restatement.
So should we pull back
The question contains two decisions. They are almost always discussed as one, and they point in opposite directions.
Do not pull back on shells, power and interconnect. This is the scarce half. It lasts thirty years. The lead times are long. Easing off now produces a shortage in 2029, not a saving in 2027. Capital spending is heading from about $785 billion this year toward a trillion next year. Most of what that buys on the physical side is the part least at risk.
Do question the pace of silicon. This is the half with the one year cycle, the contested depreciation schedule and no scarcity behind it. Buying three years of chips in advance is a wager that frontier models will not get more efficient. Getting more efficient is the single most reliable thing they do.
And build the shells for 600 kilowatts. Even while installing 130. Retrofit costs $50,000 to $100,000 a rack, and it tops out below where the roadmap already sits. The cheap moment to buy that headroom is while the slab is still being poured.
That last one is the recommendation this framework actually generates. It is unglamorous and it is the difference between a thirty year asset and a fifteen year one.
What would prove this wrong
Three markers, all public.
If vacancy crosses 5 percent, the absorption story has broken. Then the overbuilding worry becomes the correct one. One point four is not close.
If preleasing on new starts falls below 60 percent, builders are working on hope rather than signed tenants. That is the earliest honest warning available.
And if any hyperscaler shortens a depreciation schedule, take it seriously. Nobody does that voluntarily. It would be a confession that the cascade does not work, and it would arrive before the write-down.
Two cautions. The vacancy and preleasing figures are a demand fact about today, not a forecast. The whole case rests on that demand holding. The fragile number remains the one from the earlier dispatch: enormous capital spending against inference that sells for about eleven cents. And the 2027 rack specification is a vendor roadmap, not a shipped product. Treat 600 as a direction rather than a measurement.