What is RPO — $2.5 trillion of big tech backlog, and why it is still not revenue
RPO (remaining performance obligations), often called backlog, is the value of contracts a company has signed but not yet delivered, so it cannot yet book them as revenue. Think of it as a reservation ledger for future revenue. In the AI boom it has become the key number for cloud companies. As of the latest quarters, Amazon's AWS reported $578 billion, Microsoft $677 billion in commercial RPO, Google $567.7 billion and Oracle $664 billion, about $2.5 trillion combined. But backlog is not revenue. It is recognized over several years, may be concentrated in a few AI customers, can vanish if a customer cannot pay, and does not show the capital spending needed to deliver it
The three lines
- Meaning — contracts signed but not yet booked as revenue; a reservation ledger for future sales
- Scale — AWS $578B, Microsoft $677B, Google $567.7B, Oracle $664B; about $2.5 trillion combined
- Traps — years to recognize, customer concentration, renegotiation and default risk, and capex that stays out of view
Key questions
- what is rpo in earnings
- **The value of contracts signed but not yet delivered, so not yet booked as revenue. The formal accounting term is remaining performance obligations (RPO).** | Term | Meaning | |---|---| | Backlog | Orders received but not yet fulfilled; everyday term | | Remaining performance obligations (RPO) | Formal term whose disclosure accounting standards (IFRS 15, ASC 606) require | | Deferred revenue | Cash received before the service is delivered, so not yet revenue (part of RPO) | | Revenue | Amount recognized once the service is actually delivered |
- big tech cloud backlog comparison
- **As of the latest quarters, each of the four sits between $560 billion and $680 billion, about $2.5 trillion combined.** | Company | Backlog | As of | Notes | |---|---|---|---| | Microsoft | $677B (+73%) | September 30, 2026 | Commercial RPO, weighted average duration 2.3 years | | Oracle | $664B | August 31, 2026 | $455B a year earlier | | Amazon AWS | $578B | September 30, 2026 | Triple-digit growth year on year | | Google | $567.7B (Cloud $560.8B) | September 30, 2026 | Just over 55% recognized within 24 months |
- rpo vs revenue
- **Backlog is only a candidate for future revenue. When, and how much of it, becomes revenue has to be checked separately.** | | Backlog | Revenue | |---|---|---| | Timing | Future (months to years) | Already happened | | Certainty | Can shrink through changes, cancellation or default | Settled | | Costs | Capex needed to deliver is not shown | Reflected in profit with costs | | How to read | With recognition period and customer concentration | With growth rate and margin |
There is a number in big tech earnings that is bigger than revenue: money not yet earned. In its third-quarter results on October 29, 2026, Amazon said the AWS backlog stood at $578 billion — more than 12 times AWS revenue of $46 billion that quarter. A day earlier, Microsoft reported $677 billion and Google $567.7 billion. Oracle reported $664 billion in its previous quarter. Together that is about $2.5 trillion.
This number is used to justify AI infrastructure spending: customers have already signed, so building data centers is safe. Yet the same week, Amazon's share price reacted not to backlog but to free cash flow of minus $42.4 billion ("Amazon earnings and stock drop"). Here is what backlog is, and what it does not tell you.
1. What is RPO — a reservation ledger for future revenue
| Term | Meaning | Example |
|---|---|---|
| Backlog | Orders received but not yet fulfilled | A ship a shipbuilder has won but is still building |
| Remaining performance obligations (RPO) | The formal term accounting standards require companies to disclose: the value of obligations still to be performed under contracts | The remaining two years of a three-year cloud commitment |
| Deferred revenue | Cash received in advance but not yet revenue because the service has not been delivered | An annual subscription paid upfront |
| Unbilled commitments | Contracted but not yet even invoiced | Future years of a multi-year commitment |
RPO is deferred revenue plus unbilled commitments. International standards (IFRS 15) and US standards (ASC 606) require companies to disclose it, which is why cloud and software firms publish it every quarter. In industrial sectors such as shipbuilding, construction and defense, order backlog has long played the same role: a shipyard wins an order and books the revenue in pieces over the years it takes to build the ship.
In cloud, backlog grows like this. An AI company signs a commitment worth tens of billions of dollars to use GPU servers for three to five years. The cloud provider adds the full amount to backlog on day one, then moves it into revenue bit by bit as it actually delivers server capacity.
2. Backlog at four big tech firms — figures and definitions
| Company | Backlog | As of | Growth and notes |
|---|---|---|---|
| Microsoft | $677 billion | September 30, 2026 | Up 73% year on year; weighted average remaining duration 2.3 years |
| Oracle | $664 billion | August 31, 2026 | $455 billion a year earlier, $638 billion the prior quarter |
| Amazon (AWS) | $578 billion | September 30, 2026 | Triple-digit percentage growth year on year; Amazon calls it 'well diversified' |
| Google (Alphabet) | $567.7 billion | September 30, 2026 | Of which Cloud $560.8 billion; just over 55% recognized within 24 months |
| Total (simple sum) | About $2.487 trillion | — | Rough figure; definitions and dates differ |
Even under the same label, scope differs by company. Microsoft discloses only commercial (business-customer) RPO, and Amazon only AWS backlog. Google and Oracle report company-wide figures. Oracle alone uses an August 31 date. So $2.5 trillion should be used only as a rough gauge of scale.
A useful number for comparison is backlog as a multiple of revenue. AWS quarterly revenue of $46 billion annualizes to about $184 billion. A backlog of $578 billion is a little over three times that — at the current pace, more than three years of work already booked.
3. Why backlog is not revenue — five traps
| Trap | Explanation | Number to check |
|---|---|---|
| 1. Time | Becomes revenue in pieces over years | Share recognized within 12 and 24 months; weighted average duration |
| 2. Concentration | Mega-contracts from a few AI customers may make up most of it | Top-customer share (mostly undisclosed) |
| 3. Counterparty risk | If a customer cannot pay, contracts shrink or disappear | Customer cash and funding position |
| 4. Cost | The data centers and chips needed to deliver are not shown | Capital spending, free cash flow |
| 5. Changes | Renegotiation or new terms change the amount | Quarterly backlog changes and explanations |
Time. Google expects just over 55% of its Cloud backlog to become revenue within 24 months. The remaining 45% is a story for more than two years out. Microsoft's weighted average duration of 2.3 years points the same way.
Concentration and counterparty risk. Backlog exploded in the AI era because AI companies such as OpenAI and Anthropic signed compute commitments worth tens of billions of dollars. They are still running large losses and fund those commitments by raising investment. If funding dries up, the commitments wobble. The risk of a structure in which Nvidia funds its customers and the money returns as chip orders is covered in "What is AI circular financing". $16.8 billion of Google's RPO is a contract with Crux AI, an affiliated joint venture.
Cost. Turning a $578 billion backlog into revenue requires servers and data centers first. Amazon is spending about $220 billion on capital expenditure in 2026. Backlog shows the money coming in, not the money going out. The gap between the two is free cash flow ("What is free cash flow?").
4. How to read backlog — a checklist
| Question | Why it matters | Example from Q3 2026 |
|---|---|---|
| How fast does it become revenue? | The further out the revenue, the less certain | Google just over 55% within 24 months; Microsoft average 2.3 years |
| Who are the contracts with? | A large single-customer share concentrates risk | Most companies do not disclose customer shares |
| Does revenue growth keep pace? | Backlog rising without revenue suggests slow delivery | AWS revenue +39%, backlog triple-digit growth |
| How much capex? | The capacity and cost to deliver | Amazon $77.3 billion in the quarter, Google $51.4 billion |
| What about new bookings? | Backlog is cumulative; bookings are this quarter's new contracts | Microsoft commercial bookings down 12% (tough comparison with last year's mega-deals) |
Microsoft is a good example. Backlog rose 73%, but new contracts (bookings) this quarter fell 12%. That reflects a base effect from huge Azure contracts that bunched up a year earlier — information you would miss by looking at backlog alone.
5. Is a shipbuilding backlog the same as a cloud backlog?
| Shipbuilding and construction | Cloud | |
|---|---|---|
| Contract unit | One ship, one project | Compute commitments (GPU hours and the like) |
| Delivery period | 2–4 years | 1–5 years |
| Advance payments | Milestone payments | Mix of prepayment and monthly billing |
| Main risks | Raw material prices, shipowner cancellations | Customer funding trouble, chip and power supply |
| Familiar examples | South Korean yards such as HD Hyundai Heavy Industries and Hanwha Ocean | AWS, Azure, Google Cloud RPO |
South Korea's big shipbuilders have long reported order backlogs that investors watch the way cloud investors now watch RPO. The principle is the same. The difference is that cloud backlog is concentrated in a handful of young AI companies and depends on their ability to raise money. If a shipowner goes bust, a ship can be sold to another owner; a data center built for a specific customer is hard to re-let at the same price if that demand disappears. That is part of the basis for Gartner's warning that $3.5 trillion of AI infrastructure could be impaired.
6. Frequently asked questions
| Question | Answer |
|---|---|
| Does a large backlog lift the share price? | Oracle's stock jumped on a surge in RPO in 2025. In the week of October 26, 2026, Amazon reacted to cash flow rather than backlog. It depends on what the market is more worried about |
| Can backlog be cancelled? | It depends on contract terms. Most long-term commitments carry termination penalties, but if a customer is insolvent the money cannot actually be collected |
| Do companies outside the US disclose RPO? | Listed companies that follow IFRS 15 also disclose remaining performance obligations in their notes |
| Are backlog and RPO the same thing? | They are used interchangeably in everyday speech. The formal accounting term is RPO |
7. What remains and what is unconfirmed
- Customer concentration: None of the four discloses the share of backlog held by top customers. How much a few AI companies account for is the most important undisclosed figure.
- Oracle's latest figure: Oracle will report a new number with its next quarterly results, expected in December 2026.
- Recognition pace: For Amazon and Oracle, the share recognized within 12 and 24 months could not be confirmed within the scope of this article.
Big tech results and share reactions the same week are covered in "Why big tech stocks split after earnings", and the AI infrastructure impairment risk in "Gartner: $3.5 trillion of AI infrastructure faces impairment".
Sources
- Amazon IR — Amazon.com Announces Third Quarter Results (2026-10-29)
- Microsoft — FY27 Q1 Press Release (2026-10-28)
- US SEC — Alphabet Form 10-Q, quarter ended September 30, 2026
- US SEC — Oracle Form 10-Q, quarter ended August 31, 2026
- Data Studios — Amazon Q3 2026 results: AWS grows 39% to $46B, $578B backlog (2026-10-30)
- Sherwood News — What is an RPO? The number that drove Oracle's giant share move
- LPL Research — Who needs ROI when you can have RPO?