SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site,, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to, 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.

Japan Porting

The following topics are discussed in this guide. Click a topic to skip directly to this information:

In Japan we offer porting for the following number types:

  • Toll-Free +(81)800,(+81)120

Please note that most of Japanese Phone Numbers have Voice capability only. Below are instructions for porting Japanese phone numbers into Twilio. You can find porting summary and timelines here.

Japan Porting Requirements

General requirements

  • The full list of numbers that you wish to port in E164 format, eg: +[81][XXXXXXXX].
  • Porting form  signed by the authorized user and/or owner of the number(s). Note that the information on your porting form must match the authorized user name and service address provided by your current carrier. You can find the Porting Form required for the Japanese numbers below. Please ensure that following information is added:
    • Numbers to be ported 
    • End user address, same as on the current provider records  
    • Date, signature
  • Your Twilio Account SID (Your unique ID starting with “AC” that you can find on the main dashboard in Twilio Console).
  • Additionally, upload compliance documents before submitting your port request. You can see the full list of required documents here.
    • Upload your documents in the Twilio Console by selecting “Phone Numbers” > “Regulatory Compliance“ > “Bundles” or follow the link here. Please note the address restrictions to avoid rejections.
    • Choose the country, the phone number type and follow the instructions. Processing of the compliance documents may take up to several business days.
    • Once your documents have been accepted, please share the associated links that start with "BU" and "AD" along with the porting request via email.
  • It is important to note that you will need to send the original physical LOA to Twilio's Carrier partner, when your current provider approves the port. 

Japan Porting Process 

    1. Submit your porting request with all the requirements in place via this submission form.
    2. Twilio approves the port request. If everything in Step 1 is correct, you can expect Twilio to approve your port request within 24 business hours.
    3. Twilio submits the number to the Carrier Partner. This can take up to 24 business hours. Your request is then submitted to your soon-to-be former carrier as a port request. During this time, do not close your account with your carrier and keep your numbers active.
    4. Twilio’s Carrier Partner reaches out to the Losing Carrier. This can take around one week to complete.
    5. Response from the carrier. At this point, your request is either approved or rejected:
      • Approved: If approved, Twilio will notify you about a porting date. 
      • Rejected: Rejections can occur due to various reasons. However, rejection will need to be resolved with your current provider, before order can be resubmitted. 
    6. Twilio reaches out to you with a porting date. Twilio emails you with a porting date and time slot if known. Your number is on your Account and can be visible in the Twilio Console. 
    7. You will need to send the original physical LOA to Twilio's Japanese Carrier partner. 
    8. Configure your number. It is critical to configure your number prior to the porting date. This will minimize the service downtime. You can configure the numbers from the Twilio Console.
    9. Your phone number is with Twilio. Once your number(s) is routing to Twilio and everything works as expected, you can remove the number(s) from your former provider.

We charge a one-time porting fee for Japan, for more details please reach out to

Have more questions? Submit a request
Powered by Zendesk