OVHcloud BYOIP Integration Overview
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
| Field | Information |
|---|---|
| Provider Name | OVHcloud |
| Website | OVHcloud BYOIP |
| ASN(s) | AS16276 (OVHcloud ASN); optional BYOAS feature lets you include your own ASN in the BGP AS path |
| Regions Supported | Multiple OVHcloud regions across Europe (PAR, GRA, RBX, SBG, LIM, WAW, ERI), North America (VIN, HIL, BHS, TOR) and Asia-Pacific (SGP, SYD, MUM) |
| Support Contact | OVHcloud Support |
| Tech Article & Date | How to use the Bring Your Own IP (BYOIP) feature – last updated March 28, 2025 |
| BYOIP Scope | IPv4 only. Import public IPv4 ranges as Additional IP blocks; IPv6 cannot currently be imported via BYOIP. |
| Supported Versions | IPv4 (no IPv6 BYOIP support at this time) |
| Supported Services | Dedicated / Bare Metal servers (Failover / Additional IP), Hosted Private Cloud (VMware, Nutanix), Public Cloud instances, and services connected via vRack in supported regions |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | Minimum: /24 Maximum: /19 (ranges are imported as /24 blocks; larger ranges are split into multiple /24s) |
| ASN Ownership Required | An 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 Object | A 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 LOA | ROA/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 Limitations | Supported 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.
1
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.
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.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees | BYOIP 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 Standalone | BYOIP 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 Restrictions | Each 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 Limitations | IPv4 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. |