Idle Static IP Address (GCP)
CostLens finds reserved external IPs not attached to any resource — Google bills reserved-but-unused static IPs by the hour.
CostLens finds idle static IP addresses flagged by Google's Recommender — reserved external IPs not attached to any resource. Google bills reserved-but-unused static IPs by the hour, so releasing them removes the cost.
Release is irreversible
Releasing a static IP returns it to the pool — you will not get the same address back. CostLens shows this as an irreversible fix. Keep it if the address is allowlisted downstream or bound to a DNS record.
How it works
Recommender flags idle addresses
Google's Idle Resource Recommender identifies reserved external IPs with no attachment.
CostLens reads them read-only
Using the recommender.viewer + Compute read scopes from GCP Accounts, CostLens ingests each address and its projected saving.
What to do
- Confirm the IP isn't reserved for an allowlist, DNS record, or planned attachment.
- Release it to stop the charge — via CostLens Apply Fix (irreversible) once write access is granted, or in the Cloud Console.
Severity levels
| Severity | Estimated monthly savings |
|---|---|
| critical | >$500 |
| high | $100–$500 |
| medium | $20–$100 |
| low | <$20 |
Required permissions
- Detect:
roles/recommender.viewer+ Compute read — see GCP Accounts. - Apply Fix (release): a write role with
compute.addresses.delete.
Limitations
- Ephemeral IPs (released automatically when a resource is deleted) are not billed when idle and are not flagged; only reserved static IPs are surfaced.