Google Cloud previews Standard Tier for BYOIP IPv4 prefixes

Google Cloud introduced a preview of Standard Tier support for BYOIP on 3 August 2026. The change gives teams evaluating customer-owned IPv4 space another network-tier option, with eligibility and routing design to review before adoption. This is catch-up coverage of the VPC release note, not a general-availability announcement.

What changed

For IPv4 BYOIP v2, the network tier is set on the public advertised prefix, or PAP. Public delegated prefixes and sub-prefixes inherit it. Google's BYOIP overview lists an important size difference: regional Standard Tier PAPs range from /16 through /23, while Premium Tier also accepts /24 PAPs.

An organization holding only a /24 should therefore not assume it can import that block as a Standard Tier PAP. A /24 being usable at another level of the prefix hierarchy does not remove the PAP requirement.

The creation guide documents a beta gcloud workflow with the Standard Tier setting. At the time of research, creating this type of PAP through the console is not supported.

Why it matters for BYOIP

Google describes Standard Tier as using the public internet to reach Google near the destination, while Premium Tier makes greater use of Google's backbone. That distinction makes traffic patterns relevant to the choice; the release alone establishes no particular savings or performance improvement for a given workload.

Our editorial recommendation is to evaluate the preview as a network-design option. Build a comparison around the clients that use the service, the regions serving them and the address blocks you can actually provision. Start with a representative workload and a documented baseline rather than a general assumption about which tier will be better.

The inheritance model also suggests making tier selection explicit in IPAM and provisioning requests. A future operator should be able to see why a prefix was assigned to a particular design without reconstructing the original project discussion.

What to check

• Validate the proposed PAP size before allocating engineering effort to a Standard Tier pilot.
• Review current preview terms, supported resources and the CLI workflow with the team responsible for production support.
• Compare expected billing using current pricing and your own traffic assumptions. Record those assumptions so the comparison can be revisited.
• Measure reachability and application behavior from representative client networks before expanding the pilot.
• Plan the route transition carefully: Google's BYOIP documentation warns against overlapping announcements outside Google. Include a rollback sequence in the change plan.

Sources and further reading

The linked release notes establish the preview date; the two implementation guides establish the current constraints. Our Google Cloud BYOIP profile provides broader onboarding context.