Docs Playbook

Network Unused IP Addresses

Release idle public IPs and recover recurring network spend.

Elastic, floating, and reserved IP addresses often remain allocated after service changes.

Network settings and proxy configuration used during connectivity validations.
Use this playbook with scan results, owner validation, and export evidence.

Detection Signals

  • Public IP allocations not attached to active resources.
  • No inbound/outbound traffic over lookback period.
  • No documented dependency in runbooks or owner tags.

Execution Steps

  1. Correlate IP allocations with active services.
  2. Release unused addresses in controlled batches.
  3. Monitor external traffic/alerts after release.
  4. Capture released address count and savings impact.

Provider Differences

Provider Group Operational Notes
AWSUnassociated Elastic IPs.
Azure/GCPUnused public/external IP allocations.
OpenStack/OVH/ScalewayFloating or reserved IP drift.
Tencent/Alibaba/HuaweiEIP pools with stale assignments.

Share

Pass the cleanup path to the next reviewer

Send the same remediation steps to engineering, finance, or the owner who needs to sign off.

Next Step

Run a focused scan, validate owners, then export evidence for approval and execution.

Save your first $1,000 before the next billing cycle.

Download Trial View Pricing