Oracle invoked force majeure at Project Jupiter—but cannot hand the financing risk back

Oracle has invoked force majeure while seeking to delay the start of lease payments on Project Jupiter, the New Mexico data centre tied to its OpenAI capacity commitments. State officials have repeatedly denied permits for the gas pipeline intended to power the site, pushing the project at least six months behind schedule.

The notice does not make the obligation disappear. Banks have lent about $18bn to the project and Blue Owl supplied roughly $3bn of equity. Oracle can defer rent while the site is unavailable, according to the Financial Times and Semafor, but must cover carrying costs that are only slightly lower. Delaying the lease also extends its end date, preserving a longer stream of payments for the asset owners. The company remains responsible even if the building has no electricity.

That detail turns an infrastructure delay into a lesson about the AI capital stack. A special-purpose vehicle owns the site; lenders rely on a tenant contract; equity absorbs an initial layer of loss; permits and utility infrastructure determine whether the asset can operate. Each document may allocate risk precisely, yet the complete structure still depends on construction milestones arriving in the right order. Oracle now carries about $288bn of lease obligations, six times its level at the start of 2025.

Force majeure is normally associated with extraordinary outside events. Here the obstacle—securing fuel and local approval for a power-hungry data centre—looks close to the project’s core development risk. If contracts routinely treat permitting failure as exceptional, investors may discover that apparently contracted AI revenue contains more timing and political risk than its headline value suggests.