A Month of Writing About "Time to Delivery," and Here Is the First Hard Case
This site has written the same structure repeatedly this month: the headline number in AI infrastructure announcements is total contracted value, and the horizon for realizing it runs far longer than the news cycle. On September 9, Nscale's contracted backlog rose from about $51 billion to $103 billion in a month. On September 17, Anthropic signed roughly $517 billion in compute contracts over eleven months. On September 20, Crusoe's $140 billion of contracted value stood against 1 gigawatt delivered. On September 23, Alibaba announced data center capacity above 20 gigawatts by 2032. Each time the judgment was that realizing those numbers depends on power and construction schedules. Today's story turns that sentence into a case, and supplies the failure mode: **it is not that demand fell short, it is that the power cannot be connected.** How specific is the bottleneck? A natural gas pipeline that was supposed to enter service this month was delayed nearly six months to February 1, 2027, after repeated permit denials from the state land office. The campus is designed to run on gas-powered fuel cells, so a late pipeline puts the 2028 launch at risk. **This is what numbers like "20 gigawatts" and "500,000 accelerators" actually collide with — not chip supply, but pipeline permits.** In any long-range AI infrastructure plan, the most fragile link is usually not on the technology side.
Both Parties Say It Is Fine, and Three Prices Fell at Once
Oracle says Project Jupiter remains on its planned schedule and that it is fully committed to New Mexico. Blue Owl says the notice does not change the financial commitments to this multiyear project and that the parties remain fully aligned. The same day: Oracle down 3.47%, Blue Owl down 3.6%, and the $18 billion of loans tied to that data center quoted at 89 to 91 cents on the dollar. **When both sides of a transaction say nothing is wrong and three prices move down together, look at the prices.** The loan quote especially — it corresponds to this one project far more directly than the share price does, since a stock also carries expectations about every other line of business, while a bond quote reflects little beyond whether that debt gets repaid on schedule. Eighty-nine to 91 cents implies the market sees real timing or recovery risk, though it is nowhere near distressed pricing. A distinction to keep clear: **"on schedule" and "we filed a force majeure notice" can both be true at once.** The first is a judgment about current progress; the second pre-positions a legal stance for a possible future deviation. Filing the notice does not mean the project is failing — but it does mean someone decided insurance was worth taking out early.
Force Majeure Here Is a Reallocation of Responsibility
The key to reading this is knowing that securing power is Oracle's responsibility under the contract. Which means that, normally, the consequences of power not arriving fall on Oracle. Invoking force majeure attempts to reclassify "we could not get power" from "our breach" to "an external event attributable to neither party," and thereby defer rent. And even if accepted, what Oracle gains is **a three-year delay on rent once payments commence** — it still pays other costs in the interim and still owes rent across the full lease term. **So this does not save money; it moves time.** Which is exactly what says what Oracle is worried about: if the campus cannot come online in 2028, it does not want to start paying rent on a building it cannot use. A company negotiating specifically for a three-year buffer on "asset available on schedule" tells you more about its internal read of the timeline than any progress statement does.
What This Means in Practice
This story is useful to three different readers. **Anyone assessing AI compute supply:** keeping "contracted capacity" and "energized capacity" as separate line items now has a concrete justification. A 2.45-gigawatt campus held up by one pipeline is a risk that appears in no compute roadmap. **Anyone doing long-term procurement:** if your contract is tied to delivery at a specific campus, it is worth establishing which party owns power interconnection and how delay consequences are allocated. That single point is the entirety of the dispute here. **Anyone tracking Stargate:** New Mexico is one of five sites, and there is no comparable reporting on the rest of the $400 billion agreement. So what can be said today is that one site has timing risk; that cannot be generalized to the program. Finally, the boundaries: it is not certain the maneuver frees Oracle from obligations it already agreed to, and neither party has publicly said they agree a force majeure event occurred. The reporting comes from Bloomberg citing people familiar with the matter.
via: CNBC, Data Center Dynamics, The Santa Fe New Mexican, Bloomberg via Yahoo Finance