Oracle's Project Jupiter Force Majeure Notice Tests AI Data

Oracle has moved to shield itself from rent obligations at Project Jupiter, the 2.45-gigawatt AI data center campus under construction in Doña Ana County, New Mexico. The Project Jupiter force majeure notice, issued to developer Stack Infrastructure, cites potential delays in securing power for the site. Oracle is not exiting as anchor tenant. It is asking for the right to defer payments if the campus misses its planned 2028 in-service date, and it says construction remains on schedule.

Stack Infrastructure is a unit of Blue Owl Capital, the asset manager that financed much of the build. Blue Owl has stated that the notice does not change its financial commitments to the multi-year project. Oracle describes force-majeure notices as routine on developments of this size, where partners use them to preserve contractual rights rather than to unwind agreements.

The notice is a test of how the AI buildout prices power risk. It shows where the risk lands when the electricity behind a signed lease runs late: on the landlord's cash flow and on the debt secured against it.

What Oracle Is Actually Asking For

The notice is a cash-flow instrument rather than an exit. Oracle pays a reduced development-stage rent while the campus is under construction and steps up to a higher rate once the facility is operational. Triggering force majeure extends the lower-rent period. Blue Owl still receives the higher rent for the duration originally agreed, but the start of that higher-rent window moves later.

Oracle has not cancelled capacity, trimmed its commitment or tried to hand the site to another tenant. It has preserved the option to withhold full payment for a facility that cannot be energised. The notice cites potential delays in securing power, while Oracle says construction remains on schedule and the campus is still targeted for a 2028 in-service date.

The timing of the Project Jupiter force majeure notice carries its own logic. A claim filed while the schedule is still formally intact is cheaper and cleaner than one filed after the target date passes, because it fixes the contractual record in advance. If the power supply slips further, Oracle has already served notice; if it does not, the notice lapses with little cost beyond the paperwork.

Dimension	Position before the notice	Position after the notice
Rent stage	Full rent begins at 2028 in-service	Development-stage rent extended; full rent starts later
Total rent paid	Full rate for the planned duration	Unchanged; the start date moves
Oracle's lease	Anchor tenant commitment	Retained; no exit sought
Blue Owl's commitment	Multi-year financing in place	Stated as unchanged

Those two positions are compatible. Oracle keeps its lease and its capacity pipeline; Blue Owl keeps its tenant and its long-run rent. What changes is the timing of cash flows across the contracts underneath them.

Power Is the Binding Constraint

For most of the past decade the constraint on data center construction was land, chips or capital. A campus sized at 2.45 gigawatts draws more power than many mid-sized cities, and the scarce commodity is a firm interconnection agreement with a delivery date that holds. The notice points at that bottleneck: the buildings are going up, while the electricity supply behind them is not yet locked to the schedule the lease assumes.

That distinction matters because the two kinds of delay behave differently. A late semiconductor shipment can be expedited with money. A late transmission upgrade or generation contract generally cannot, because the timeline is set by permitting, equipment lead times and grid operators rather than by the developer's balance sheet.

Project Jupiter sits in the southern New Mexico corridor near El Paso, where large industrial loads are close to existing transmission and land is cheaper than in established hubs such as northern Virginia. The same geography that makes the site attractive also makes the power timeline harder to compress. New generation, substations and grid upgrades have to clear regional planning and equipment procurement before a single server racks, and those steps sit largely outside the developer's control.

The campus supports OpenAI's training and inference capacity as part of the Stargate buildout. That link sharpens the schedule risk, because compute commitments made to model developers carry dates, and slippage at one site has to be absorbed somewhere else in the portfolio or renegotiated.

What the Clause Does, and Where It Stops

Force majeure clauses excuse a party from performance when events beyond its control make delivery impossible, and they are standard in energy and commodity contracts for that reason. Oracle's use of the mechanism is narrower than a full excusal: the lease survives, the tenant survives, and only the payment schedule moves.

The unresolved question is whether a power procurement delay counts as unforeseen on a project that was underwritten on the assumption that power would be arranged. That is the point a court or arbitrator would test if the two sides ever litigated, and neither has signalled that path. Both have instead described the notice as an ordinary precaution between partners, which keeps the dispute inside the contract rather than in front of a judge.

Who Bears the Risk

The market reaction was immediate. Oracle shares fell about 3% on the news, and debt tied to the project has traded below 90 cents on the dollar, a level that indicates investors are pricing execution risk rather than treating the paper as a utility-like obligation.

That repricing is the substantive story for anyone funding AI infrastructure. The build-to-suit model behind this cycle rests on one premise: a creditworthy tenant signs a long lease, and lenders underwrite the lease rather than the technology. Force majeure clauses are the seam in that premise. They exist in energy and commodity contracts precisely because physical delivery can fail, and their use here shows where the model can leak.

Blue Owl's exposure sits in the gap between the two rent stages. Its returns depend on the campus reaching full rent on schedule, and every month spent in the development stage is a month of lower cash flow against the same debt service. Its statement that financial commitments are unchanged addresses the financing side of the project; the rent-timing question sits on the other side of the same contract.

The trade-off is uneven. Oracle gains optionality at low cost. The notice preserves rights, costs little if the project lands on time, and protects a large payment stream if it does not. Blue Owl carries schedule risk on a campus whose economics were underwritten against a 2028 start.

Oracle's dual role complicates the picture. It is the tenant paying rent on Project Jupiter and at the same time the vendor selling AI capacity to customers including OpenAI. A delayed campus therefore hits both sides of its ledger: costs continue accruing while the revenue that the capacity was meant to generate arrives later. That alignment of interests explains why the company would rather stretch the rent schedule than walk away from a site it still needs.

For lenders and investors holding similar paper across the AI buildout, the practical question is whether their own force majeure language is as flexible, and whether the power behind their campuses has a delivery date that survives the interconnection queue. The next checkpoint is whether the Project Jupiter force majeure notice is followed by a formal reset of the 2028 in-service target and a power contract with a firm energisation date.

Why this matters

Oracle's notice turns a construction story into a contract story. The AI buildout has been underwritten on the assumption that demand is the scarce input and that a signed lease converts cleanly into a payment stream. Project Jupiter shows that the electricity behind those leases carries a schedule of its own. For decision-makers allocating capital to AI infrastructure, power procurement now deserves the same scrutiny as the tenant's credit, because it sets the date on which the rent, and the return, actually begins.

Photo by BoliviaInteligente on Unsplash

✔Human Verified

Researched and cross-referenced against primary sources by the Bytevyte editorial team. This article was generated with the assistance of artificial intelligence and reviewed by the Bytevyte editorial team.