Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Third Party Exchange

Third Party Exchange is yet another way of creating an Interconnect with Twilio. By utilizing the Third Party Exchange option, our customers can connect to Twilio's infrastructure from a 3rd party provider (Currently supported: Equinix Fabric, Megaport, and Packet Fabric) to create a virtual Cross Connect. This is extremely advantageous for customers that have their calling infrastructure hosted in the cloud and would like to maintain their existing provider. In order to do this, you/your provider and Twilio will have to configure our respective network components.


Network Requirements

network-requirements page anchor

Your end

your-end page anchor

IP Addresses

ip-addresses page anchor

Your border devices (e.g. IP-PBX, SIP-PRI IAD, Session Border Controller, NAT gateway, etc.) will need to be assigned IPv4 addresses.



Your IP routes must be globally unique ("public IPs") rather than RFC 1918(link takes you to an external page) address ranges. In other words, your IP addresses have to be outside of the following ranges :

  • -
  • -
  • -

You will need to add Twilio's IP routes to the access control list on your firewall (e.g. AWS Network ACL) to allow your and Twilio's platform elements to talk to each other.

All services accessed over the Third Party Exchange will come from known Twilio IP ranges. We encourage you to allow all Twilio's IP routes on your firewall.

Step 1 Submit a request with the third party exchange

step-1-submit-a-request-with-the-third-party-exchange page anchor

Submit a request via the third party exchange portal (i.e. Equinix Fabric(link takes you to an external page), Megaport). To prevent any delays in provisioning, it is important to complete this step before proceeding to step 2.

Step 2 Submit a provisioning request in Twilio Console

step-2-submit-a-provisioning-request-in-twilio-console page anchor

You will need to provide the following information to submit a request:

  • Desired connection exchange location.
  • Desired bandwidth.
  • Service provider (i.e. Equinix Fabric, Megaport).
  • Public BGP interface IP if you would like to use your own. If not, Twilio can assign a private BGP interface IP from the link local range 169.254.X.X.
  • Public Autonomous System Number (ASN) if you have one. Twilio can assign a private one if you don't have one already.
  • BGP Prefix.

Step 3 Twilio configures the connection

step-3-twilio-configures-the-connection page anchor

Twilio will proceed to set up the connection and allocate a BGP interface (point-to-point) IP along with a private ASN if necessary. You will be notified once the connection has been configured by Twilio. At this point your configuration details will be viewable in Console.

Step 4 Advertise IP routes

step-4-advertise-ip-routes page anchor

Advertise your IP routes via the Third Party Exchange. The routes for your devices must be announce via BGP to Twilio over the connection.

Rate this page: