Redundancy in Cloud Router Connections

Due to the way we assign devices for Cloud Router connections, we cannot guarantee redundancy when building connections within the same metro.

However, we still recommend that you follow the best practices recommended by the cloud service provider.

Cloud service provider redundancy


Provision in multiple AWS locations.

See AWS - AWS Direct Connect Resiliency Recommendations and AWS - Using the AWS Direct Connect Resiliency Toolkit to get started.

Google Cloud Platform

Create redundant interconnects.

See Google - Best practices for Cloud Interconnect and High Availability and Redundancy for Google Cloud Interconnect.


Create diversity through BGP.

See High availability and disaster recovery for Direct Link and Models for diversity and redundancy in Direct Link (2.0).

Microsoft Azure

Configure both the primary and secondary connections within the ExpressRoute.

See Microsoft - Designing for high availability with ExpressRoute and High Availability and Redundancy in a Single ExpressRoute Circuit.


Create two separate virtual circuits.

See OCI Docs - FastConnect Redundancy Best Practices and OCI Docs - Connectivity Redundancy Guide.

NAT and IPsec connections

There is no redundancy option for NAT and IPsec connections.

Opening a support ticket

If you want to check whether your connections (that are not using NAT and are not IPsec) are redundant, you can open a support case by emailing and requesting information about whether your connections are using unique devices.

If they are not, in some cases our network engineers will be able to manually move a connection onto a separate device within the same location.