Edge locations allow customers to control their connectivity into and out of Twilio's platform; this includes routing over the public Internet and through private connections with Twilio's Interconnect.
Visit the Using the Twilio REST API in a non-US Region docs page to learn how to use Edge Locations with Twilio's Helper Libraries.
| Product | Documentation |
|---|---|
| Programmable SMS | API |
| Notify | API |
| Programmable Voice | API, Sending SIP & Receiving SIP |
| Programmable Voice SDK | Mobile SDK & JavaScript SDK |
| Elastic SIP Trunking | API & Trunking |
| HTTP Callback (Webhooks) | HTTP Callbacks (Webhooks) |
| Conversations | API (Excluding Media REST API) |
| Lookup | API |
| Edge ID | Location |
|---|---|
sydney | Australia |
sao-paulo | Brazil |
dublin | Ireland |
frankfurt | Frankfurt |
tokyo | Japan |
singapore | Singapore |
ashburn | US East Coast (Virginia) |
umatilla | US West Coast (Oregon) |
roaming | Use Twilio's Global Low Latency routing to select the data center with the lowest-latency connection to your user. |
roaming Edge ID is not available for SIP Domains and Elastic SIP Trunking
Looking for Legacy Region IDs like us1, br1?
If you have access to private Interconnect connections, you will also be able to use one of the following values
| Edge ID | Location |
|---|---|
ashburn-ix | US East Coast (Virginia) over Interconnect exchange in Virginia |
san-jose-ix | US West Coast (Oregon) over Interconnect exchange in San Jose |
london-ix | Ireland over Interconnect exchange in London |
frankfurt-ix | Frankfurt over Interconnect exchange in Frankfurt |
singapore-ix | Singapore over Interconnect exchange in Singapore |
tokyo-ix | Tokyo over Interconnect exchange in Tokyo |
sydney-ix | Sydney over Interconnect exchange in Sydney |