Twilio offers numerous cloud-based communication products and APIs that can be consumed by developers to build applications and tools to communicate with their end-users and enhance their user experience.
To accomplish this requires a network connection to Twilio. This can be routed over the open Internet or via a secure, private connection.
The open Internet, although convenient, by definition has only a "best effort" service delivery with no quality or service guarantee. It also lacks security — traffic can be intercepted and is subject to eavesdropping — which means that it's not the right option for customers and organizations with QoS and bandwidth requirements, or stringent security requirements.
Twilio Interconnect is an alternative to the open Internet that provides private connections between your network and Twilio. It offers the best performance and data throughput, and the lowest latency. Since your data never touches the public Internet, it also provides the best security, and can guarantee quality from end-to-end.
There are several reasons why Interconnect is the preferred method of connecting to Twilio. High availability, g_uaranteed data throughput_, quality of service, and enterprise-grade security are just a few of the strong arguments to make use of Twilio Interconnect. If you need highly consistent connectivity between your communication infrastructure and Twilio, then Twilio Interconnect is the right choice. Likewise if you have policies (internal or external) that preclude you from sending traffic across the open Internet — for example, HIPAA, PCI, or GDPR.
Twilio Interconnect has several flavors to accommodate various use cases:
Data Center: Equinix DC1
Twilio Edge Location ID: ashburn-ix (us1-ix)
208.78.112.0/25, 168.86.128.0/18 le 24208.78.112.0/25, 168.86.160.0/21Data Center: Equinix SV1
Twilio Edge Location ID: san-jose-ix (us2-ix)
67.213.136.0/25, 168.86.128.0/18 le 2467.213.136.0/25, 168.86.168.0/22Data Center: Equinix LD8
Twilio Edge Location ID: london-ix (ie1-ix)
185.187.132.0/25, 185.187.133.0/24, 168.86.128.0/18 le 24185.187.132.0/25, 185.187.133.0/24, 168.86.173.0/24Data Center: Equinix FR4
Twilio Edge Location ID: frankfurt-ix (de1-ix)
185.194.136.0/25, 168.86.128.0/18 le 24185.194.136.0/25, 168.86.174.0/24Data Center: Equinix SG3
Twilio Edge Location ID: singapore (sg1-ix)
103.75.151.0/25, 168.86.128.0/18 le 24103.75.151.0/25, 168.86.176.0/24Data Center: Equinix TY6
Twilio Edge Location ID: tokyo-ix (jp1-ix)
103.144.142.0/25, 168.86.128.0/18 le 24103.144.142.0/25, 168.86.177.0/24Data Center: Equinix SY3
Twilio Edge Location ID: sydney-ix (au1-ix)
103.146.214.0/25, 168.86.128.0/18 le 24103.146.214.0/25, 168.86.172.0/24Each Twilio region has dedicated equipment to offer secure interconnect services as listed in the table below. Once you choose your Exchange location and the desired bandwidth, Twilio will provision the required 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 Exchange 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. Similarly, for Europe and Asia Pacific, our exchanges in London, Frankfurt, Singapore, Tokyo, and Sydney can be used to accomplish redundancy in those regions.
| Location | 10Mbps | 100Mbps | 500Mbps | 1Gbps |
|---|---|---|---|---|
| US — Ashburn, Virginia | ✅ | ✅ | 🚫 | ✅ |
| US — San Jose, California | ✅ | ✅ | 🚫 | ✅ |
| UK — London | ✅ | ✅ | ✅ | ✅ |
| Germany — Frankfurt | ✅ | ✅ | ✅ | ✅ |
| Singapore | ✅ | ✅ | ✅ | ✅ |
| Japan — Tokyo | ✅ | ✅ | ✅ | ✅ |
| Australia — Sydney | ✅ | ✅ | ✅ | ✅ |
Your border devices (e.g., IP-PBX, SIP-PRI IAD, Session Border Controller (SBC), NAT gateway, etc.) will need to be assigned IPv4 addresses that are a part of one or more CIDR blocks (globally addressable) that your provider will announce to Twilio (your "IP Routes").
Your IP routes must be globally unique ("public IPs") rather than RFC 1918 address ranges. In other words, your IP routes have to be outside of the follow 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
All services accessed over Twilio Interconnect will initiate from Twilio's IP routes. You will see them announced via BGP. You must allow all of Twilio IP routes on your 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 freely without being blocked by the firewall or other security rules.