Skip to content

OVHcloud BYOIP Integration Overview

BYOIP SUPPORTER
ASN 16276
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: India, Singapore, France, Germany, Poland, United Kingdom, Canada, United States, Australia

Searching for the best IP providers? OVHcloud offers a Bring Your Own IP (BYOIP) service that lets you import your own public IPv4 ranges and use them as Additional IP blocks across compatible Dedicated, Hosted Private Cloud, and Public Cloud services. Below you’ll find OVHcloud setup docs, BYOIP requirements, benefits, and technical guidance to onboard and manage your custom IP address blocks while preserving your existing routing and reputation.

Provider Details

FieldInformation
Provider NameOVHcloud
WebsiteOVHcloud BYOIP
ASN(s)AS16276 (OVHcloud ASN); optional BYOAS feature lets you include your own ASN in the BGP AS path
Regions SupportedMultiple OVHcloud regions across Europe (PAR, GRA, RBX, SBG, LIM, WAW, ERI), North America (VIN, HIL, BHS, TOR) and Asia-Pacific (SGP, SYD, MUM)
Support ContactOVHcloud Support
Tech Article & DateHow to use the Bring Your Own IP (BYOIP) feature – last updated March 28, 2025
BYOIP ScopeIPv4 only. Import public IPv4 ranges as Additional IP blocks; IPv6 cannot currently be imported via BYOIP.
Supported VersionsIPv4 (no IPv6 BYOIP support at this time)
Supported ServicesDedicated / Bare Metal servers (Failover / Additional IP), Hosted Private Cloud (VMware, Nutanix), Public Cloud instances, and services connected via vRack in supported regions

Technical Requirements

RequirementDetails
Prefix SizeMinimum: /24
Maximum: /19 (ranges are imported as /24 blocks; larger ranges are split into multiple /24s)
ASN Ownership RequiredAn ASN is optional. It is only required if you enable BYOAS. Ownership is proven by inserting an OVHcloud token into the WHOIS object for your AS.
IRR or RADb ObjectA route object in the relevant RIR (ARIN, RIPE NCC, APNIC) must exactly match the imported prefix, with origin set to AS16276 (OVHcloud) or your own ASN (BYOAS).
ROA or LOAROA/LOA are not mandatory for OVHcloud BYOIP. Ownership and authorization are validated via the WHOIS token and route object. RPKI ROAs are recommended and are managed at the RIR level.
RIR LimitationsSupported RIRs: ARIN, RIPE NCC, APNIC (with specific eligible block types). NIR support is experimental; AFRINIC and LACNIC ranges are not currently supported. ARIN/RIPE/APNIC IP blocks can be used in any OVHcloud region.

Step-by-Step BYOIP Process

  • Ownership Verification: Add the OVHcloud-provided token to the WHOIS object for your IPv4 range (and ASN if using BYOAS) via your RIR portal, then wait for validation.
  • Routing Authorization: Create or update a route object for the exact prefix in ARIN/RIPE/APNIC with origin set to AS16276 (OVHcloud) or your own ASN.
  • IP Range Order: Order BYOIP from the OVHcloud Control Panel, selecting the target region (Campus) where the imported range will be used.
  • Delivery & Assignment: Once approved, your range is split into /24 Additional IP blocks that you can assign to eligible services in that region via the Control Panel or IP API.

Cost and Limitations

ItemDetails
FeesBYOIP import itself is positioned as included at no extra cost; standard OVHcloud billing still applies for the underlying services and any Additional IP usage.
Bundled or StandaloneBYOIP blocks are consumed as Additional IP blocks and must be attached to compatible OVHcloud services (Dedicated / Bare Metal, Hosted Private Cloud, Public Cloud, vRack-connected services).
Traffic/Peering RestrictionsEach imported range is tied to a single OVHcloud region; the same block cannot be used in multiple regions at once. Concurrent announcements from other networks (multihoming) are not supported and may cause routing issues.
Other LimitationsIPv4 only (no IPv6 BYOIP). Region (Campus) cannot be changed after delivery. BYOIP has no dedicated SLA; some Additional IP features (such as WHOIS customization) are not available for imported ranges; AFRINIC/LACNIC IP space is not eligible.

Automation & Developer Access

  • API Access: Manage BYOIP ranges via the OVHcloud IP / IPFO API, including assigning, moving, and slicing/aggregating blocks down to /30 or /32.
  • Terraform/SDK: Automation is available through the OVHcloud API, official client libraries, and the community Terraform provider; BYOIP-specific resources are exposed via IP-related endpoints.

Abuse & Reputation Management

  • IP Reputation Monitoring: OVHcloud does not provide native reputation monitoring for imported ranges; customers must monitor RBLs/abuse lists and keep the IP space clean.
  • Blacklist Removal Assistance: Delisting and remediation for blocklisted IPs are handled by the customer; OVHcloud may suspend announcements for ranges with persistently poor reputation.

OVHcloud Bring Your Own IP (BYOIP)
How to use the Bring Your Own IP (BYOIP) feature – OVHcloud Support
Preparing a leased subnet for OVHcloud BYOIP (IPXO 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.