Twilio Changelog | Apr. 13, 2026
Transit CallerID Sunset: Migrate to Verified CallerID or Immutable Call Forwarding Before May 31, 2026
Starting May 31, 2026, Twilio will begin sunsetting the Transit CallerID feature. Customers currently using Transit CallerID to present a different phone number than the one they're calling from will need to migrate to an alternative before this date.
Why this is changing
Global regulators are increasingly restricting calls with modified caller IDs. Australia, Brazil, Norway, Germany, Spain, and Sweden have already implemented blocking or restrictions, and additional markets are following. Continuing to rely on Transit CallerID puts voice traffic at risk of carrier blocking in these and future regulated regions.
Two migration paths for customers using Transit CallerID
The right migration path for customers depends on how Transit CallerID is currently being used.
Static non-Twilio numbers: Customers who always present the same CallerID on every call should migrate to Verified CallerID or Twilio-owned numbers in their Twilio account. This lets them continue presenting their preferred number without relying on Transit CallerID.
Dynamic non-Twilio numbers: Customers who present different non-Twilio numbers as CallerIDs on a per-call basis (for example, ISVs presenting individual agent DIDs with a large number inventory) need to migrate based on their product: Programmable Voice customers should use PV Immutable Call Forwarding. Elastic SIP Trunking customers should use ESIPT Immutable Call Forwarding.
Customers who have not migrated by May 31, 2026 may experience interruptions to their voice flows.
Need a hand?
These resources will help:
For migration support and questions, customers with paid support should reach out to their Twilio account teams.