# Ensure Private Subnet Ranges Do Not Overlap

- Source: https://support.icompaas.com/support/solutions/articles/a_1791826027143485-ensure-private-subnet-ranges-do-not-overlap
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [OVH Cloud](https://support.icompaas.com/support/solutions/c_1791819364512367) › [checks](https://support.icompaas.com/support/solutions/folders/f_1791819376721251)
- Last updated: 2026-10-12
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure the private subnets created in the project's private networks use IP address ranges (CIDRs) that do not overlap with each other, or with networks they will be connected to, such as on-premises networks, VPNs, or other projects on the same vRack.

**Rationale**

Overlapping address ranges cause routing conflicts, so traffic may go to the wrong network or fail completely. This can break connectivity, make firewall rules unreliable, and prevent future connections between networks. Planning unique ranges avoids outages and keeps network rules predictable.

**Impact**

-   Routing between networks works correctly
    
-   Avoids connectivity outages
    
-   Changing a subnet range may require recreating the network and its resources
    

**Default Value**

OVHcloud does not prevent you from creating subnets with overlapping ranges in different networks.

**Pre-Requisites**

-   Permission to manage the Public Cloud project
    
-   A network address plan
    

**Test Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  In the left-hand menu, under Network, select Private Network and review the subnet ranges of each private network and region.
    
4.  Compare them with each other and with connected networks.
    
5.  If any ranges overlap, follow the implementation steps.
    

**Implementation Steps**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  Create a new private network with a non-overlapping subnet range.
    
4.  Move the affected resources to the new network.
    
5.  Delete the old network once it is empty.
    

**Backout Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  Move the resources back to the original network and delete the new one.
    

**Reference**

-   [https://help.ovhcloud.com/csm/en-public-cloud-compute-control-panel?id=kb\_article\_view&sysparm\_article=KB0050405](https://help.ovhcloud.com/csm/en-public-cloud-compute-control-panel?id=kb_article_view&sysparm_article=KB0050405)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.