Is Google Cloud revenue keeping pace with its backlog, and which spending range is really Alphabet's?
Alphabet's current spending guidance is the higher range it set in July, and Cloud revenue is growing faster than its backlog but has not yet reached the size Alphabet's own schedule for that backlog calls for.
Drafted with Claude Opus 5.5; counter-case by GPT-6 Astra · read and committed by the publisher How we work →
Bottom line
- Which of the two capital-spending ranges in circulation is Alphabet's, and is Google Cloud revenue keeping up with its contracted backlog?
- The higher range, raised on the July call, is current, and Cloud revenue is growing faster than the backlog but is not yet at the size Alphabet's own recognition schedule implies.
- Grant Bishop's view: A third-quarter report showing Cloud revenue growing more slowly than the backlog, or margins giving way under rented capacity, would change that answer.
What would change our mind
If Alphabet's third-quarter report shows Cloud revenue growing more slowly from the second quarter than the Cloud backlog, or Cloud margins falling sharply on rented capacity, the conclusion that revenue is keeping pace on growth would no longer hold.
The question
Two ranges circulate for Alphabet's capital expenditure this year, meaning its spending on data centers, servers and other long-lived assets: $195–205B and $180–190B . Google Cloud's contracted backlog, meanwhile, was put at $514B on the second-quarter call . The question has two halves: which spending range is current, and whether Cloud revenue is growing fast enough to turn that backlog into sales on the schedule Alphabet itself has set. The answer bears on Spending on the AI build is running ahead of its revenue, and on Spare computing capacity does not stop new power construction.
Spending on the AI build is running ahead of the revenue it produces.
What is known
The spending conflict is a matter of dates. On its second-quarter call on July 22, Alphabet raised its guidance to the higher range from the lower one, citing faster delivery of capacity . The lower range had itself been raised on the first-quarter call, to include an acquisition . A prospectus supplement filed in June still carries the lower range ; it predates the July call. The lower range is not a rival estimate. It is an old one.
Spending ran at $80.6B in the first half , of which $44.9B fell in the second quarter , and Alphabet said 2027 capital expenditure will increase significantly . Second-quarter free cash flow, meaning operating cash flow less capital spending, was negative $5.9B, against $53.3B over the trailing twelve months .
On the backlog, Alphabet's quarterly filing for the second quarter puts remaining performance obligations, which is contracted revenue not yet recognized, attributable to Google Cloud at $513.9B , from $462.3B at the end of March . Its first-quarter filing said it expects just over 50% of the backlog to be recognized within 24 months .
Cloud revenue rose 82% to $24.8B in the second quarter , from $20.0B in the first, when growth was 63% . Cloud's operating margin was 35.6% . Alphabet said it would expand third-party capacity in the third quarter as a bridge to its own, and that this would pressure Cloud margins .
Names that bear on this
Alphabet reported second-quarter results and held its call on July 22 , and filed its quarterly report for the period . Those disclosures settle the spending range and show Cloud revenue outgrowing its backlog in the quarter, while leaving open whether revenue reaches the size the recognition schedule implies. Its third-quarter report is the next disclosure that resolves both halves.
Amazon reported on July 30 that Amazon Web Services (AWS), its cloud unit, had reached an annualized sales run-rate of $169B . Its quarterly filing put commitments on contracts longer than one year at about $496B at the end of June, from about $364B at the end of March ; the definition differs from Alphabet's, so the comparison is loose. Its last explicit spending guidance, about $200B for the year, came in its fourth-quarter release early this year , and its second-quarter release did not restate it ; trailing-twelve-month free cash flow turned negative, at about -$7.6B . Amazon cuts both ways: a peer spending at similar scale with cash flow already below zero, and a backlog that grew faster than Alphabet's over the same quarter. Its third-quarter results are the next disclosure; no release in these sources has dated them.
The case for
The spending conflict resolves cleanly. The two ranges are two points in time, not two readings of one plan: the higher is the July guidance, and the lower survives only in a June document filed before it . The range has gone up twice in two quarters, and each time Alphabet named the cause, an acquisition in the first quarter and faster delivery of capacity in the second . Guidance raised for stated reasons describes a company spending into demand it can already see.
That demand shows up in revenue. Cloud revenue went from $20.0B in the first quarter to $24.8B in the second , while the Cloud backlog went from $462.3B to $513.9B . In proportion, revenue grew the faster of the two, so on the quarter the backlog is not running away from the business meant to fill it. Growth of 82% did not come at the cost of profitability: Cloud's operating margin was 35.6% .
The conversion hurdle is steep, and the second quarter shows it can be climbed. Recognizing just over half the backlog within the window Alphabet has given requires Cloud revenue well above its second-quarter level, so Cloud has to keep accelerating. It did exactly that between the first and second quarters, when year-on-year growth stepped up sharply . Rented third-party capacity in the third quarter is Alphabet's own answer to the constraint: it chose to serve demand now rather than make customers wait for its buildings .
The depth of the backlog also stands out against the nearest peer. Amazon's commitments, on a different definition, are smaller than Alphabet's Cloud backlog and sit against a larger cloud business . The definitions differ, so the comparison is loose, but a bigger backlog behind a smaller revenue base still says the contracts Alphabet's revenue is chasing are plentiful, and the constraint it faces is capacity, not customers.
The case against
Faster percentage growth is not the same as enough revenue. The quarter-on-quarter comparison favors Alphabet, and it would be wrong to claim the backlog is currently outgrowing revenue . The test that matters is whether the revenue base is large enough to absorb the contracted work, and on that test the second quarter falls well short: a year of Cloud revenue at that quarter's pace would be a fraction of the $513.9B backlog .
Alphabet's first-quarter filing anticipated recognizing just over half the backlog within 24 months . Applied to the second-quarter balance, that schedule calls for annual revenue well above what Cloud now produces, so growth has to persist across the whole recognition period, not for a quarter. The reading is conditional, since the timing disclosure predates the larger balance, but it shows the size of the execution burden. One strong quarter is not delivery.
The spending conflict is resolved, and in the less comfortable direction. The current range is the higher one, issued in July; the June prospectus figure is not an equally current alternative . With $80.6B spent in the first half , the rest of the range asks more of each second-half quarter than the $44.9B spent in the second quarter . Free cash flow in that quarter was negative $5.9B; the trailing-twelve-month figure of $53.3B argues against reading one quarter as a trend, but the quarter shows the funding strain of the build, and Alphabet has said next year's spending will increase significantly .
Capacity shortage carries a disclosed profit cost as well. Alphabet said it would rent third-party capacity in the third quarter as a bridge and that this would pressure Cloud margins, so the 35.6% margin of the second quarter does not settle what converting the near-term backlog will earn . The objection is not weak demand or unsettled guidance. It is that the backlog still needs sizeable revenue growth while heavier spending, a quarter of negative cash flow and expected margin pressure leave the economics of meeting that demand unproven.
What we don't know, and when
We do not know whether the third quarter repeated the second: whether Cloud revenue again grew faster than the backlog, how far rented capacity pressed on Cloud margins, how much was spent against the higher range, and whether Alphabet still expects just over half the larger backlog to be recognized on the same schedule. Alphabet's third-quarter report answers all four. We do not know whether Amazon will restate its spending guidance or how its commitments moved; its third-quarter results will show, and no release in these sources has dated them. Nor do we know how large next year's spending will be: Alphabet has said only that it will increase significantly, and no filing or release has dated a range.
What would change our mind
Our answer is that Alphabet's current spending guidance is the higher range set in July, and that Cloud revenue is outgrowing its backlog without yet reaching the size Alphabet's own schedule for that backlog implies. This sharpens Spending on the AI build is running ahead of its revenue: the open half of the question now sits on a single set of third-quarter numbers rather than on a dispute over which range to believe. If the third-quarter report shows Cloud revenue growing more slowly from the second quarter than the Cloud backlog, the claim that revenue is keeping pace fails and we revise the answer. If Cloud margins fall sharply on rented capacity, the case that the economics of conversion hold fails and we revise as well. If it shows revenue accelerating again with margins holding near the second quarter's despite rented capacity, the case against loses its sharpest point. A further change to the spending range would alter the first half of the answer only if Alphabet gave a reason other than capacity delivery.
How this piece was made
Sources. 10 numbered sources, in the Record.
Related claims
Tell the publisher
Something we should look at? Suggest a company, a topic or a feature.
Record
Written according to the Grant Bishop standard — machine-researched, machine-checked, human-judged; then read and committed by the publisher. Every number traces to a filing or a dated market record; every claim carries a date and what would prove it wrong.
- Drafted by
- Claude Opus 5.5; counter-case by GPT-6 Astra under Grant Bishop's methodology
- Verification
- multi-source verified, machine-drafted, human-gated
- As of
- 2026-10-25
- Published
- Oct 24, 2026, 21:08 ET · 2026-10-25 01:08 UTC · changelog
- Bears on
- What would change this
- If Alphabet's third-quarter report shows Cloud revenue growing more slowly from the second quarter than the Cloud backlog, or Cloud margins falling sharply on rented capacity, the conclusion that revenue is keeping pace on growth would no longer hold.
- Position disclosure
- The publisher holds index-level U.S. equity exposure and no direct position in any single name discussed.
- Not advice
- General commentary for a general audience. Not advice for your situation.