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 -, -,
br1 Brazil -, -,
ie1 Ireland -, -,
de1 Frankfurt -, -,
jp1 Japan -, -,
sg1 Singapore -, -,
us1 US East Coast (Virginia) - , -,
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

us2 region is not available for Client

Private Interconnect Regions

If you have access to private Interconnect connections, you will also be able to use one of the following values

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 - 443 (Signaling), 10,000 - 20,000 (Media)
us2-ix US West Coast (Oregon) over Interconnect exchange in San Jose - 443 (Signaling), 10,000 - 20,000 (Media)
ie1-ix Ireland over Interconnect exchange in London - 443 (Signaling), 10,000 - 20,000 (Media)
de1-ix Frankfurt over Interconnect exchange in Frankfurt - 443 (Signaling), 10,000 - 20,000 (Media)
sg1-ix** Singapore over Interconnect exchange in Singapore - 443 (Signaling), 10,000 - 20,000 (Media)
jp1-ix** Tokyo over Interconnect exchange in Tokyo - - 443 (Signaling), 10,000 - 20,000 (Media)
au1-ix** Sydney over Interconnect exchange in Sydney - - 443 (Signaling), 10,000 - 20,000 (Media)

** Requires Voice Client JS SDK 1.9.5+

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:


See Twilio.Client.Device documentation for more information.

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.