Loading…

Palo Alto Networks (PANW) backlog: remaining performance obligations

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

Data as of .

Palo Alto Networks backlog history

$0$10B$20BOct 2022Apr 2023Oct 2023Apr 2024Oct 2024Apr 2025Oct 2025Apr 2026Jul 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
31 Jul 2026$21.2B$11.5B1.8 yrs$7.75B
30 Apr 2026$18.4B$10.6B1.7 yrs$7.11B
31 Jan 2026$16.0B$9.89B1.6 yrs$6.25B
31 Oct 2025$15.5B$9.56B1.6 yrs$6.13B
31 Jul 2025$15.8B$9.22B1.7 yrs$6.30B
30 Apr 2025$13.5B$8.87B1.5 yrs$5.76B
31 Jan 2025$13.0B$8.57B1.5 yrs$5.60B
31 Oct 2024$12.6B$8.29B1.5 yrs$5.51B
31 Jul 2024$12.7B$8.03B1.6 yrs$5.54B
30 Apr 2024$11.3B$7.79B1.5 yrs$5.01B
31 Jan 2024$10.8B$7.53B1.4 yrs$4.92B
31 Oct 2023$10.4B$7.21B1.4 yrs$4.73B

Questions

What is Palo Alto Networks's backlog?
Palo Alto Networks reported $21.2B of remaining performance obligations at 31 Jul 2026, up 34% from a year earlier and up 15% from the previous quarter. That is 1.8 years of trailing revenue already under contract. Book-to-bill last quarter: 1.82.
How fast does Palo Alto Networks's backlog turn into revenue?
Over the last twelve months Palo Alto Networks recognised revenue equal to about 70% 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.