Bloomberg Businessweek Daily: Oracle's Force Majeure (Podcast)

Oracle has issued a force majeure notice to the Blue Owl Capital unit developing Project Jupiter, a major New Mexico data center, seeking to defer payments if construction delays prevent the facility from opening as planned in 2028. The move does not indicate Oracle is exiting its role as anchor tenant, but it highlights escalating regulatory and opposition-related execution risks for the project. Delays could affect Oracle's planned data-center capacity expansion and create financial pressure for the developer.

Analysis

The key equity issue is not a single-site delay but whether Oracle’s AI-cloud capacity plan is becoming less synchronized with contracted customer demand and third-party financed construction. A payment deferral preserves Oracle’s downside optionality, but it also signals that committed capacity may be less firm than investors assume; repeated use across projects would raise the perceived execution discount on OCI growth, capex efficiency and the durability of backlog conversion. For ORCL, the near-term multiple risk is greater than the direct P&L impact because the stock’s AI premium depends on credible, on-time infrastructure delivery.

Blue Owl’s risk is likely concentrated in fee-related earnings only if its sponsored vehicles have meaningful construction exposure, unreimbursed carrying costs, or impaired fundraising capacity from delayed asset activation. The more important second-order effect is for the private-credit/data-center financing complex: developers may demand stronger parent guarantees, larger deposits and tighter completion protections from hyperscale tenants, increasing project funding costs and reducing levered equity returns. That favors scaled operators with balance-sheet-funded builds, including MSFT and GOOGL, relative to Oracle’s more asset-light, partner-financed expansion model.

Over the next 1-3 months, watch Oracle disclosures on remaining performance obligations, OCI growth guidance, capital commitments and any change in the timing of capacity additions. The bearish interpretation is falsified if Oracle reiterates OCI growth while demonstrating substitute capacity elsewhere, or if Project Jupiter reaches key permitting/construction milestones without incremental tenant concessions. Structurally, a broader slowdown in AI training demand would turn contractual flexibility from a prudent hedge into evidence that the industry overbuilt; conversely, persistent GPU scarcity would make the delay a lost-revenue problem rather than a cost-control win.

Key Decisions for Investors

• Reduce ORCL overweight into the next earnings event; use a 1-3 month long MSFT / short ORCL relative-value position rather than an outright Oracle short. The trade targets a widening valuation gap if Oracle must defer OCI revenue or raise capex, while risk is a rapid Oracle capacity substitution or a new large OCI contract.
• Do not initiate an outright OWL short without vehicle-level exposure data. Set an alert for disclosures showing material fee-earning AUM tied to the project, impairment/reserve language, or lower infrastructure fundraising; those would support a 3-6 month underweight versus alternative-asset peers KKR and APO.
• Buy limited-risk ORCL downside only if implied volatility remains below the post-earnings move range: 3-6 month put spreads can express execution risk while capping loss if AI demand or alternative sites offset the disruption. Exit if OCI guidance is maintained or raised and disclosed capacity timelines remain unchanged.
• Monitor private data-center developers and lenders for stricter tenant-credit provisions. A visible increase in required deposits, parent guarantees or construction spreads would validate a 6-18 month shift toward balance-sheet-rich hyperscalers and away from externally financed capacity models.