A Cross Connect refers to a physical connection that takes place at a provider's data center between Twilio's network and your network. To create a cross-connect, you, Twilio, and the data center provider will have to configure our respective network components.
Presence in a Twilio Exchange data center.Cross-connect links your internal network to the Twilio Interconnect location over Layer 2 Ethernet using gigabit single mode fiber. If you are already in one of our data centers you can connect to us directly in the meet-me-room. Alternatively, you can have a layer 2 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 the following data centers with more global data centers coming online soon.
|Equinix DC1-DC6, DC10, and DC11||Ashburn, Virginia, United States|
|Equinix SV1 and SV5||San Jose, California, United States|
|Equinix FR4||Frankfurt, Germany|
|Equinix LD8||London, United Kingdom|
|Equinix JP1||Tokyo, Japan|
|Equinix SY3||Sydney, Australia|
IP Routes.Your border devices (e.g. IP-PBX, SIP-PRI IAD, Session Border Controller, NAT gateway, etc.) will need to be assigned 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 address ranges - to avoid conflicts with other networks that Twilio platform is peered with. In other words, your IP routes have to be outside of the following ranges:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
Firewall.You will need to add Twilio's IP routes to the access control whitelist on your firewall to allow your and Twilio's platform elements to talk to each other.
IP Routes.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 Interconnect Connection.Twilio will provision bandwidth for your connections at Twilio Interconnect locations selected by you. See connection bandwidth and location options listed below. 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.
|US - Ashburn, Virginia||✅||✅||🚫||✅|
|US - San Jose, California||✅||✅||🚫||✅|
|UK - London||✅||✅||✅||✅|
|Frankfurt - Germany||✅||✅||✅||✅|
|Tokyo - Japan||✅||✅||✅||✅|
|Sydney - Australia||✅||✅||✅||✅|
Letter of Authorization.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.
Cross-connect.The data center provider will cross-connect your and Twilio ports in the meet-me-room.
|Presence in a Twilio Interconnect data center||to cross-connect with Twilio you will need a physical port in a Twilio Interconnect data center||connect to us in the meet-me-room room or procure a point-to-point circuit to the meet-me-room in one of our data centers.|
|Connection bandwidth and location requirements||so that Twilio can provision adequate bandwidth for your needs||to estimate bandwidth, convert your maximum number of concurrent calls to required throughput in Mbps. Many of our customers found the following ratio helpful: 1 Mbps of bandwidth is roughly equal to 10 concurrent G.711 codec calls.|
|Letter of authorization||to allow the data center provider to cross-connect your and Twilio's infrastructure||Twilio will provide you with the letter of authorization|
|Your IP routes||so that Twilio can allow traffic from your network||share IP routes for your border devices with your Twilio onboarding contact|
|Your ASN||to configure dynamic routing using BGP between your and Twilio networks||ask your network administrator for your company's ASN; if you are using a public ASN, you must own it. If you don't own one, Twilio will issue a private ASN to you in the 65000 range.|
|Twilio’s IP routes||to allow traffic from Twilio to your network||ask your network administrator to permit traffic from Twilio's routes/ports|
- Desired Exchange location and bandwidth
- IP routes
- public ASN if you have one
- Twilio account SID
After the physical link is setup, Twilio will assign a point-to-point IP to your connection. Twilio also issue a private ASN to you if you don't own a public one.
The routes for your border devices must be announced via BGP to Twilio over the cross-connect.