Twilio Changelog | Apr. 13, 2026
Transit Caller ID Sunset: Migrate to Verified Caller ID or Immutable Call Forwarding Before June 22, 2026
Starting June 22, 2026, Twilio will begin sunsetting the Transit Caller ID feature for some customers. Customers currently using Transit Caller ID 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
Globally, regulators are increasingly restricting calls with modified caller IDs. Several countries 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 Caller ID
The right migration path for customers depends on how Transit Caller ID is currently being used.
Static non-Twilio numbers: Customers who always present the same caller ID on every call should migrate to Verified Caller ID or Twilio-owned numbers in their Twilio account. This lets them continue presenting their preferred number without relying on Transit Caller ID.
Dynamic non-Twilio numbers: Customers who present different non-Twilio numbers as caller IDs on a per-call basis because they are forwarding an inbound call back to the PSTN Elastic SIP Trunking customers should use ESIPT Immutable Call Forwarding.
Customers who have not migrated by June 22, 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.