SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Why did I receive a port-away notification?

 

You received a port-away notification because one of Twilio's carrier partners has informed us that a phone number in your project is being ported (moved) from Twilio’s platform to another carrier’s network.

Here's what you can do next:

  • If the Port-Away is Expected: If you initiated this port-away or were expecting it, you should approve the notification to allow the process to proceed smoothly.
  • If the Port-Away is Not Warranted: If you did not initiate or expect this port-away, you should dispute the notification. By disputing it, Twilio will work on your behalf to retain the phone number.

In some instances, we will approve the request because we validate the port request with the information shared by the new carrier. If you notice any unauthorized port post we approved the request; immediately dispute the request directly from the console or reach out to us.
If you do not submit a dispute, the port-away request will be allowed to proceed.

Please refer to this article to know how to dispute the port away request and for additional assistance, reach out to the Twilio porting team at porting@twilio.com .

Have more questions? Submit a request
Powered by Zendesk