Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Getting Started With Cross-connect

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.


Your 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.
Data Center Location
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 SG3 Singapore
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: - - -

  • Firewall. You will need to add Twilio's IP routes to the access control allow list on your firewall to allow your and Twilio's platform elements to talk to each other.

Twilio components

  • 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 allow 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.

Location 10-Mbps 100-Mbps 500-Mbps 1-Gbps
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.

Provider components

  • Cross-connect. The data center provider will cross-connect your and Twilio ports in the meet-me-room.

What you will need to create a Twilio Interconnect connection

What Why How
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

Configuring your private connection to Twilio

Step 1: Let your Twilio onboarding contact know your:

  • Desired Exchange location and bandwidth
  • IP routes
  • public ASN if you have one
  • Twilio account SID

Step 2: Order a cross-connect with the letter of authorization from Twilio, with your provider

Step 3: Receive point-to-point IP from Twilio

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.

Step 4: 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.

Next step

Rate this page:

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 browsing the Twilio tag on Stack Overflow.