Menu

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?

Twilio Client Regions

Twilio Client 1.4 lets you select the specific Twilio data center used when your Twilio Client Device connects to Twilio. Network communication to and from Twilio will originate/terminate from the fixed, static IP address ranges listed below for each region. Refer to these ranges if you need to configure your local network to allow communication or apply Quality of Service routing rules to communication with Twilio.

Region information for twilio.js

By default, twilio.js will use Twilio's Global Low Latency routing capability to determine which data center is closest to your user, establishing a connection through Twilio's nearest point of presence. Global Low Latency uses latency-based DNS lookups to determine the nearest data center. You may want to override this in some cases, especially when your users are working from a fixed location and using a DNS server in another region.

If you are operating a restricted network that requires whitelisting of media IPs, our recommendation is to specify the region in your application. Twilio will continue to expand our Global Low Latency footprint in the future by adding more regions with different IP ranges and leaving the region selection up to Global Low Latency could result in connections being established to regions that are not whitelisted by your infrastructure which may result in one-way audio or call set up failures.

Use any one of the following values as the region parameter when calling .setup() in twilio.js version 1.3 or later. Leaving the value undefined will cause Twilio to default to its Global Low Latency routing, which cause the Device to establish its connection to the Twilio region closest to the user.

Region ID Location Media Server IP Address Range CIDR notation
au1 Australia 54.252.254.64 - 54.252.254.127 54.252.254.64/26
br1 Brazil 177.71.206.192 - 177.71.206.255 177.71.206.192/26
ie1 Ireland 54.171.127.192 - 54.171.127.255, 52.215.127.0 - 52.215.127.255 54.171.127.192/26, 52.215.127.0/24
de1 Frankfurt 35.156.191.128 - 35.156.191.255 35.156.191.128/25
jp1 Japan 54.65.63.192 - 54.65.63.255 54.65.63.192/26
sg1 Singapore 54.169.127.128 - 54.169.127.191 54.169.127.128/26
us1 US East Coast (Virginia) 54.172.60.0 - 54.172.61.255 , 34.203.250.0 - 34.203.251.255 54.172.60.0/23, 34.203.250.0/23
gll Use Twilio's Global Low Latency routing to select the data center with the lowest-latency connection to your user. Any of the above Any of the above

If you have access to private Interconnect connections and are using twilio.js version 1.4 or later, you will also be able to use one of the following values as the region parameter when calling .setup().

Region ID Location Signaling and Media Server IP Address Range CIDR notation Port Range
us1-ix US East Coast (Virginia) over Interconnect exchange in Virginia 208.78.112.64 - 208.78.112.127 208.78.112.64/26 443 (Signaling), 10,000 - 20,000 (Media)
us2-ix US West Coast (Oregon) over Interconnect exchange in San Jose 67.213.136.64 - 67.213.136.127 67.213.136.64/26 443 (Signaling), 10,000 - 20,000 (Media)
ie1-ix Ireland over Interconnect exchange in London 185.187.132.64 - 185.187.132.127 185.187.132.64/26 443 (Signaling), 10,000 - 20,000 (Media)

Example usage

Force connections through Twilio Ireland:

Twilio.Device.setup(token, { region: "ie1" });

Force connections through Twilio US East Coast region over your private Interconnect connection to that region:

Twilio.Device.setup(token, { region: "us1-ix" });

Let Twilio choose the nearest region:

Twilio.Device.setup(token);

See Twilio.Client.Device documentation for more information.

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.

Loading Code Sample...