CRITICAL EVENT UPDATE · AI Infrastructure × Power × Project Finance
Oracle Invokes Force Majeure on Project Jupiter as Power Delays Reach AI Contracts and Finance
Critical Event Update | Time-to-Power × Capacity-to-Cash | 25 September 2026
Oracle issued a force-majeure notice concerning Project Jupiter, a major New Mexico data-centre campus developed by Blue Owl's STACK Infrastructure for OpenAI. A source said the project faces a roughly one-year delay in securing power; Oracle says it remains on schedule and Blue Owl says commitments are unchanged. Power and permitting risk is now moving directly into contracts, returns and financing.
Delay described by a source
Reported bank-loan package
Blue Owl equity invested
Original in-service year
Power bottleneck reaches contracts | Project returns delayed | AI demand not overturned
01 · RESEARCH BRIEF
The one-minute brief
Project Jupiter is part of the Stargate build-out and reportedly involves about $3 billion of Blue Owl equity and $18 billion of bank loans. Power-pipeline delays and water and air-permit challenges have made the delivery and payment timetable contentious.[1][2] Demand remains intact, but time-to-power is determining when capital starts producing revenue and who absorbs delay costs.
Audio transcript
Oracle's force-majeure notice on Project Jupiter shows that power and permitting risk has reached AI contracts, returns and financing. Demand remains, but energisation now determines who can turn capacity into cash.
Known facts and open questions
- Confirmed
- Oracle issued a force-majeure notice
- Confirmed
- Blue Owl says financial commitments are unchanged
- Disputed
- Source cites a one-year delay; Oracle says on schedule
- To validate
- Final power, permitting and payment effects
Power
Pipeline and interconnection delays
Project
Capacity misses intended service date
Contract
Force majeure reallocates payment timing
Finance
Development returns slip and new funding tightens
02 · THESIS → EVIDENCE → UPDATE
What changed in the thesis?
AI infrastructure execution quality
- Prior thesis
- AI demand was strong, but power and permits could delay capacity conversion.
- New evidence
- Oracle issued a force-majeure notice on Project Jupiter and a source described a one-year power delay with spillovers into other funding discussions.
- Updated view
- Time-to-power has become a contract and credit variable. Capacity-to-cash, risk allocation and payment terms now belong ahead of headline capex.
03 · EVIDENCE & ANALYSIS
Evidence and analysis
01｜What Happened
Oracle issued a force-majeure notice regarding Project Jupiter, the New Mexico data-centre campus being developed by Blue Owl's STACK Infrastructure. A source said power delays could push the programme back by about a year. Oracle says the project remains on schedule; Blue Owl says commitments and financial obligations are unchanged.[1][2]
02｜Why It Matters Now
The campus supports OpenAI and carries large equity and bank financing. A delay changes more than construction sequencing: it can move rent, interest, development returns and refinancing. The key AI-industrialisation question is shifting from demand to when capacity becomes powered and cash-generative.
03｜Confirmed Facts vs Uncertainty
The force-majeure notice, project scale and Blue Owl response are reported. The one-year delay comes from a source and conflicts with Oracle's public position. Power responsibility, lease-payment timing, final service date and permit-litigation effects remain incompletely disclosed.
04｜Transmission Mechanism
Power and permit delays → capacity cannot enter service → customer payments and developer returns slip → debt interest continues to accrue → equity returns fall → lenders tighten pricing and protections → other AI-campus funding and construction schedules are affected.
05｜Prior View → New Evidence → Updated View
The prior view was that AI construction faced power, permitting and funding constraints. The new evidence puts those constraints inside force-majeure, lease and project-loan structures. Execution quality is now central to AI credit analysis.
06｜Cross-Asset / Cross-Industry Read-through
Oracle faces capacity-conversion and contract-execution risk; Blue Owl and lenders face a longer development period; OpenAI may receive compute later; utilities, gas pipelines, grid equipment and permitting expertise gain strategic value; lenders may demand stronger power proof and completion protection on new projects.
07｜What Does NOT Change
The event does not prove weaker OpenAI demand or cancellation of Project Jupiter. Oracle says the project is on schedule and Blue Owl says financial commitments remain. The site was not expected to contribute Oracle revenue in fiscal 2027, limiting immediate revenue effects.
08｜Risks / Alternative Scenarios
Base: the project is delayed but completed. Relief: power and permits resolve quickly with no material payment change. Downside: delay expands and requires more interest, equity or contract dispute. Tail: similar failures across campuses trigger broad AI project-finance repricing.
09｜Next Validation
24H: additional Oracle, Blue Owl or OpenAI statements. 7D: power pipeline, permit litigation and loan terms. 30D: construction milestones, payment arrangements, other data-centre spreads and project delays.
10｜Current Evidence State
The force-majeure notice and power dispute are confirmed; the one-year delay and financial impact are not jointly confirmed. Evidence supports execution risk entering contracts and finance, not project cancellation or an AI-demand reversal.
11｜Our View
This is a real-world test of the AI Industrialisation Stack: compute demand exists, but power, grid, permits and finance must close together. Project assessment should prioritise secured power, interconnection, risk allocation, completion protection and capacity-to-cash over headline gigawatts and contract value.
04 · INVESTMENT IMPLICATIONS
Industry and asset implications
AI project finance
Pricing and completion protections may tighten.
Data centres
Time-to-power becomes a valuation and credit variable.
Power and grid
Supply availability determines order conversion.
Oracle / OpenAI
Demand holds, but delivery timing is tested.
Demand can remain strong while power delays push revenue, returns and cash flow to the right.
05 · VALIDATION & RISKS
What to verify next
Next 24 hours
Parties confirm schedule or payment changes
Failure signal: Oracle demonstrates on-time progress
Next 7 days
Power or permit delays persist
Failure signal: Key obstacles clear
Next 30 days
Other projects face higher funding costs
Failure signal: Funding and construction remain stable
What would change our view?
The main misread is treating an engineering and contract delay as an AI-demand collapse. Current evidence supports tighter execution constraints, not a demand reversal.
06 · FAQ
Key questions
Has Project Jupiter been cancelled?
No. Public evidence concerns schedule and payment risk; Blue Owl says commitments are unchanged.
Why does a power delay affect finance?
Unpowered capacity cannot generate rent or service revenue while interest and development costs continue.
Will this affect other AI projects?
It may tighten loan conditions and risk premia, but broad repricing still needs confirmation.
07 · TERMS & SOURCES
Terms, sources and related research
Key terms
- Force majeure
- A contractual mechanism for extraordinary obstacles beyond a party's control.
- Time-to-power
- Time from development to stable energisation and operations.
- Capacity-to-cash
- Conversion of planned capacity into revenue and cash flow.
[1] Reuters｜Oracle–Blue Owl project delay sends ripples through AI financing ↗
[2] Reuters｜Oracle cites force majeure over Project Jupiter ↗
This report separates the confirmed force-majeure notice and company responses from the disputed delay length and unconfirmed financial consequences.