IBM Cloud BYOIP Integration Overview
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
| Field | Information |
|---|---|
| Provider Name | IBM Cloud |
| Website | IBM Cloud |
| ASN(s) | AS13884, AS36351 (IBM Cloud / SoftLayer backbone) |
| Regions Supported | BYOIP 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 Contact | IBM Cloud Support Center |
| Tech Article & Date | Bring your own subnet (VPC); Bring Your Own IP Address (solution tutorial) – Dates not specified |
| BYOIP Scope | IPv4-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 Services | VPC 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
| Requirement | Details |
|---|---|
| Prefix Size | IPv4 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 Required | Not 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 Object | Not 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 LOA | ROA 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 Limitations | No 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.
1
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.
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.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees | No 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 Standalone | BYOIP is consumed as part of IBM Cloud networking services (VPC, Direct Link, VPN) rather than as a separate standalone product. |
| Traffic/Peering Restrictions | Direct 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 Limitations | No 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. |