Oracle FY2026 operating cash flow (TTM)
$31.98B
Net cash provided by operating activities (TTM snapshot)
Oracle recent financing posture
Debt + equity
ATM program up to $20B; issued $25B+ notes; Series D mandatory convertible preferred closed Feb 2026
What happened (and what we can prove)
Oracle’s AI buildout is turning capex from a multi-year plan into a near-term cash-and-credit stress test
Multiple outlets reported that Oracle is dealing with multi-billion-dollar cost overruns across its $165B AI data-center buildout, including the Wisconsin and New Mexico/“Project Jupiter” sites. The key hard confirmation we can anchor in filings: Oracle capex jumped to $55.7B in fiscal 2026 (ended May 31, 2026) — from $21.2B in fiscal 2025 — which is the financial signature of “overrun-like” execution risk even before we debate the exact “$165B campus” project-accounting.
| Metric | FY2025 | FY2026 |
|---|---|---|
| Oracle capital expenditures | $21.2B | $55.7B |
- SEC-filed FY2026 capex: $55.7B (up from $21.2B in FY2025), aligning with reports of overruns rather than “on-budget” expansion.
- The operational mechanism is not just higher construction costs — it’s also the financing and long-dated infrastructure commitments that convert power/network delays into capital-at-risk time.
- This matters because cloud infrastructure scale-up behaves like a cycle: early builds absorb cost inflation first; revenue ramp depends on customer consumption and infrastructure readiness.
Load-bearing facts from filings
Oracle is financing the AI buildout like a capital project company: long leases, unconditional purchase obligations, and equity/debt backstops
Beyond headline capex, the most credit-relevant details are the long-dated commitments and capital-markets instruments that sit behind future build and power/network capacity. In Oracle’s FY2026 10-K, the company discloses additional lease commitments and unconditional purchase obligations tied largely to data center arrangements — plus explicit equity and notes activity in early 2026.
What Oracle disclosed in FY2026 10-K (credit-relevant commitments)
Additional lease commitments
$260B
Substantially all related to data center arrangements; expected to commence between FY2027–FY2029 (15–19 years).
Unconditional purchase obligations (as of May 31, 2026)
$13.309B
Primarily data center power; includes $1.841B FY2027, $1.034B FY2028, $1.053B FY2029, etc.
Post–May 31, 2026 additional purchase commitments
$19B
Additional unconditional purchase commitments for cloud infrastructure with a 5-year term starting FY2027.
ATM equity program
$20B
Established Feb 2, 2026; up to $20.0B aggregate sales proceeds; no shares sold as of May 31, 2026 (per filing context captured during extraction).
| Instrument | Timing (2026) | Size / key terms | Purpose (as described) |
|---|---|---|---|
| Oracle | Feb 2026 | ATM common equity up to $20.0B | General corporate purposes / support expansion |
| Oracle | Feb 4–5, 2026 (consummated/closed) | $25B aggregate principal notes + Series D mandatory convertible preferred (100M depositary shares) | Intended for general corporate purposes including capex and repayment/investments |
- Lease and power commitments reduce flexibility: when power/network constraints delay production, Oracle’s cost structure can stay “fixed” longer than expected.
- That’s why credit posture becomes part of the infrastructure story: any slippage in demand ramp forces the company to “bridge” more expensive capital to longer timelines.
- This bridges directly to the reported BBB downgrade narrative: the filings show the company is already in a mode that can be interpreted by rating agencies as higher execution and leverage risk.
Causal chain
How cost overruns can translate into a credit-rating problem (even if revenues later catch up)
Cost overruns don’t only inflate capex totals — they also alter timing. In hyperscaler-like builds, timing is the difference between “spend now, monetize soon” and “spend now, monetize after power capacity is ready.” That timing shift increases leverage and reduces near-term free cash flow, which is exactly what rating models punish.
Oracle free cash flow flipped negative as capex surged into FY2026
Directionally consistent with a spend-heavy build phase (TTM net cash provided by operating activities vs. investing outflows for PPE).
단위: USD
Net cash provided by operating activities (TTM)
31,977,000,000
Investments in property, plant & equipment (TTM, outflow)
Represents cash outflow line item magnitude from cash flow statement extract.
-55,663,000,000
- Mechanism 1 (timing): cost overruns extend buildout schedules; power and network readiness become gating items.
- Mechanism 2 (liquidity): larger capex means more cash absorbed before depreciation and revenue catch up.
- Mechanism 3 (capital markets): to avoid a liquidity squeeze, management leans on debt and equity issuance (ATM + notes + convertible preferred activity in early 2026).
- Net effect: rating agencies can view the combination as higher leverage and weaker debt-service protection during the ramp window.
Local grid constraints as a supply-chain bottleneck
Power is the chokepoint: New Mexico electricity constraints can dominate data-center economics more than GPU procurement
Reports tied New Mexico/Project Jupiter cost overruns to local energy and infrastructure concerns. That fits a broader data-center supply chain reality: GPUs are “component constrained,” but data centers are “system constrained” by interconnection, substations, and utility upgrade lead times.
- If power availability lags, the critical path becomes utility work and interconnection capacity rather than IT procurement.
- That pushes capitalization into longer construction periods and can defer revenue realization (less capacity usable → slower monetization).
- This also increases the probability of regulatory disputes and financial guarantee requirements — because utilities and regulators want ratepayer protection against stranded capacity or delayed repayment.
Downstream impact
If Oracle’s infrastructure ramp slows, customers feel it through service capacity and unit economics — not through headlines
Oracle’s downstream is cloud demand (enterprise + developers) consuming OCI capacity. The risk isn’t only that Oracle spends too much; it’s that capacity monetization per dollar of capex can fall if usable availability ramps slower than expected or at higher cost.
| Signal | What you’d expect if the ramp is healthy | What you’d expect if the ramp is broken |
|---|---|---|
| OCI capacity utilization / workload growth | Steady ramp without large “idle capacity” narratives | Slower consumption growth relative to capex cadence |
| Cash flow conversion | Capex stays high but free cash flow trends back toward less negative | Free cash flow stays deeply negative as capex rises further |
| Cost of financing and leverage | Stable interest coverage as credit improves or remains steady | Higher interest margins / more reliance on equity vs. operating cash generation |
- Downstream customer impact usually shows up as (a) fewer enterprise workloads supported at planned service levels or (b) pricing/unit economics pressure that can be partially offset by AI demand but still compresses margins.
- This matters for supply chain too: higher “cost per deployed capacity” flows upstream as suppliers get paid to meet revised schedules.
Supply-chain mapping (upstream + downstream)
Oracle’s AI megacampus bet ties together upstream power equipment, data-center construction, and downstream cloud workloads
Even without naming every vendor in the filings, the commitments Oracle discloses effectively identify the supply-chain nodes the buildout depends on: data-center power (utility upgrades, grid interconnect equipment) and long-lived cloud infrastructure purchases. Downstream is the cloud consumption layer that turns deployed capacity into recurring revenue.
| Layer | Named linkage to Oracle’s disclosures | Examples of what typically sits in this node |
|---|---|---|
| Upstream: power & grid interconnect | Unconditional purchase obligations primarily for data center power ($13.309B as of May 31, 2026); local electricity constraints linked in reporting | Utility interconnect, substations, switchgear, power delivery engineering, grid upgrade contractors |
| Upstream: data-center construction & long-term hosting arrangements | Large additional lease commitments tied to data center arrangements ($260B; 15–19 years commencing FY2027–FY2029) | Construction/EPC, facility operators, long-term capacity hosting providers |
| Upstream: cloud infrastructure supply (long-term purchases) | Additional $19B unconditional purchase commitments for cloud infrastructure (5-year term starting FY2027) | Server/storage networking providers, ODM/EMS channels, data-center systems integrators |
| Downstream: cloud demand converting capacity into revenue | OCI/cloud revenue mix (from SEC 10-K segment context extracted) depends on customers consuming capacity | Enterprises and developers consuming OCI capacity for AI workloads |
Credit and regulatory overhang
The Wisconsin credit/guarantee dispute is a “ratepayer protection tax” that converts BBB concerns into cash collateral risk
Reports say Oracle’s credit rating slide to BBB coincided with a Wisconsin Public Service Commission dispute involving financial guarantees that could cost more than $100M annually. We can’t fully validate the exact “BBB downgrade + $100M” chain from Oracle’s SEC filing extract alone in this session, but we can validate Oracle’s capex intensity and its credit-sensitive borrowing structures — the exact ingredients that make regulators and utilities tighten collateral rules.
- Regulatory financial guarantees are effectively a second liquidity channel: even if operating performance later improves, collateral requirements can require immediate cash or letters of credit.
- That collateral requirement compounds the capex-to-free-cash-flow mismatch during the ramp phase.
- So the dispute is not only legal risk; it’s operational finance risk.
Management actions: what they signal
Oracle has already leaned into equity + notes, so the market should expect ongoing financing—unless utilization ramps faster than capex
Oracle didn’t wait for the FY2026 cash squeeze to appear in hindsight. It established an ATM equity program up to $20B and issued large notes plus mandatory convertible preferred depositary shares in early 2026, which is consistent with an approach of keeping funding optionality open during a long infrastructure ramp.
| Action | When | What it buys Oracle |
|---|---|---|
| Oracle ATM equity program | Feb 2, 2026 | Ability to raise equity opportunistically up to $20B; can reduce pressure to issue equity at the worst moment. |
| Oracle notes offering | Consummated Feb 4, 2026 | Lock in multi-year funding for capex/general corporate uses. |
| Oracle Series D mandatory convertible preferred (depositary shares) | Closed Feb 5, 2026 | Hybrid instrument providing capital with later conversion mechanics (reducing immediate straight equity dilution complexity). |
Investment thesis (synthesis)
Oracle’s AI megacampus works only if demand monetization catches up to power-led capex timelines
The evidence we can hard-anchor from filings supports one thing strongly: Oracle has entered a heavy infrastructure build phase (FY2026 capex $55.7B vs $21.2B), backed by long-dated lease/power commitments and early-2026 capital-market financing. The critical question is whether OCI revenue ramp and utilization keep pace with infrastructure readiness — especially where the power grid is the bottleneck.
- Base-case (supported by filings): Capex-intensive AI builds temporarily depress free cash flow and increase reliance on financing.
- Bull case: Faster-than-expected usable capacity and stable credit treatment allows the ramp to monetize and free cash flow to recover.
- Bear case: Overruns extend timelines and regulatory/power constraints increase collateral or delay utilization, making the balance sheet carry more cost per monetized capacity for longer.
