Cross Connect provides a direct connection between your data center and Twilio's cloud as if they were one and the same network. this means that there is no man in a middle between your applications running on your infrastructure and Twilio's platform hosting our APIs and services, offering not only the best in the market avaiability and perfromance, but also the most secure option to utilize Twilio's services.
Since Cross Connect is a direct connection between your network and Twilio's, it provides the best perfromance and least delay offering the best voice call quality.
There are three components to create a cross-connect, parts from you, parts from Twilio and finally the data center provider will have to configure our respective network components to have end-2-end connectivity from your data center to Twilio. One of the first items to decide is at which Interconnect Exchange (list below) you want to have a cross connect with Twilio. Please see the below table for the available locations.
Cross Connect links your internal network to the Twilio Interconnect location using a gigabit fiber link. If you're already in one of our regional data centers you can connect to us directly in the meet-me-room. Alternatively, you can have an Ethernet point-to-point circuit provisioned between your location and the
meet-me-room of one of our data centers. Currently, Twilio Interconnect is available in these global data centers.
Your edge/border devices (e.g. IP-PBX, SIP-PRI IAD, Session Border Controller (SBC), NAT gateway, etc.) will need to be assigned global IPv4 addresses that are part of one or more CIDR blocks that your provider will announce to Twilio (your “IP Routes”). Note that your IP routes have to be globally unique ("public IPs") - as opposed to [RFC 1918](https://tools.ietf.org/html/rfc1918) address ranges.
Your IP routes must be globally unique ("public IPs") - as opposed to RFC 1918 address ranges. In other words, your IP routes have to be outside of the following ranges:
You will need to add Twilio's IP routes to the access control white-list on your firewall to allow your and Twilio's platform elements to talk to each other.
All services accessed over Twilio Interconnect will come from Twilio's IP routes. You will see them announced via BGP. We encourage you to whitelist *all* of Twilio IP routes and ports on your firewall.
Twilio will provision bandwidth for your connections at Twilio Interconnect exchange locations selected by you. See connection bandwidth and location options available. For high availability, we strongly recommend connecting to "at least two" of our geographically redundant Twilio Interconnect locations. For example, you can select a 100-Mbps connection in Ashburn, Virginia and a 100-Mbps connection in San Jose, California to create redundant connections to Twilio on both coasts of the United States. Similarly for Europe, Frankfurt and London are great redundant exchange locations where Singapore and Tokyo offer the same for the APAC region.
You will receive a letter of authorization (LOA) from Twilio, allowing the data center provider to create a cross connect. The letter will specify the exact location of Twilio's port provisioned for you.
Let your Twilio onboarding contact know your:
- Desired connection exchange location
- Desired bandwith for the cross connect
- IP routes
- Public ASN if you have one (Twilio can assign a private one for you if you don't have one already)
- Twilio account SID
Order a cross-connect (with the letter of authorization from Twilio)
After the physical link is setup, Twilio will assign a point-to-point IP to your connection. Twilio also issues a private ASN to you if you don't own a public one.
Advertise your IP routes via the cross-connect.
The routes for your border devices must be announced via BGP to Twilio over the cross-connect.