Oracle could reportedly owe payments on AI data-centre capacity even when delayed electricity connections prevent the sites from operating, shifting a hidden infrastructure risk onto the cloud company.

The Financial Times reported on 25 September that contracts supporting Oracle’s rapid data-centre expansion can require payments to investors even if power is not available on schedule. The report focuses on the divide between financing and physical delivery: buildings and leases can become binding before utilities or on-site generation can provide the electricity needed for computing.

The underlying contracts were not public during this review. Their payment triggers, exceptions and remedies therefore cannot be verified from a primary filing. The specific obligation should be read as an FT-reported claim, not as a settled description of every Oracle data-centre agreement.

Why it matters

AI infrastructure is often described in chips and construction budgets, but power availability can determine whether the investment produces revenue. A completed building without an energized connection cannot run accelerators. If rent, debt service or investor payments start before electricity arrives, the operator bears a mismatch between fixed cash outflows and usable capacity.

That risk grows with scale. Large AI campuses may require generation and transmission comparable with a small city. Grid studies, environmental reviews, gas supply, generation equipment and high-voltage connections proceed on different schedules. A delay in any one can leave expensive servers idle or force a project to rely on temporary generation.

Oracle has publicly described Project Jupiter in New Mexico as separate from its planned microgrid and has said construction can continue while power arrangements are reviewed. In earlier company statements, it said Oracle—not local ratepayers—would pay the project’s power costs and described a revised plan centred on fuel cells. Those statements verify Oracle’s public position on the project, but they do not disclose the lease clauses described by the FT.

Contracts decide who waits and who pays

Infrastructure agreements can allocate delay risk in several ways. Rent might begin when a building is delivered, when power becomes available, or when computing service starts. A force-majeure clause may suspend obligations for events outside a party’s control, but the result depends on whether securing power was assigned to that party and whether the event was foreseeable.

Investors prefer predictable payments because data centres require large upfront financing. Cloud providers prefer flexibility when grid schedules move. Customers want capacity on a promised date. The final allocation affects financing costs: whoever accepts uncertainty will price it into rent, debt, guarantees or service charges.

The FT’s report points to a broader constraint on the AI build-out. Capital can fund land, buildings and accelerators faster than utilities can add firm power. Announced gigawatts should therefore not be treated as operating gigawatts. Useful reporting needs separate dates for financing, construction, electrical interconnection, equipment installation and customer service.

There are several possible outcomes when power slips. Oracle could negotiate new milestones, use temporary or on-site generation, move workloads to other regions, or pay for capacity that remains idle. Which outcome applies depends on the contracts and permits, not on a general statement that a campus remains under construction.

The next evidence to watch is primary documentation: lease extracts, financing disclosures, utility interconnection agreements or a company filing quantifying exposure. Oracle’s response to the reported clauses would also clarify whether the payments are unconditional, limited to a specific project or protected by exceptions. Until then, the story identifies a plausible financial risk whose size and mechanics remain unverified.

Verification

  1. UNVERIFIED FROM PRIMARY CONTRACTS — The FT reports that some Oracle-backed data-centre agreements require payments despite missing electricity. Via: https://www.ft.com/content/a96bf05a-a299-4d6a-a753-b298dd0f4016
  2. VERIFIED AS ORACLE’S POSITION — Oracle says Project Jupiter construction and its microgrid permitting are separate processes. Primary source: https://www.oracle.com/news/announcement/project-jupiter-statement-on-construction-permitting-2026-09-14/
  3. VERIFIED AS ORACLE’S POSITION — Oracle says it will pay the project’s power costs and has revised the power plan. Primary source: https://www.oracle.com/news/announcement/blog/weve-overhauled-project-jupiters-power-plan-2026-07-01/
  4. ANALYSIS — The explanation of financing, interconnection and delay-risk allocation is general infrastructure analysis.

Glossary candidates

  • Interconnection: The process of connecting a facility to an electrical grid.
  • Force majeure: A contract clause addressing extraordinary events that prevent performance.
  • Firm power: Electricity expected to be available reliably when needed.

Cold-reader sentence: Oracle’s AI expansion may expose it to payments before power arrives, but the decisive contract terms are not public.