Morgan Stanley: Oracle's Force Majeure Notice Rattles Data Center Debt Market
nashnova research
Oracle issued a force majeure notice on its New Mexico data-center project, sending data-center bond spreads sharply wider and prompting Morgan Stanley to warn that the move could trigger a broad reassessment of contract protections across the AI infrastructure financing chain.
What exactly did Oracle do?
Oracle issued a force majeure notice on "Project Jupiter," a data-center build in New Mexico — invoking the contract clause that lets a party suspend or exit obligations due to extraordinary circumstances.
The notice came well before the planned delivery date. Morgan Stanley calls this an "escalation."
This means → the market's concern goes beyond one project. The question is whether Oracle is signaling a harder stance on lease commitments — and on compute contracts — whenever pressure arises.
How hard did debt markets react?
After the notice, data-center bond spreads — the gap between bond yields and benchmark rates, wider = more default fear — blew out on Thursday.
The cost of five-year CDS protection on Oracle — essentially an insurance policy against Oracle failing to pay — hit an all-time high. In plain terms = the market has never been this nervous about Oracle's credit.
Morgan Stanley sees the impact as uneven: deals with higher construction risk and weaker tenants face the worst hit; assets near stabilized operations are better insulated.
Why is the "precedent effect" the biggest open question?
Morgan Stanley flags one question above all others: will other tenants cite this dispute as a precedent?
This means → if another high-quality hyperscaler — a Microsoft Azure or Amazon AWS — takes a similar step, the fallout would dwarf a single-project dispute and force a rethink of contract frameworks industry-wide.
Much of the construction financing in this space is backed by long-term leases from investment-grade tenants. If the market concludes that force majeure can break a lease, the logic underpinning that collateral is shaken.
How does Oracle's own credit look?
Morgan Stanley explicitly says it does not believe Oracle is trying to dodge debt obligations — but remains cautious on Oracle as an issuer.
The reasons are straightforward: ongoing cash burn, elevated adjusted leverage, and downgrade risk — S&P and Moody's cut Oracle's rating in July to one notch above junk.
A syndicate of roughly 20 banks provided $18 billion in construction financing for Project Jupiter. The loans are now sitting on over $2 billion in paper losses and cannot be transferred to third parties. In plain terms = the banks' money is locked in with no exit.
What does this mean for AI infrastructure financing?
The AI data-center financing market was already under strain: rising borrowing costs, supply pressure pushing up risk premiums, and growing local opposition to data centers across the U.S.
Oracle's force majeure notice adds contractual uncertainty on top of all that. This reflects a deeper issue — the AI buildout's financing chain faces not just a "cost of capital" problem but a "can you trust the contract?" problem.
Morgan Stanley highlights a structural blind spot: the prevalence of bank and private-credit financing means investors have "limited visibility" into the contract terms backing AI builds. This means → how much similar risk exposure exists across the market is largely opaque to outsiders.
市场有风险，内容仅供研究参考，不构成投资建议。