Lease IPv4 for Google Cloud BYOIP
If you use many public IPs in Google Cloud, BYOIP can change the cost model. Google says imported addresses are not billed while idle or in use, so leasing a block can be a simple way to lower recurring spend and keep your own range without buying it outright.
Savings per /24
1 month
$716.80
12 months
$8601.60
Google Cloud BYOIP workflow
Create and verify the PAP
Add your range as a public advertised prefix. For external BYOIP, Google checks ownership with ROA and reverse DNS. In the recommended regional v2 path, Google lists PAP provisioning at about two weeks.Delegate the range to the target project
Create one or more public delegated prefixes and assign each block to a project and scope. For regional v2, Google says delegated prefixes are ready in a few minutes and can be split into smaller blocks.Announce the prefix and assign the IPs
For regional v2, the prefix is not announced automatically after provisioning, so you choose when to announce it. Do not keep the same prefix or sub-prefix announced outside Google at the same time, then create IPv4 addresses for supported resources.
Live Estimate
BYOIP savings calculator
See cloud IPv4 cost vs. leased BYOIP
USD
Public IPv4 estimate
$3.20
/ IP / mo
Google Cloud
Public IPv4 pricing
1 month
$819.20
12 months
$9830.40
IPv4 Online
1 month
$102.40
12 months
$1228.80
Savings
1 month
$716.80
12 months
$8601.60
Estimates use public list pricing and a benchmark lease rate for directional comparison only.
Google Cloud BYOIP is most useful when address planning matters
Use case 01
Public GCP services are large enough to budget separately
Once Google Cloud is fronting a meaningful number of public endpoints, teams start treating IPv4 as its own cost line. BYOIP gives them a cleaner model to compare against provider-assigned addresses.
Use case 02
Projects and regions need their own IP pools
PAP and delegated prefixes are a better fit when different projects, environments, or regions should have clearly separated public ranges instead of sharing one growing pool.
Use case 03
Traffic is moving into Google Cloud in stages
BYOIP works well for phased migrations because you can prepare the prefix, delegate the space to the target project, and cut services over without renumbering everything at once.
Frequently asked questions
Why use leased IPv4 for Google Cloud BYOIP?
Google Cloud says imported BYOIP addresses are not billed while idle or in use. If you already need a public block, leasing can be a practical way to compare that model with ongoing provider-assigned IP spend.
Do I need to buy a block for Google Cloud BYOIP?
No. Many teams lease first when they want their own range in Google Cloud now and do not want to make a large upfront purchase.
What block sizes does Google Cloud BYOIP support?
Google Cloud lists IPv4 public advertised prefixes from /16 to /24. In the recommended regional v2 setup, delegated prefixes can go down to /28. Many teams still start with a /24, but the right size depends on the rollout.
Need leased IPv4 for Google Cloud BYOIP?
Tell us how many public IPs you plan to use in Google Cloud. We will help you compare lease pricing with the cost of staying on provider-assigned addresses.