Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Oracle’s reported $664 billion of remaining performance obligations (RPO) is a multi-year revenue pipeline, not $664 billion of current revenue, cash or profit. Oracle expects to recognize portions over several years as it delivers cloud capacity and other contracted services; the timing, cost of fulfillment and renewals determine how much reaches earnings and free cash flow.
What Oracle’s cloud backlog actually measures
Oracle’s best disclosed proxy for its cloud backlog is remaining performance obligations, or RPO. RPO represents contracted consideration for services and other obligations that Oracle has not yet delivered. It provides visibility into future billings and revenue recognition, but it is not a sales forecast and does not guarantee a particular margin or cash outcome.
Oracle reported RPO of $664 billion as of August 31, 2026, compared with $455 billion a year earlier. The company attributed the increase primarily to significant cloud contracts entered during the period. RPO is broader than a pure cloud-infrastructure figure, so it should be treated as a company-wide contractual measure and a proxy for cloud backlog rather than a separately audited cloud-only balance.
RPO also differs from bookings. A booking records a newly signed contract; RPO is the value of obligations still outstanding after considering the contracts already in force and the services already delivered. Revenue is recognized only as Oracle satisfies its performance obligations. Cash can arrive before, during or after recognition, depending on billing terms and financing components.
#1 Best Overall
When could Oracle recognize the $664 billion?
In its 2026 Form 10-Q, Oracle said it expected to recognize approximately 13% of RPO as revenue over the next 12 months, 37% during months 13 through 36, 34% during months 37 through 60, and the remainder thereafter. Applying those percentages to $664 billion produces the following analytical estimates:
| Recognition window | Oracle’s disclosed share | Approximate amount based on $664 billion | How to interpret it |
|---|---|---|---|
| Next 12 months | 13% | About $86 billion | Near-term revenue pipeline, not incremental revenue guidance |
| Months 13–36 | 37% | About $246 billion | Expected delivery in years two and three |
| Months 37–60 | 34% | About $226 billion | Expected delivery in years four and five |
| After month 60 | Approximately 16% | About $106 billion | Long-dated obligations and amounts outside the five-year view |
The dollar figures are simple multiplication of Oracle’s percentages and its August 31 balance. They are analytical estimates, not Oracle guidance. The schedule will change as Oracle signs new contracts, delivers services, recognizes revenue, experiences cancellations or renewals, and updates its estimates.
How Oracle recognizes cloud contracts
Subscription cloud services
Oracle states that Oracle Cloud Applications and Oracle Cloud Infrastructure arrangements generally last one to five years, may be renewed at the customer’s option, and are recognized ratably over the contractual period. If a customer pays for a year of capacity and support, Oracle generally records the consideration as revenue as the service is provided rather than when the contract is signed.
Usage-based arrangements
For usage-model contracts, Oracle recognizes revenue as customers consume cloud services over time. A contract can therefore be large in total value but produce less revenue in an early period if usage ramps slowly. Conversely, heavy compute or storage consumption can accelerate recognition relative to a simple straight-line subscription.
Software licenses and other obligations
Software license transactions are generally recognized up front when the software is made available. That pattern differs from cloud subscriptions and means the mix of RPO matters. Two providers can report similar RPO totals but recognize revenue at different speeds if one has more ratable cloud services and the other has more licenses, implementation work or usage-based commitments.
What current operating results say about conversion
Oracle reported $11.6 billion of total cloud revenue in the first quarter of fiscal 2027, up 62% year over year. Cloud infrastructure revenue was $7.4 billion, up 121%. Those figures show that cloud delivery is already scaling, but they should not be divided mechanically into the $664 billion RPO to predict a precise growth rate. The RPO balance includes obligations that may be recognized over many years and may include services beyond infrastructure.
Oracle also said customers booked more than $30 billion of additional AI cloud contracts in the quarter. It delivered 850 megawatts of additional data-center capacity during the same period. These are indicators of demand and supply expansion, not proof that every newly booked dollar will be recognized immediately.
Oracle’s fiscal 2026 release reported $638 billion of RPO at May 31, 2026, up $85 billion sequentially. It said $75 billion of large AI-contract RPO represented prepaid or customer-supplied hardware. That disclosure is important: a high RPO total can contain contracts where customers fund equipment or provide hardware, so the economic burden and revenue pattern may differ from a conventional fully Oracle-funded cloud deployment.
Why backlog does not equal profit
Capacity must be funded before service delivery
Oracle spent $28.5 billion on capital expenditures in the first quarter of fiscal 2027, compared with $8.5 billion in the prior-year quarter. The company said the increase was primarily for data-center expansion. At the same time, first-quarter free cash flow was negative $5.4 billion. This is the central financial tension in the backlog: Oracle may have contractual visibility years into the future while spending cash today on land, buildings, power systems, networking and accelerators.
Lease commitments add long-term fixed obligations
Oracle disclosed $288 billion of additional data-center lease commitments. Those leases generally begin between fiscal 2027 and fiscal 2029 and run for 15 to 19 years. Lease commitments are not the same as immediate capital expenditure, but they create future fixed payments that must be supported by operating cash flow, financing or additional customer receipts.
Prepayments improve cash timing but not instant revenue
Oracle reported $11.4 billion of customer prepayments with a significant financing component in the first quarter of fiscal 2027. Prepayments can strengthen near-term cash, yet they are not automatically revenue. Where a significant financing component exists, the effects are reflected in deferred revenue and recognized over the performance period. The accounting therefore separates the date Oracle receives money from the date it delivers the contracted cloud service.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to read the backlog against future earnings and cash flow
Revenue timing
The 13% next-12-month share provides the clearest near-term visibility, but it should be viewed as a portion of the existing balance, not as a forecast of total company revenue. New contracts can replenish or expand RPO while older contracts convert into revenue, so a growing RPO balance can coexist with substantial recognition.
Margins and unit economics
RPO does not disclose the gross-margin profile of each contract. AI infrastructure may require expensive GPUs, power and networking, and contracts with customer-supplied hardware may have different economics from contracts financed entirely by Oracle. Without contract-level costs, the backlog cannot be translated into future operating income simply by multiplying it by a historical margin.
Cash conversion
Cash flow depends on billing schedules, customer prepayments, construction spending, lease payments, equipment purchases, working capital and financing. Negative free cash flow during a capacity build-out does not by itself invalidate the backlog, but it shows that accounting revenue and cash generation can be separated for a prolonged period.
Can Oracle build enough capacity to deliver the contracts?
Oracle’s earnings release identified several execution dependencies: anticipating and managing data-center capacity, sourcing GPUs, operating complex cloud offerings, responding to economic conditions and protecting systems against cybersecurity threats. The company’s statement that demand for AI cloud training and inferencing services is growing faster than supply captures the immediate constraint: signed demand is valuable only if Oracle can obtain equipment, power and facilities and put them into service on schedule.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →The 850 megawatts delivered in the first quarter demonstrates expansion, while the $28.5 billion quarterly capital-spending figure shows the cost of pursuing it. Long-term leases can secure physical capacity but also reduce flexibility if demand, technology or customer requirements change. GPU supply and model-generation cycles create additional risk because equipment can become obsolete before a long contract is fully recognized.
Best Value
What the $664 billion does not tell you
- It does not show customer-by-customer concentration. Oracle has not quantified how much of the total depends on its largest customers.
- It does not provide a cancellation rate or renewal rate. Cloud arrangements may be renewable at the customer’s option, so renewal assumptions matter after the current contractual term.
- It does not disclose a gross-margin schedule for the backlog.
- It does not guarantee that every dollar will be recognized on the original timetable. Usage, implementation, capacity and contract changes can affect timing.
- It does not equal cash on hand. Billing terms and significant financing components can move cash ahead of or behind revenue.
- It does not isolate AI infrastructure from applications, support, licenses and other obligations included in the reported RPO measure.
A practical framework for comparing Oracle with another cloud provider
Backlog comparisons are meaningful only when the measures are defined consistently. Use these questions before concluding that one provider has a larger or better-quality pipeline:
- What is included? Check whether RPO covers infrastructure, applications, support, licenses, implementation and other contract types.
- How soon is it recognized? Compare the percentage expected within 12 months and the amount scheduled for years two through five.
- What is the revenue pattern? Separate ratable subscriptions, usage-based services and up-front license recognition.
- How is it financed? Examine customer prepayments, financing components and whether customers supply hardware.
- What must be built? Compare capital expenditure, leases, power commitments, GPU purchases and other fulfillment obligations.
- What happens to free cash flow? A provider may show strong bookings while funding a multiyear construction cycle through debt, leases or operating cash.
- How durable are contracts? Look for renewal, cancellation and customer-concentration disclosures, recognizing that Oracle has not quantified those items in the cited materials.
What investors should monitor next
Track RPO growth alongside the percentage scheduled for the next 12 months. A rising total with a falling near-term share would indicate that more value is moving into later periods; a stable total with stronger near-term conversion would suggest an aging pipeline. Neither signal is sufficient alone, because new bookings and revenue recognition change the denominator continuously.
Monitor cloud infrastructure growth, delivered megawatts, capital expenditures, lease additions, free cash flow and customer prepayments together. The combination reveals whether Oracle is converting contracts into operating capacity and cash or merely increasing obligations ahead of fulfillment.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Finally, watch disclosures about GPU availability, data-center delivery, cybersecurity incidents, customer concentration, renewals and contract economics. These factors determine whether the contractual pipeline becomes durable, profitable revenue.
Bottom line
Oracle’s $664 billion RPO is best understood as a five-year-plus pipeline of contracted obligations. On Oracle’s stated schedule, roughly $86 billion could be recognized in the next 12 months, about $246 billion in months 13–36, $226 billion in months 37–60 and $106 billion thereafter, assuming the percentages applied to the August 31 balance remain representative. The opportunity is substantial, but delivery requires unprecedented data-center investment, long-term leases and reliable access to GPUs and power. RPO establishes visibility; it does not establish immediate revenue, cash, profit or guaranteed execution.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
