Understanding Edge Locations
Twilio operates a collection of network edges around the world, called Edge Locations. Edge Locations are the entry and exit points where your application's network traffic connects to Twilio's platform.
How your traffic reaches an Edge Location depends on your connection type:
- REST API (HTTPS): When you send an HTTPS request to the Twilio REST API, Twilio's CDN uses geo-aware DNS to route the request to the nearest Edge Location automatically. You don't choose an edge location. Instead, you select a processing region by using the appropriate hostname.
- Voice SDKs and SIP: When you use Voice SDKs or SIP in your application, it connects to a specific Edge Location. The chosen Edge Location directly influences media latency and call quality.
- Interconnect (private connection): You select a specific Edge Location for guaranteed ingress control. For more information, see the Twilio Interconnect product overview.
This guide covers:
- How Edge Locations work for different connection types (REST API, Voice/SIP, Interconnect)
- How Edge Locations relate to Twilio Regions
- The proper hostname format to ensure your data is processed in the correct region
Info
To see a complete list of available Edge Locations, see the reference page.
Action Required by April 28, 2026
We are making changes to the PRODUCT.REGION.twilio.com domain pattern. The following domains will stop working on April 28, 2026: api.ie1.twilio.com, api.au1.twilio.com, api.br1.twilio.com, api.de1.twilio.com, api.jp1.twilio.com, api.sg1.twilio.com, and api.us2.twilio.com.
Note: api.us1.twilio.com remains valid and will continue to work.
See the API Domain Migration Guide for migration instructions.
Your application connects to Twilio through an Edge Location, which forwards traffic to a Twilio Region for processing. How you reach an Edge Location depends on the connection type:
| Connection type | Example | Edge Location selection |
|---|---|---|
| HTTPS (REST API) | Send an SMS via Programmable Messaging | Automatic — Twilio's CDN selects the nearest edge. The hostname determines your processing region. |
| SIP | Outbound call from your PBX via Elastic SIP Trunking | Configurable — Your SIP endpoint connects to a specific edge, affecting media latency. |
| WebSocket | Connect to a Video Room using a Voice or Video SDK | Configurable — The SDK connects to a specific edge, affecting media quality. |
| Interconnect (private connection) | Dedicated link from your infrastructure to Twilio | Guaranteed — You select the exact edge location. Traffic uses a private connection, not the public internet. |
Twilio's CDN selects the optimal edge location for incoming REST API (HTTPS) requests based on DNS resolution and current network conditions. The edge location label in the FQDN (for example, dublin in api.dublin.ie1.twilio.com) does not guarantee that your request will enter through that edge. Instead, the label specifies the region where Twilio processes the request.
Twilio cannot guarantee the IP address or edge location where REST API traffic will ingress. If you need guaranteed ingress control, use Interconnect to specify the exact edge location and set up a private connection that doesn't use the public internet.
The hostname you use determines where Twilio processes, authenticates, and stores your data. This applies to all connection types (REST API, SIP, SDKs).
US processing (default):
*PRODUCT*.twilio.com
Examples: api.twilio.com, api.us1.twilio.com
Ireland or Australia processing:
*PRODUCT*.*EDGE_LOCATION*.*PROCESSING_REGION*.twilio.com
| Region | Hostname | Example |
|---|---|---|
| Ireland (IE1) | *PRODUCT*.dublin.ie1.twilio.com | api.dublin.ie1.twilio.com |
| Australia (AU1) | *PRODUCT*.sydney.au1.twilio.com | api.sydney.au1.twilio.com |
The edge location name (dublin, sydney) is a required part of the hostname for non-US regions. For REST API requests, it does not control where your traffic enters the network — only where it is processed. For Voice/SIP, the edge location also affects media routing.
Info
Regional processing requires region-specific API credentials. See Manage Regional API Credentials.
Twilio also initiates outbound connections to your applications — for example, webhook callbacks, forwarding calls via Elastic SIP Trunking, or connecting a call to a mobile SDK.
Processing always occurs within a Twilio Region. Outbound traffic exits through an Edge Location optimized for your geographic location. To configure outbound edge behavior, see Webhooks Connection Overrides.
Your application never connects directly to a Twilio Region. Traffic always passes through an Edge Location, which forwards it to the destination Region for processing:
| Leg | Spans | Transport |
|---|---|---|
| Outer | Your application to Edge Location | Public internet (or private Interconnect) |
| Inner | Edge Location to destination Twilio Region | Twilio's internal network |
REST API:
- Using the REST API in a non-US Region — How to target Ireland or Australia for data processing using hostnames and SDK parameters
- API Domain Migration Guide — If you use
api.ie1.twilio.comor similar legacy domains, they stop working April 28, 2026
Voice & SIP (edge location affects media latency):
- Mobile SDKs — Configure edge for iOS and Android Voice SDKs
- JavaScript SDK — Configure edge for browser-based Voice
- SIP endpoint Registration — Edge selection for SIP endpoints
- SIP outbound traffic — Edge selection for outbound SIP
- Voice Failover — Edge failover best practices
- Elastic SIP Trunking — Edge selection for SIP trunks
Webhooks:
- Connection Overrides — Configure which edge Twilio uses for outbound webhook callbacks