Oracle Project Lighthouse: power risk between bookings and revenue
An external analyst flags delivery risk following a restarted transmission review. That assessment is distinct from an official revision to Oracle’s delivery schedule.
A. Key facts
Aterio flags risk to Oracle’s second-half 2027 delivery target after the Wisconsin transmission review restarted. The analysis was released on September 30 and covers filings through September 24.
B. Business significance · InveDeck interpretation
Bookings do not produce computing services without electricity. The key risk is a longer gap between upfront investment and cash generation.
C. Quantifiable impact
Aterio’s base-case estimate (E) puts partial power in December 2027 and full 1.3 GW in October 2028. These are not commitments. Total campus power and approximately 900 MW of IT load are different measures. Delayed revenue or FCF was not quantified.
D. Link to earnings and expectations
The analysis is not an announced earnings-guidance cut. If contracts remain intact, revenue conversion timing may change before total RPO does. Pre-operation costs and financing requirements also warrant attention.
E. Industry and supply chain · InveDeck interpretation
GPU, server and memory installation schedules could be affected, but no order cancellation was established. The need for grid investment should be distinguished from near-term computing-capacity delivery risk.
F. What to watch next
- PSC application-completeness findings and subsequent approvals
- Actual power availability and commissioning dates
- Changes to Oracle delivery targets, revenue recognition or investment plans
Sources and verification scope
- Aterio · Business Wire · 2026-09-30
Aterio’s review of regulatory filings and scenario release. Its estimates are not commitments by Oracle or regulators.
- TechRadar · 2026-10-04
Follow-up coverage citing Aterio. It is not treated as independent confirmation of an additional delay.
Reported facts are separated from InveDeck interpretation. Read the original reporting through the source links.
Revision history (2)
- 11/10/2026, 12:06 KST · Revision 1 — Initial publication after rechecking the shared Watch analysis against its sources.
- 11/10/2026, 22:32 KST · Revision 2 — Corrected one Korean character-encoding error found during cumulative HTML verification. Facts, figures and conclusions are unchanged.