Loading…

Cloudflare (NET) backlog: remaining performance obligations

How much revenue Cloudflare already has under contract, how fast it converts, and who it is with.

Data as of .

Cloudflare backlog history

$0$1B$2B$3BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$2.88B$2.73B1.1 yrs$877M
30 Jun 2026$2.73B$2.51B1.1 yrs$812M
31 Mar 2026$2.54B$2.33B1.1 yrs$755M
31 Dec 2025$2.50B$2.17B1.2 yrs$684M
30 Sep 2025$2.14B$2.01B1.1 yrs$599M
30 Jun 2025$1.98B$1.88B1.1 yrs$547M
31 Mar 2025$1.86B$1.77B1.1 yrs$508M
31 Dec 2024$1.69B$1.67B1.0 yrs$478M
30 Sep 2024$1.50B$1.57B1.0 yrs$390M
30 Jun 2024$1.42B$1.48B1.0 yrs$371M
31 Mar 2024$1.34B$1.39B1.0 yrs$356M
31 Dec 2023$1.24B$1.30B1.0 yrs$348M

Questions

What is Cloudflare's backlog?
Cloudflare reported $2.88B of remaining performance obligations at 30 Sep 2026, up 34% from a year earlier and up 5% from the previous quarter. That is 1.1 years of trailing revenue already under contract. Book-to-bill last quarter: 1.19.
How fast does Cloudflare's backlog turn into revenue?
Over the last twelve months Cloudflare recognised revenue equal to about 110% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.