Edge Locations
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.
What Twilio products support Edge Locations?
| Product | Documentation |
|---|---|
| Programmable SMS | API |
| Notify | API |
| Programmable Voice | API, Sending SIP & Receiving SIP |
| Programmable Voice SDK | Mobile SDK & Client JS SDK |
| Elastic SIP Trunking | API & Trunking |
| HTTP Callback (Webhooks) | HTTP Callbacks (Webhooks) |
Public Edge Locations
| 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. |
umatilla Edge Location is not available for Client
roaming Edge ID is not available for SIP Domains and Elastic SIP Trunking
Looking for Legacy Region IDs like us1, br1?
Private Interconnect
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 |
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.