---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/interconnect/third-party-exchange#article
headline: Third Party Exchange
description: Use Third Party Exchange to connect to Twilio's infrastructure from a 3rd party provider. Learn about the requirements and next steps in this guide.
url: https://www.twilio.com/docs/interconnect/third-party-exchange
inLanguage: en
dateModified: 2026-08-13T17:05:12.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Third Party Exchange

Third Party Exchange lets you create a Twilio Interconnect connection from a third-party provider (Equinix Fabric, Megaport, and PacketFabric) to create a virtual Cross Connect. This is advantageous for customers that have their calling infrastructure hosted in the cloud and want to maintain their existing provider. To set it up, you (or your provider) and Twilio configure your respective network components.

![Diagram illustrating a virtual Cross Connect to Twilio via a third-party exchange provider.](https://docs-resources.prod.twilio.com/f2618e5bab0c85ef86ce93f71fa20084abacf4bf8635fcba4db7216c4b537257.svg)

## Network Requirements

### Your end

#### IP Addresses

Your border devices (e.g. IP-PBX, SIP-PRI IAD, Session Border Controller, NAT gateway, etc.) will need to be assigned IPv4 addresses.

> \[!WARNING]
>
> Your IP routes must be globally unique ("public IPs") rather than [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) address ranges. In other words, your IP addresses 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](/docs/interconnect#interconnect-regions-ip-details) to the access control list on your firewall (e.g. AWS Network ACL) to allow your and Twilio's platform elements to talk to each other.

### Twilio's end

#### IP Ranges

All services accessed over the Third Party Exchange will come from known Twilio IP ranges. We encourage you to allow **all** [Twilio's IP routes](/docs/interconnect#interconnect-regions-ip-details) on your firewall.

### Step 1 Submit a request with the third party exchange

Submit a request via the third party exchange portal (i.e. [Equinix Fabric](https://docs.equinix.com/connecting-to-service-provider/fabric-connect-twilio/), Megaport, PacketFabric). To prevent any delays in provisioning, it is important to complete this step before proceeding to step 2.

### Step 2 Submit a provisioning request in Twilio Console

You will need to provide the following information to submit a request:

* Desired connection exchange location.
* Desired bandwidth.
* Service provider (i.e. Equinix Fabric, Megaport).
* Circuit ID: For Equinix Fabric connections, enter the UUID. For Megaport connections, enter the Service Identifier. For PacketFabric connections, enter either the Request ID or the Circuit ID.
* Public BGP interface IP if you would like to use your own. If not, Twilio can assign a private BGP interface IP from the link local range 169.254.X.X.
* Public Autonomous System Number (ASN) if you have one. Twilio can assign a private one if you don't have one already.
* BGP Prefix.

### Step 3 Twilio configures the connection

Twilio will proceed to set up the connection and allocate a BGP interface (point-to-point) IP along with a private ASN if necessary. You will be notified once the connection has been configured by Twilio. At this point your configuration details will be viewable in Console.

### Step 4 Advertise IP routes

Advertise your IP routes through the Third Party Exchange. The routes for your devices must be announced through BGP to Twilio over the connection.