Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Setup Best Practices

Creating a highly available setup

creating-a-highly-available-setup page anchor

To ensure uninterrupted service during maintenance windows and outages, it is strongly advised that you set up your solution to failover to another Twilio Edge location.

Option 2: Failover to a Public Edge Location via the public internet

option-2-failover-to-a-public-edge-location-via-the-public-internet page anchor

Example: Set up a 100-Mbps connection in US East Coast, Ashburn, Virginia (ashburn-ix). In the event of a connection failure via the ashburn-ix edge, the application would retry US West Coast, Oregon public edge (umatilla) or US East Coast, Ashburn, Virginia public edge (ashburn) if connecting via the ashburn-ix edge fails.

Note: If a VPN is used as a backup for Cross Connect, the VPN needs to be a route based VPN with BGP .

Multiple connections in the same location

multiple-connections-in-the-same-location page anchor

By default, Twilio treats two connections with the same type, location, and bandwidth equally when sending traffic to your network. Assuming your routing device doesn't manipulate BGP preferences and your application supports load-sharing, Twilio relies on the BGP multi-path function. This allows both connections to be utilized simultaneously, distributing the traffic across both circuits.

In the event one of the connections fails, Twilio will automatically switch to the remaining functional circuit, directing all the traffic to your network through that circuit. This failover mechanism ensures uninterrupted communication despite the failure of one connection.

Rate this page: