
Share
A contractual boilerplate clause just became a market signal. Oracle's move to protect itself on a delayed New Mexico data center exposes how little bond investors understand the risks buried in AI infrastructure financing.
Oracle sent a force majeure notice this week to Blue Owl unit Stack Infrastructure, the developer building Project Jupiter, a massive New Mexico data center campus meant to supply computing power to OpenAI. The notice itself is not an admission of failure. But it is a signal that the company sees enough risk in the project's timeline to formally protect itself from the financial consequences of delay.
That signal spooked the market. Oracle shares closed down 3.5% Thursday, paring steeper morning losses. Blue Owl finished down 3.6%. For two companies central to the AI buildout story, that is not a rounding error.
Why it matters extends well beyond one data center. Investors are already questioning the foundations of the AI economy, and this episode adds a concrete data point to those doubts. A force majeure clause exists to relieve a party from contractual obligations when forces outside its control prevent performance. Historically, that has meant hurricanes, wars, or other catastrophic disruptions. What's unusual here is the suggestion that regulatory friction and public opposition could now trigger the same protections.
New Mexico's top land official rejected a gas pipeline in July that was meant to supply on-site fuel cells for the Jupiter campus. That regulatory setback could contribute to a delay stretching years, according to prior Axios reporting. William Blair analyst Sebastien Naji connected the dots directly in a research note Thursday: by asserting force majeure now, Oracle "positions itself to defer payments on capacity it cannot yet energize, should the campus fail to come online in 2028 as planned."
Oracle is pushing back on that framing. VP Michael Egbert said in a statement that "Project Jupiter remains on our planned schedule. We are committed to New Mexico and confident in our path forward." He characterized the notice as routine. "Force-majeure notices are commonplace in developments of this scale and are often used to preserve contractual rights among project partners. They do not, by themselves, establish a project delay or change delivery expectations," he said.
Blue Owl offered a similarly measured response. A spokesperson said the firm remains "fully aligned" with Oracle on the development and that the notice "does not change the financial commitments to this multiyear project." Naji, for his part, thinks the near-term hit to Oracle is limited. Still, he flagged the broader issue investors will keep circling back to: concern that data center delays could push out revenue recognition, a factor that "will continue to be a focal point as investors gauge the company's ability to deliver" on promised compute capacity.
Force majeure clauses are unremarkable in project finance circles. Developers and lenders in infrastructure deals have used them for decades to allocate risk when the unexpected happens. What's changed is who's now exposed to that risk. The AI borrowing binge has pulled in a different class of investor, one more accustomed to lending against staid, investment-grade corporate balance sheets than parsing project-level construction contracts.

Johnathan Owen, a portfolio manager at TwentyFour Asset Management who covers investment grade debt, put it plainly: many of these lending desks are not used to this kind of contractual architecture. "I'm sure a lot of these desks are aggressively going through these docs to find out what risks they're actually exposed to," he said.
That scramble matters. Quinn Emanuel Urquhart & Sullivan attorneys, in a recent client alert, described force majeure provisions in AI data center contracts as no longer "back-end boilerplate." Instead, they called it "a core litigation and risk-allocation tool that can determine whether a delay remains isolated, or cascades through the project's construction, customer, power, insurance, and financing documents." That's a meaningful shift in how these clauses function. They are no longer a legal footnote. They are a mechanism that can determine who absorbs the cost when a multibillion-dollar campus doesn't come online on schedule.
Public opposition to data center construction has been stiffening for months, driven by concerns over power consumption, water use, and local infrastructure strain. If regulatory pushback becomes a recognized trigger for force majeure protections, that opens a new category of risk for every lender and equity holder tied to the AI infrastructure buildout. Nvidia CEO Jensen Huang has dismissed fears around circular financing arrangements in this space, but this episode suggests the risks are broader than financing structure alone. Timeline risk, regulatory risk, and community opposition are now squarely in the mix.
The near-term financial exposure for Oracle appears contained, according to Naji's assessment, and both companies insist the 2028 completion target still holds. That's the official line, and there's no evidence yet to directly contradict it.
But the market reaction tells its own story. A 3.5% single-day drop in Oracle shares on a notice that both parties describe as routine reflects genuine unease about revenue timing tied to AI infrastructure commitments. Watch for whether other data center developers and their corporate tenants start invoking similar protections. Watch for how bond desks price risk once they've finished combing through project finance documents that weren't designed with retail-facing investment products in mind.
The bigger question is whether force majeure becomes a recurring tool in AI infrastructure contracts rather than a one-off event tied to New Mexico's specific pipeline dispute. If regulatory and permitting delays become a standard trigger across the sector, that reshapes how investors should model revenue recognition timelines for every company claiming AI-driven compute capacity growth. Given how much capital has flowed into this buildout on the assumption of predictable delivery schedules, that reshaping would carry consequences well beyond Oracle and Blue Owl.
Tags
Original Sources
Oracle moves to shield itself from AI buildout risks
↗ https://www.axios.com/2026/09/24/oracle-force-majeure-blue-owl-openai
About the author
Marcus began tracking AI's market implications in 2016, noticing AI-related patent filings accelerating ahead of earnings upgrades before most of the sell-side had caught on. A former fixed-income quantitative analyst, he spent two decades building models that priced risk across emerging markets before pivoting to cover the economic impact of AI full-time. His writing translates opaque technical developments into clear risk/reward terms — and he's rarely diplomatic about the gap between AI valuations and underlying fundamentals. He believes most market participants still underestimate AI's long-run deflationary effect on knowledge work.
More from The Analyst →This Week's Edition
25 September 2026
31 articles
Related Articles

Eli Lilly Deepens China Bet With $100 Million InnoCare Drug Discovery Deal
Finance & Markets · 5 min

AI Buildout's $10 Trillion Price Tag Is Starting to Look Like a Financial Stability Problem
Finance & Markets · 5 min

Island Raises $400 Million at $6.4 Billion Valuation as AI Agent Risk Fuels Security Spending
Finance & Markets · 5 min
Related Articles

Eli Lilly Deepens China Bet With $100 Million InnoCare Drug Discovery Deal
Finance & Markets · 5 min

AI Buildout's $10 Trillion Price Tag Is Starting to Look Like a Financial Stability Problem
Finance & Markets · 5 min

Island Raises $400 Million at $6.4 Billion Valuation as AI Agent Risk Fuels Security Spending
Finance & Markets · 5 min
More Stories
© 2026 Cedar & Bloom. All rights reserved.