# Ensure Unassociated Floating IPs Are Released

- Source: https://support.icompaas.com/support/solutions/articles/a_1791826027769645-ensure-unassociated-floating-ips-are-released
- 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 Floating IP addresses that are not attached to any instance or load balancer are released. Floating IPs should exist only while they are in use by a resource.

**Rationale**

Unused Floating IPs cost money and make the list of public addresses harder to review. They can also be attached to a resource by mistake, exposing it to the internet. Releasing unused addresses keeps public exposure under control and reduces cost.

**Impact**

-   Reduces cost and public exposure
    
-   Keeps the list of public IPs easy to review
    
-   A released IP address cannot be recovered
    

**Default Value**

Floating IPs stay in the project until they are deleted, even when not attached.

**Pre-Requisites**

-   Permission to manage the Public Cloud project
    

**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 Public IPs and open the Floating IP tab.
    
4.  Look for Floating IPs that are not attached to any instance or load balancer.
    
5.  If any are found, 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.  In Public IPs, open the Floating IP tab.
    
4.  Confirm the IP is not needed, then open its ⋯ menu and delete it.
    

**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.  Create a new Floating IP if one is needed. The original address cannot be recovered.
    

**Reference**

-   [https://docs.ovhcloud.com/en/guides/public-cloud/network-services/faq](https://docs.ovhcloud.com/en/guides/public-cloud/network-services/faq)

## 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.