Skip to content

Diversity in Google Connections

Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure.

Google Cloud and Megaport simplify the deployment of diverse connections by establishing multiple domains (1 and 2) within each metro. Each domain is physically separated on Megaport edge devices and connected to diverse Google devices. During Megaport scheduled maintenance, no more than one domain within a data center will experience downtime at any moment. Whenever possible, diverse services have maintenance periods scheduled for different days.

Each Google Cloud destination port indicates its domain using “zone1” or “zone2” in the Megaport Portal.

Azure zones

To create diverse connections, you need to create two connections: one connection for each Google Cloud destination port. This figure shows the approach of using VXCs to diverse Google Cloud ports.

Diversity zone connections

For end-to-end diversity, the connections must be on diverse ports at both ends. In other words, truly diverse VXCs can only exist between two pairs of diverse ports. This figure shows a fully redundant solution with VXCs from different physical locations using diverse ports.

Redundant diversity zones

The preferred diversity method deploys connections in different Megaport locations. This offers the most redundancy and protection.


Last update: 2024-02-01