Skip to main content
Google Cloud charges for a reserved static external IP address while it is not in use by a running VM or load balancer. nOps finds addresses that have been billed this idle-address charge every day for two weeks, and shows that charge as the saving from releasing them.

Why it matters

Static IPs are often reserved for a VM or load balancer that was later deleted, and then keep billing quietly for months.

How nOps finds it

Google bills the ‘Static Ip Charge’ only for reserved addresses that are not in use. nOps flags an address when that charge was billed on all of the last 14 days and in the last 2 days. The saving is the address’s charges over the last 7 days, scaled to a month, net of discounts and excluding credits, and must be at least $5 a month. Projects whose spend on the service is at least 90% paid by credits or promotions are left out.

Before you start

Confirm the address is not kept for a DNS record, allow list or resource you plan to recreate.

How to implement

  1. In the console, open VPC network → IP addresses and find the address. The In use by column is empty for an idle address.
  2. Check DNS records, partner allow lists and firewall rules that refer to the address.
  3. Release it: gcloud compute addresses delete ADDRESS_NAME --region=REGION (or --global for a global address).
  4. Remove it from Terraform so it is not reserved again.

Risks and considerations

  • A released address goes back to Google’s pool. You cannot get the same address back.
  • If a partner allow-lists the address, releasing it will break that access when you later need it.

FAQs

Yes. A stopped VM does not count as using the address, so Google bills the idle-address charge and nOps can flag it.