OVHcloud Connect - PoPs and Regions
Understand how OCC works with PoPs and Regions, and find out which ones are the most suitable for your infrastructure
Introduction
When setting up OVHcloud Connect, you choose one or more Points of Presence (PoP) as the hand-off point between your network or your provider's network, and OVHcloud. Each PoP is tied to a specific geographic zone; consequently, it can only access OVHcloud regions within that same zone.
This guide explains how OVHcloud PoPs and regions interact with OVHcloud Connect, and provides a framework for selecting the most suitable PoP for your specific infrastructure needs.
Understanding Regions and PoPs
Regions
OVHcloud organises its infrastructure into regions — geographical areas where data centres and services are hosted. Each region may contain one or more PoPs where OVHcloud Connect is available.
Points of Presence (PoP)
OVHcloud PoPs are located inside major carrier-neutral datacenters managed by our partners. If you are ordering a Direct connection, you need to be present (or arrange a circuit) in the same datacenter to install a cross-connect.
If you are using a Provider, the provider handles the physical connectivity and may reach the PoP from a different facility.
OVHcloud regularly adds new locations. Always check the OVHcloud Connect webpage for the most up-to-date list.
How to choose a PoP
When selecting a PoP for your OVHcloud Connect service, consider the following:
1. Proximity (latency)
Choose the PoP that is geographically closest to your infrastructure to minimise network delay. For example, if your data centre is in Paris, a French PoP will provide the lowest latency.
2. Provider availability
If you are using OVHcloud Connect Provider, verify that your chosen provider has a presence at the PoP. Not all providers are available at every PoP.
3. Redundancy
For high-availability architectures, select two PoPs in different locations so that a single site failure does not take down your connection. Follow one of the resilient architecture tutorials for details:
4. Regulatory / data residency requirements
Some industries or countries require data to stay within a specific geography. Choose a PoP and region that comply with your data residency obligations.
5. Target OVHcloud region
To ensure the best performance, your OVHcloud Connect service should terminate in the region where your OVHcloud workloads are running (or will run). Verify that the PoP serves the region you need.
PoP and Region Mapping Tables
The following tables list the regions accessible from each PoP, the corresponding low-latency OVHcloud region, and the available OCC Direct bandwidth, by geographic zone:
PoP / Low-latency Region Mapping Table
What's next?
- Understand Multi-AZ for resilient architectures
- Review Configure OCC L3 with BGP for technical setup
Go further
For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analyzed by our experts.
Join our community of users.