Independent technology-migration research

PT-2026-018 · 17 July 2026

PlatformTrace

The public record of technology change.

Communications lifecycle bulletin · High confidence

Twilio began sunsetting Transit CallerID on 31 May 2026.

Customers using non-Twilio numbers as outbound caller IDs must move to supported static or forwarding-based alternatives.

Scope: this affects Transit CallerID configurations. Twilio Programmable Voice and Elastic SIP Trunking continue.

Verified change

Twilio says global restrictions on modified caller IDs make continued use of Transit CallerID vulnerable to carrier blocking. Customers that had not migrated by 31 May 2026 may experience interruptions to voice flows.

Migration paths

  • Static non-Twilio numbers: use Verified CallerID or Twilio-owned numbers.
  • Dynamic non-Twilio numbers: use Immutable Call Forwarding for Programmable Voice or Elastic SIP Trunking.

Limitations

The source warns of possible interruptions and carrier blocking. It does not claim that every call in every region fails immediately after the date.

Source

Twilio changelog: Transit CallerID sunset