BYOIP on Google Cloud
Import a /24 or larger as a public advertised prefix, delegate it to projects and regions, and use the addresses like Google-provided IPs. Google doesn't charge for BYOIP addresses.
What Google Cloud requires
- Prefix size: /16 to /24 for the advertised IPv4 prefix, delegated onwards in blocks down to /28.
- Validation: a ROA and a reverse DNS record that prove you control the range.
- Time: about two weeks to provision a current (v2) prefix. It can't be sped up.
- Regional by default. Global prefixes need allowlisting through a support case; IPv6 is regional only.
- One announcement. The prefix shouldn't be announced elsewhere at the same time.
Where you can use it
Most resources that take a static external IP, including VMs, load balancers and GKE ingress for external Application Load Balancers.
Not supported for GKE nodes and Pods, or as an HA VPN external IP.
Steps
- BlockWe lease or sell you a clean /24 or larger.
- RegistryWe set up the ROA and the reverse DNS record for validation.
- ProvisionYou create the advertised prefix and delegate it to projects.
- AnnounceYou decide when Google starts announcing it.
What a /24 costs per month
Google external IPv4
$934
$0.005 per IP-hour × 256
Leased /24 via BYOIP
$97
RIPE rate, $0.38 per IP
You save
$10,045 / yr
About 90% less
Google price for external IPs in use on standard VMs, checked October 2026; unused static IPs cost $0.01 per hour. Google doesn't charge for idle or in-use BYOIP addresses.
Planning BYOIP on Google Cloud?
Start early: provisioning takes weeks. Tell us the region and size.