NavigationContentFooter
Jump toSuggest an edit
Was this page helpful?

I can't delete my Private Network due to a reserved IPAM IP

Reviewed on 15 May 2025Published on 15 May 2025

You may be attempting to delete a Private Network VPC via the Scaleway console, API, or other developer tool, and see one of the following error messages:

  • resource_still_in_use
  • Detach resources from this Private to delete it
  • Private Network must be empty to be deleted
  • precondition failed: resource_still_in_use

CauseLink to this anchor

If your Private Network has no attached resources (Instances, Elastic Metal servers etc), this error is probably due to a private IP address being reserved for the Private Network in IPAM.

SolutionLink to this anchor

You must release the reserved private IPs from IPAM in order to delete the Private Network.

In the IPAM section of the Scaleway console, use the filters to select the region and VPC of your Private Network. If there are any private IPs reserved for the Private Network, release them.

Tip

If you cannot see any reserved IPs in IPAM, check again that you have correctly used the filters to display reserved IPs for a given region / VPC / Private Network. In the console, IPAM shows only reserved IPs for the selected filters. There is no overview of all reserved IPs across all your Private Networks.

Was this page helpful?
API DocsScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCareers
© 2023-2025 – Scaleway