Loading…

PagerDuty (PD) backlog: remaining performance obligations

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

Data as of .

PagerDuty backlog history

$0$200M$400MOct 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$426M$495M0.9 yrs$236M
30 Apr 2026$441M$494M0.9 yrs$243M
31 Jan 2026$449M$492M0.9 yrs$249M
31 Oct 2025$415M$489M0.8 yrs$223M
31 Jul 2025$425M$484M0.9 yrs$230M
30 Apr 2025$430M$476M0.9 yrs$240M
31 Jan 2025$440M$468M0.9 yrs$246M
31 Oct 2024$405M$457M0.9 yrs$217M
31 Jul 2024$403M$447M0.9 yrs$218M
30 Apr 2024$388M$439M0.9 yrs$224M
31 Jan 2024$247M$431M0.6 yrs$228M
31 Oct 2023$206M$420M0.5 yrs$196M

Questions

What is PagerDuty's backlog?
PagerDuty reported $426M of remaining performance obligations at 31 Jul 2026, up 0% from a year earlier and down 3% from the previous quarter. That is 0.9 years of trailing revenue already under contract. Book-to-bill last quarter: 0.88.
How fast does PagerDuty's backlog turn into revenue?
Over the last twelve months PagerDuty recognised revenue equal to about 115% 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.