# Regional IP Address

> A reserved regional external IP bills by the hour whenever it is not attached to a running resource, making orphaned reservations pure waste. ZopNight discovers every regional address via Cloud Asset Inventory, checks its attachment state, and flags unattached reservations as immediate cleanup candidates in its recommendations.

Source: https://zop.dev/integrations/gcp/gcp-address
Updated: 2026-08-19

---

A reserved regional external IP address provides a stable endpoint for VMs and load balancers. Google charges for reserved addresses that are not attached to a running resource, making orphaned IPs pure waste.

## The hourly meter on a reserved regional IP

The billing logic on a regional address inverts the usual cloud pattern: you pay for it when it is doing nothing. An address attached to a running VM or forwarding rule serves traffic and, depending on the attachment, costs little or nothing extra; the same address sitting reserved but unattached accrues an hourly charge for holding a scarce IPv4 number out of the pool. The meter never grows with usage and never stops on its own. An orphaned reservation from a deleted VM keeps producing the identical line item every month until someone releases it.

## Attachment state is the whole story

Because the charge hinges entirely on whether the address is in use, the only fact an audit needs per address is its attachment. ZopDev discovers reserved addresses via Cloud Asset Inventory and flags unattached addresses as immediate cleanup candidates in recommendations. There is nothing to schedule here, because an IP has no on and off state a scheduler could toggle. The entire savings motion is detection followed by a release decision.

## Regional address waste patterns ZopNight surfaces

Two patterns account for most of the waste. First, teardown leftovers: a VM is deleted, but the static address that was promoted from its ephemeral IP survives the deletion and begins billing as unattached. Second, just-in-case reservations: addresses reserved for a migration or a firewall allowlist that never happened, held for months on the theory that releasing them is risky. The risk is real only if external systems (DNS records, partner allowlists) still reference the address, which is exactly what should be checked before release rather than a reason to keep paying indefinitely.

## Reviewing regional IPs in the console

Google Cloud console → VPC network → IP addresses lists every reservation with a Region column and an In use by column. Filter to external addresses and sort by In use by: every row showing no attachment is billing hourly for holding a number.