Twilio’s Cross Connect service provides a direct physical connection between your data center and Twilio’s cloud as if they were one and the same network. This means that there is no intermediary between your applications running on your infrastructure and Twilio’s platform hosting our APIs and services. This not only offers the best-in-the-market availability and performance, but also is the most secure way to utilize Twilio’s services.
Since Cross Connect is a direct connection between your network and Twilio’s, it provides the best performance, the least delay, and the best voice call quality.
Setting up Cross Connect
Three participants are needed to come together to create a Cross Connect: you, Twilio, and your data center provider. All three will need to provide the components that are required to set up the link.
One of the first choices you need to make is at which Interconnect Exchange you want to have a cross connect with Twilio.
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 one of our data centers’ meet-me rooms. 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”).
Your IP routes must be globally unique (“public IPs”), not RFC 1918 private address ranges. In other words, your IP routes have to be outside the following ranges:
You will need to add Twilio’s IP routes to your firewall’s access control accept-list to allow your network to talk to Twilio’s platform.
All services accessed over Twilio Interconnect will come from Twilio’s IP routes. You will see them announced via BGP. We encourage you to allow all of Twilio IP routes and ports on your firewall.
Twilio Interconnect connection
Twilio will provision bandwidth for your connections at the Twilio Interconnect Exchange locations you select. For high availability, we strongly recommend connecting to at least two of our geographically redundant Twilio Interconnect locations. For example, you can select a 100Mbps connection in Ashburn, Virginia and a 100Mbps connection in San Jose, California to create redundant connections to Twilio on both coasts of the United States. For Europe, Frankfurt and London are great redundant exchange locations. Singapore and Tokyo offer the same for the APAC region.
Letter of Authorization
You will receive a Letter of Authorization (LOA) from Twilio, permitting the data center provider to create a Cross Connect. The letter will specify the exact location of the port Twilio has provisioned for you.
Data center provider components
With the LoA issued by Twilio, the data center provider will cross-connect your ports and Twilio’s in the meet-me room.
Configuring your private connection to Twilio
Let your Twilio onboarding contact know your:
- Desired connection exchange location.
- Desired bandwidth for the Cross Connect.
- IP routes.
- Public Autonomous System Number (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 from your data center provider using the LoA from Twilio.
After the physical link has been set up, Twilio will assign a point-to-point IP to your connection. Twilio also issues a private ASN to you if you don’t already 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.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.