Skip to content

Google Cloud BYOIP Integration Overview

BYOIP SUPPORTER
ASN 396982
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Iowa, South Carolina, Northern Virginia, Columbus, Dallas, Oregon, Los Angeles, Salt Lake City, Las Vegas, Canada, Brazil, Chile, Belgium, United Kingdom, Germany, Netherlands, Switzerland, Italy, Poland, Finland, Spain, Israel, Qatar, Saudi Arabia, India, Singapore, Indonesia, Taiwan, Hong Kong, Japan, South Korea, Australia, South Africa

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Google Cloud infrastructure.

Searching for the best IP providers? Google Cloud delivers robust BYOIP automation, IP reputation management, and enterprise-grade availability. Below you’ll find Google Cloud setup docs, requirements, reviews, pricing, and benefits for streamlining your BYOIP configuration.

Provider Details

FieldInformation
Provider NameGoogle Cloud
WebsiteGoogle Cloud
ASN(s)396982
Regions SupportedAll global regions. IPv6 BYOIP is regional only.
Support ContactVia Google Cloud Console
Tech Article & DateBring your own IP addresses – October 2024
BYOIP ScopeGlobal for IPv4; regional for IPv6
Supported VersionsIPv4 and IPv6 (limited services)
Supported ServicesVMs, Load Balancers, VPN, Global Load Balancing, Cloud NAT, Cloud CDN

Technical Requirements

RequirementDetails
Prefix SizeIPv4: /16 to /24 (advertised), /16 to /28 (delegated)
IPv6: /48 (advertised), /32 to /56 (delegated)
ASN Ownership RequiredNo; must authorize ASN 396982
IRR or RADb ObjectNot required
ROA or LOAROA required
RIR LimitationsSupports ARIN, RIPE, APNIC, LACNIC, AFRINIC

Step-by-Step BYOIP Process

Estimated Setup Time: Up to 4 weeks

Tested By Us: Not tested

Preparation

  • Create ROA authorizing ASN 396982
  • Create PTR record pointing to a hostname provided by Google Cloud

Provisioning

  • Use Google Cloud Console or gcloud CLI to create a Public Advertised Prefix (PAP)
  • Specify IP range and verification IP

Validation

  • Google verifies ROA and PTR
  • Typically completed in a few minutes

Delegation

  • Create Public Delegated Prefixes (PDPs) from PAP
  • Use PDPs in your projects

What are PAP and PDP?

In Google Cloud BYOIP, once you import your IP block, it’s registered as a Public Advertised Prefix (PAP). From that, you can carve out smaller Public Delegated Prefixes (PDPs) to assign to specific VPCs or projects.

For example, if your imported block is 192.168.1.0/24 (PAP), you can split it into:

  • 192.168.1.0/25 – assignable to one VPC or project
  • 192.168.1.128/25 – assignable to another

This structure lets you control how portions of your BYOIP range are used within your infrastructure.

Usage

  • Assign IPs from PDPs to VMs, Load Balancers, etc.

Propagation Notes:

  • ROA propagation: up to 24 hours
  • PAP provisioning: approx. 4 weeks
  • PDP creation: a few minutes

Cost and Limitations

ItemDetails
FeesNo extra charges; standard Google Cloud rates apply
Bundled or StandaloneIntegrated with VPC networking services
Traffic/Peering RestrictionsClean reputation required; poor IPs may be rejected
Other LimitationsIPv6 BYOIP limited to regional passthrough NLB; not all services support BYOIP

Automation & Developer Access

  • API Access: Yes (gcloud CLI and REST API)
  • Terraform / SDKs: Partial; some features require CLI

Abuse & Reputation Management

  • IP Reputation Monitoring: Not provided (use third-party tools)
  • Blacklist Removal Support: Not offered (user responsibility)

Additional Notes

  • Before terminating your Google Cloud account (tenant), ensure all services using BYOIP addresses are manually canceled.
  • After cancellation, confirm that your IP prefix is no longer advertised via public BGP.
  • If the prefix remains advertised after termination, it may continue to persist on the internet without your control.
  • Only Google Cloud Support can withdraw these announcements post-termination, and without an active account, this may take several weeks or even months.

Google Cloud BYOIP Documentation
Google Cloud CLI (gcloud)
IPXO Setup Guide

FAQ

BYOIP, or Bring Your Own IP, is a service that enables organizations to bring their own public IP addresses—whether owned outright or leased from an IP provider—into a service provider’s network infrastructure. Instead of relying on IP addresses assigned by the provider, BYOIP allows businesses to retain control over their IP resources. This ensures continuity, particularly for organizations with established IP-based reputations, branding, or dependencies on specific address blocks. IP providers can assist in streamlining this process, making it easy to integrate your IPs into the desired network environment.

BYOIP offers several compelling advantages. By using your own IPs, you can maintain continuity in your network’s identity, reduce the risk of disruptions to email deliverability or service recognition, and avoid reputational concerns associated with shared IPs. Additionally, BYOIP provides enhanced flexibility and control over your IP resources.

BYOIP is ideal for organizations that either own public IP addresses or lease them from a trusted IP provider with explicit BYOIP support. This includes enterprises, cloud providers, content delivery networks (CDNs), and businesses with compliance requirements or IP reputation needs. Working with a reputable IP provider ensures that leased IPs can be seamlessly integrated into another provider’s infrastructure without ownership concerns.

You must either legally own the IP addresses or have explicit authorization from a leasing IP provider to route and manage them. IP providers who offer BYOIP-ready IP addresses simplify this process, providing documentation and support to ensure compliance with regional internet registry (RIR) policies and service provider requirements. This collaboration ensures smooth implementation without any legal or operational issues.

To use BYOIP, you’ll typically need to present documentation verifying your authority over the IP block. This can include official records from a regional internet registry (RIR) such as ARIN, RIPE NCC, or APNIC. If you are leasing IPs, the IP provider should supply proof of their ownership and grant you permission for BYOIP. Providers that specialize in IP leasing often handle this paperwork for you, reducing administrative burden and ensuring compliance.

Yes, BYOIP is designed to be a secure and reliable solution. Reputable service providers and IP providers implement robust safeguards to prevent unauthorized use or hijacking of IP addresses. Security measures include BGP filtering, route validation, and advanced protocols like Resource Public Key Infrastructure (RPKI). By collaborating with a trusted IP provider, businesses can benefit from additional layers of protection, ensuring that only authorized traffic is routed through their IP blocks.

The setup process for BYOIP varies by provider, typically taking anywhere from a few hours to a few days. Factors include the complexity of your network, the verification process for IP ownership or authorization, and the time needed for global BGP route propagation. IP providers often expedite the preparation and validation stages, ensuring a smooth and timely integration into the desired infrastructure.

Absolutely. Many providers, in partnership with IP providers, support routing IPs across multiple data centers or geographic regions. This feature optimizes performance for global businesses by reducing latency and improving service availability. When working with an IP provider, you can also ensure that your leased or owned IPs are aligned with your geographic requirements for compliance and efficiency.

If you choose to discontinue BYOIP with a provider, your IP addresses will be released from their network, and routing will cease. You can then reallocate these IPs for use with a different service provider or project.