Skip to content

IBM Cloud BYOIP Integration Overview

BYOIP SUPPORTER
ASN AS13884, AS36351 (IBM Cloud / SoftLayer backbone)
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: Japan, Germany, Spain, United Kingdom, Canada, United States, Brazil, Australia

This landing page provides detailed information for integrating Bring Your Own IP (BYOIP) with IBM Cloud infrastructure, with a focus on Virtual Private Cloud (VPC) environments and hybrid connectivity patterns.

Searching for the best IP providers? IBM Cloud lets you bring your own IPv4 address ranges into VPC by defining custom address prefixes and subnets and connecting them to on-premises networks through VPN and Direct Link. Below you’ll find IBM Cloud setup documentation, BYOIP requirements, benefits, and cost details to help you securely onboard and manage your custom IP address ranges.

Provider Details

FieldInformation
Provider NameIBM Cloud
WebsiteIBM Cloud
ASN(s)AS13884, AS36351 (IBM Cloud / SoftLayer backbone)
Regions SupportedBYOIP supported in IBM Cloud VPC regions globally, including locations in the United States, Canada, Brazil, United Kingdom, Germany, Spain, Japan, Australia and other IBM Cloud markets
Support ContactIBM Cloud Support Center
Tech Article & DateBring your own subnet (VPC); Bring Your Own IP Address (solution tutorial) – Dates not specified
BYOIP ScopeIPv4-only. VPC bring your own subnet (public and private IPv4 ranges) and overlay-based BYOIP patterns for Classic and hybrid connectivity; IBM Cloud does not currently provide a public edge announcement service for customer prefixes.
Supported ServicesVPC address prefixes and subnets for virtual server instances and bare metal servers; integration with VPN gateways, Direct Link, Transit Gateway and virtual appliances. Public internet access continues to use IBM-assigned floating IPs and public gateways.

Technical Requirements

RequirementDetails
Prefix SizeIPv4 CIDR ranges used as VPC address prefixes and subnets; IBM documentation does not define extra BYOIP-specific minimum or maximum beyond standard VPC subnet limits.
ASN Ownership RequiredNot required for VPC bring your own subnet, because IBM Cloud does not originate your prefixes; ASN ownership and routing policy are handled on your own edge or with upstream providers.
IRR or RADb ObjectNot enforced by IBM Cloud for VPC overlays; IRR and RPKI objects are recommended and usually required by your internet transit providers when you publicly advertise your ranges.
ROA or LOAROA recommended with your RIR for public routing. IBM typically requests proof of IP ownership (for example an LOA and RIR records) only when configuring customer-owned subnets or special networking engagements through IBM Support.
RIR LimitationsNo IBM-documented restrictions by RIR; Direct Link BYOIP is limited to non-overlapping RFC1918 private address space, while public IANA-registered prefixes remain under your own routing control.

Step-by-Step BYOIP Process

  • Create a VPC: Create an IBM Cloud VPC in the target region and, if needed, set address prefix management to manual so you can fully control the CIDR ranges.
  • Define Address Prefixes: For each zone where you plan to deploy workloads, create one or more address prefixes using your own IPv4 ranges (RFC1918 or public) that do not overlap with existing networks.
  • Create Subnets: Create subnets within each zone that use ranges inside the address prefixes you defined and attach them to your virtual server instances and appliances.
  • Configure Connectivity and Routing: Attach VPN or Direct Link connections, Transit Gateway and any virtual routers, then add custom routes and NAT or overlay patterns according to the IBM BYOIP tutorial.

Cost and Limitations

ItemDetails
FeesNo separate charge for bringing your own addresses; you pay normal IBM Cloud charges for VPC resources, Direct Link or VPN connectivity and data transfer.
Bundled or StandaloneBYOIP is consumed as part of IBM Cloud networking services (VPC, Direct Link, VPN) rather than as a separate standalone product.
Traffic/Peering RestrictionsDirect Link 2.0 supports BYOIP for non-overlapping RFC1918 ranges between on-premises and VPC networks; Direct Link on Classic has no BYOIP support. BYOIP ranges in VPC behave as private addresses, so public internet access must use IBM-assigned floating IPs or public gateways instead of your own prefix.
Other LimitationsNo managed public-edge prefix announcement comparable to hyperscaler BYOIP services; BYOIP on IBM Cloud focuses on private addressing and overlay patterns. Some Classic services and global IP features cannot directly use customer prefixes.

Automation & Developer Access

  • API and CLI Access: Full automation via IBM Cloud CLI and REST APIs for VPC address prefixes, subnets, gateways and Direct Link resources.
  • Terraform and SDKs: Supported through the official IBM Cloud Terraform provider and language SDKs for codifying BYOIP networking patterns.

Abuse & Reputation Management

  • IP Reputation Monitoring: No native, provider-managed BYOIP reputation scoring; customers should use RIR tools, IP brokers or third-party reputation services.
  • Blacklist Removal Assistance: IBM Cloud expects customers to manage abuse handling and delisting for their own prefixes, working directly with blocklist and RBL operators.

IBM Cloud VPC – Bring your own subnet
IBM Cloud BYOIP solution tutorial
IPXO BYOIP Overview

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.