Loading…

Twilio (TWLO) backlog: remaining performance obligations

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

Data as of .

Twilio backlog history

$0$2B$4B$6BDec 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$121M$5.83B0.0 yrs$157M
30 Jun 2026$138M$5.57B0.0 yrs$153M
31 Mar 2026$158M$5.30B0.0 yrs$160M
31 Dec 2025$175M$5.07B0.0 yrs$159M
30 Sep 2025$169M$4.90B0.0 yrs$159M
30 Jun 2025$159M$4.73B0.0 yrs$148M
31 Mar 2025$169M$4.58B0.0 yrs$154M
31 Dec 2024$182M$4.46B0.0 yrs$156M
30 Sep 2024$148M$4.34B0.0 yrs$139M
30 Jun 2024$153M$4.24B0.0 yrs$139M
31 Mar 2024$151M$4.19B0.0 yrs$142M
31 Dec 2023$144M$4.15B0.0 yrs$144M

Questions

What is Twilio's backlog?
Twilio reported $121M of remaining performance obligations at 30 Sep 2026, down 28% from a year earlier and down 13% from the previous quarter. That is 0.0 years of trailing revenue already under contract. Book-to-bill last quarter: 0.99.

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.