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.
Example: Set up a 100-Mbps connection in Ashburn, Virginia (ashburn-ix) and a 100-Mbps connection in San Jose, California (san-jose-ix) to create redundant connections to Twilio on both coasts of the United States. In the event of a failure at the private edge ashburn-ix, the application would retry another private edge san-jose-ix. Similarly, for redundancy in Europe and Asia Pacific, leverage our exchanges in London, Frankfurt, Singapore, Tokyo and Sydney.
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 .
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.