--- title: "How to use the Bring Your Own IP feature" description: "Import your own IPv4 and IPv6 ranges into OVHcloud with Bring Your Own IP (BYOIP), and use them as Additional IPs on your OVHcloud services" url: https://docs.ovhcloud.com/pl/guides/network/ip-addresses/bring-your-own-ip/bring-your-own-ip lang: en lastUpdated: 2026-11-12 --- > For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/pl/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/pl/llms-full.txt. # How to use the Bring Your Own IP feature ## Objective The [Bring Your Own IP (BYOIP)](https://www.ovhcloud.com/pl/network/byoip/) feature allows you to use IPv4 and IPv6 address ranges that you already own, as Additional IPs directly on the OVHcloud network and products. - **IPv4 ranges** are imported in the form of /24 IP blocks, and behave like a regular OVHcloud [Additional IP](https://www.ovhcloud.com/pl/bare-metal/ip/) block product. - **IPv6 ranges** are imported as a single range. You then create /56 IP blocks inside it, which behave like Additional IPv6 blocks. ## Requirements ### Supported RIRs and WHOIS types A [Regional Internet registry](https://en.wikipedia.org/wiki/Regional_Internet_registry) (RIR) is an organization that manages IP addresses in a given region. Your IP range must be registered with one of these RIRs: - [ARIN](https://www.arin.net/) - [RIPE](https://www.ripe.net/) - [APNIC](https://www.apnic.net/) (support for National Internet Registries - NIRs - is experimental at the moment) AFRINIC and LACNIC ranges and AS numbers are not supported at the moment. ARIN, RIPE and APNIC ranges can be used in any OVHcloud region. The WHOIS record of the range **must precisely match the range you import**: with a parent or child block, you will not be able to use the range. The range must have one of the following types in the WHOIS: | RIR (WHOIS field) | IPv4 | IPv6 | More information | | :-------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ARIN (_Network type_) | • Direct Allocation
• Direct Assignment
• Reallocated
• Reassigned | Same as IPv4 | • [Using WhoIs - Network](https://www.arin.net/resources/registry/whois/#network)
• [Reporting Reassignments](https://www.arin.net/resources/registry/reassignments/) | | RIPE (_status_) | _inetnum_ object:
• ALLOCATED PA
• LIR-PARTITIONED PA
• SUB-ALLOCATED PA
• ASSIGNED PA
• ASSIGNED PI
• LEGACY | _inet6num_ object:
• ALLOCATED-BY-RIR
• ALLOCATED-BY-LIR
• AGGREGATED-BY-LIR
• ASSIGNED
• ASSIGNED PI

_ASSIGNED ANYCAST_ is not accepted, as BYOIP does not support anycast. | • [Description of the INETNUM Object](https://docs.db.ripe.net/RPSL-Object-Types/Descriptions-of-Primary-Objects/#description-of-the-inetnum-object)
• [Description of the INET6NUM Object](https://docs.db.ripe.net/RPSL-Object-Types/Descriptions-of-Primary-Objects/#description-of-the-inet6num-object) | | APNIC (_status_) | • Allocated-Portable
• Allocated-Non-Portable
• Assigned-Portable
• Assigned-Non-Portable | Same as IPv4 | • [INETNUM Quick Guide](https://www.apnic.net/manage-ip/using-whois/guide/inetnum/)
• [Recording network assignments](https://www.apnic.net/manage-ip/using-whois/updating-whois/network-assignments/) | ### Supported sizes | | Accepted sizes | What you get | | :------- | :----------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **IPv4** | /24 to /19 | One /24 block per /24 of the range: 1 for a /24, 2 for a /23, 4 for a /22, 8 for a /21, 16 for a /20, 32 for a /19. | | **IPv6** | /48 to /32, with a prefix length that is a multiple of 4 (/32, /36, /40, /44 or /48) | No block at delivery: you create /56 blocks yourself, one by one (see [Use an IPv6 range](#ipv6-blocks)). The range can hold 256 /56 blocks for a /48, 4,096 for a /44, 65,536 for a /40, 1,048,576 for a /36 and 16,777,216 for a /32. | Smaller ranges are not accepted. Bigger ranges are not accepted at the moment, but feel free to contact us to discuss this. ### Quotas The following quotas apply to every OVHcloud account, and cannot be increased at the moment: - **Imported ranges:** you can import an IPv6 range into a region only if you hold fewer than 5 imported ranges (IPv4 and IPv6 combined) in that region. For example, with 5 IPv4 ranges in a region, you cannot import an IPv6 range there. IPv4 imports are not limited. - **IPv6 blocks:** you can create up to 80 /56 blocks in each imported IPv6 range. ### Region A region can be viewed as a list of datacenters where an IP can be used. The available regions are displayed on the [Bring Your Own IP product page](https://www.ovhcloud.com/pl/network/byoip/). You choose one region when you order. Once the delivery is done, you can move any block of the imported range to any eligible OVHcloud service in that region. An imported range can only be used in that one region, and its region cannot be changed: to change it, cancel the service and order it again. **Exception for IPv4:** if you chose the Gravelines, Roubaix or Strasbourg region and ordered the service after January 1st, 2023, you can move your **/24** blocks across those 3 regions (and only those 3). Blocks smaller than a /24 (after [slicing](#range-slicing)), and /24 blocks re-aggregated after a previous slicing, cannot be moved across them. This exception does not apply to IPv6 ranges. ### Proof of ownership To prove that you own the IP range, and the AS number if you announce the range from your own AS, add the token displayed in the order form to the public WHOIS objects of the range (and of the AS number, if applicable), from your RIR's web portal. The token may also be found in the OVHcloud Console, in the IP section. Use the same token for the IP range and the AS number. They can be managed by different RIRs. | RIR | IP range | AS number | | :---- | :-------------------------------------------------------------------------------------- | :---------------------------------------------- | | RIPE | **descr** field of the **inetnum** object (IPv4) or of the **inet6num** object (IPv6) | **descr** field of the **aut-num** object | | ARIN | **Public Comments** field of the **Network** object | **Public Comments** field of the **ASN** object | | APNIC | **remarks** field of the **inetnum** object (IPv4) or of the **inet6num** object (IPv6) | **remarks** field of the **aut-num** object | The token must be on its own line in the field. Other lines may be present. Add it before placing the order, and do not remove it until the end of the delivery process. ### Route object To allow OVHcloud to announce your IP range, create a **route object** (IPv4) or a **route6 object** (IPv6) for the range on its RIR, matching the range exactly, with the OVHcloud **AS number** (`AS16276`) or your own AS number in its **origin** field. For more information, refer to your RIR's documentation: - RIPE - [Managing Route Objects](https://docs.db.ripe.net/Authorisation/Protection-of-Route-Object-Space/) - ARIN - [Submitting Routing Information](https://www.arin.net/resources/manage/irr/#submitting-routing-information) - APNIC - [Creating Route Objects](https://www.apnic.net/manage-ip/using-whois/guide/creating-route-objects/) > \[!TIP] > We also recommend creating an RPKI ROA (Route Origin Authorisation) for your range, with the same origin AS. OVHcloud does not check ROAs at the moment. ### Announcement elsewhere and reputation Your range should not be announced or in use on the Internet (no BGP announcement on any public network). **Warning:** If your range is already announced on the Internet from sites other than OVHcloud (multihoming case), you risk packet loss or other routing issues: OVHcloud cannot guarantee connectivity to OVHcloud services with your range, nor provide support for it. You can order the service while your range is still announced from another site, but you must stop that announcement as soon as the service is delivered. Otherwise, OVHcloud cannot be held responsible for connectivity issues with your services hosted at OVHcloud. We may refuse IP ranges or AS numbers with a bad reputation, and we reserve the right to stop announcing them if their reputation has a negative impact on OVHcloud's reputation. *** ### OVHcloud Console Access - **Direct link:** "IP addresses" - **Navigation path:** "Bare Metal Cloud" > "Network" > "IP addresses" *** ## Instructions ### Order a BYOIP service 1. Click "Order an IP" at the top of the page, then select "Bring your own IP (BYOIP)". You are taken to the BYOIP configuration page. 2. Select the **IP version** of the range: **BYOIPv4** or **BYOIPv6**. 3. Select the **RIR** that manages the range, then the **region** where you want to use it. 4. Copy the **token** displayed on the page and add it to the WHOIS objects of your range and, if applicable, of your AS number (see [Proof of ownership](#proveownershipip)). 5. Enter the range in CIDR notation (see [Supported sizes](#supportedsize)). 6. Choose the AS that will announce your range: - **OVHcloud AS** (recommended): OVHcloud announces your prefix from AS16276. No additional information is required. - **Own AS**: your prefix is announced from your own AS number (BYOAS). Select the RIR that manages your ASN, then enter your AS number. 7. Click "Next". In the confirmation window, check that all the [requirements](#requirements) are met, then click "Confirm" to submit your order. ### View your imported ranges Open the `BYOIP Ranges ` tab of the IP addresses page. The table lists your imported ranges with their region, origin AS, RIR AS and RIR. Use the `IPv4 ` and `IPv6 ` buttons above the table to filter the ranges by IP version. To list the IP blocks of a range, click the `⋮ ` button to the right of the range, then select `View IP blocks `. The steps below start from this list. All the IP blocks obtained from your imported ranges have the `BYOIP` tag, which differentiates them from your other Additional IPs. ### When your range is announced OVHcloud announces your imported range on the Internet only while **at least one of its IP blocks is routed to a service**. When all its blocks are in the parking area, OVHcloud stops announcing the range. ### Use an IPv4 range An imported IPv4 range is split into /24 blocks, which behave like the Additional IP product and can be moved to any service in the [region](#choosearegion) of the range. To start the announcement of your range, assign one of its blocks to an eligible product, from the OVHcloud Console or the OVHcloud API (see [When your range is announced](#announcement)). #### Slice and aggregate blocks Any block of an imported IPv4 range can be split into smaller blocks (/25 to /30) and/or individual addresses (/32), and aggregated again. These actions apply to the IP blocks of the range, not to the imported range itself. **Warning:** To be able to slice or aggregate a block, it must be unused (i.e. in the parking area) and there must not be any pending task associated with it (e.g. no pending move operation). To slice a block: ##### Via the OVHcloud Console 1. In the IP blocks list of your IPv4 range, click the "⋮" button to the right of the block, then select "Slice into blocks". 2. In the **Slice size** list, select the size of the child blocks. 3. Review the resulting blocks, then click "Slice IP block". ##### Via the OVHcloud API [POST /ip/{ip}/bringYourOwnIp/slice](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#post-/ip/-ip-/bringYourOwnIp/slice) Use the following parameters: - ip: the IP block you want to slice, in CIDR notation. - slicingSize: the resulting size of the sliced blocks, expressed as a network prefix size, in bits. For example if you want to slice a /24 block into 2 smaller blocks of size /25, you should enter the value "25". **Note:** This API call is asynchronous, the newly created blocks are made available shortly after the call. They will be usable as any other Additional IP block or individual address. To preview the resulting blocks for each block size, use the following API call with the same `ip` parameter: [GET /ip/{ip}/bringYourOwnIp/slice](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#get-/ip/-ip-/bringYourOwnIp/slice) To aggregate several child blocks into a parent block: ##### Via the OVHcloud Console 1. In the IP blocks list of your IPv4 range, click the "⋮" button to the right of one of the blocks you want to aggregate, then select "Aggregate blocks". 2. In the **Aggregate into** list, select the parent block. 3. Review the IPs to aggregate, then click "Aggregate IP block". ##### Via the OVHcloud API [POST /ip/{ip}/bringYourOwnIp/aggregate](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#post-/ip/-ip-/bringYourOwnIp/aggregate) Use the following parameters: - ip: the IP block you want to merge, in CIDR notation. - aggregationIp: the resulting block, in CIDR notation. It will be an aggregate of all its children blocks. **Note:** This API call is asynchronous, the re-aggregated blocks are made available shortly after the call. To preview all the possible aggregated blocks for a given IP block, use the following API call with the same `ip` parameter. For each possible aggregated block, it gives the list of children blocks to be merged back. [GET /ip/{ip}/bringYourOwnIp/aggregate](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#get-/ip/-ip-/bringYourOwnIp/aggregate) **Limitations:** - Configuration elements associated to individual IP addresses (/32) such as firewall rules or reverse DNS entries will be kept after slicing/merging operations. - Slice/aggregate API tasks cannot be followed up with the task number returned by the API, as the associated IP objects are destroyed in the process. - The listing of IP addresses and blocks returned by the API is ordered by network prefix size. We are working to provide a solution to list IPs by numerical order. - Once sliced, smaller blocks cannot be moved outside the region chosen at order time, and a re-aggregated /24 block cannot be moved across the Gravelines, Roubaix and Strasbourg regions (see [Region](#choosearegion)). ### Use an IPv6 range An imported IPv6 range does not contain any IP block when it is delivered. Create /56 blocks inside it, within the [quota](#quotas). The only block size available at the moment is /56, the only size supported by vRack and by the Additional IPv6 product. IPv6 ranges cannot be sliced or aggregated. The /56 blocks behave like Additional IPv6 blocks: like Additional IPv6, they can only be used with a [vRack](https://www.ovhcloud.com/pl/network/vrack/) at the moment, and more services will become eligible as they support Additional IPv6. A new block is created in the parking area, so your range is not announced yet (see [When your range is announced](#announcement)). To use the block, route it to your vRack by following our guide on [configuring an Additional IPv6 block in a vRack](https://docs.ovhcloud.com/pl/guides/bare-metal-cloud/dedicated-servers/configure-ipv6-in-vrack.md). To create a /56 block: #### Via the OVHcloud Console 1. In the IP blocks list of your IPv6 range, click "Create IP Block". 2. Enter the first address of the /56 block you want to create. The /56 prefix length is added automatically. The block must fall within your imported range and must not overlap an existing block. 3. Click "Create IP block". #### Via the OVHcloud API [POST /ip/service/{serviceName}/bringYourOwnIp/subRange](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#post-/ip/service/-serviceName-/bringYourOwnIp/subRange) Use the following parameters: - serviceName: the internal name of your BYOIP service. - ip: the /56 block to create, in CIDR notation. - description (optional): a description of the block. The call returns the created block. There is no task to follow. To list the blocks of an imported range, use the following API call: [GET /ip/service/{serviceName}/bringYourOwnIp/subRange](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#get-/ip/service/-serviceName-/bringYourOwnIp/subRange) To view the imported range of a BYOIP service, use the following API call: [GET /ip/service/{serviceName}/bringYourOwnIp/importedRange](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#get-/ip/service/-serviceName-/bringYourOwnIp/importedRange) To delete a /56 block: **Warning:** Deleting a block also deletes its firewall rules and all its other settings. You can create the same block again, but you will need to configure it again. #### Via the OVHcloud Console 1. If the block is routed to a service, move it back to the parking area first: only a parked block can be deleted. 2. In the IP blocks list of your IPv6 range, click the "⋮" button to the right of the block, then select "Delete". 3. Type the block shown in the dialog to confirm, then click "Delete". #### Via the OVHcloud API [DELETE /ip/service/{serviceName}/bringYourOwnIp/subRange/{ip}](https://api.eu.ovhcloud.com/console/?section=/ip&branch=v1#delete-/ip/service/-serviceName-/bringYourOwnIp/subRange/-ip-) Use the following parameters: - serviceName: the internal name of your BYOIP service. - ip: the /56 block to delete, in CIDR notation. The block must be in the parking area. ### Reverse DNS and WHOIS Some operations available on the Additional IP product are not available, or work differently, on the BYOIP product: - **Reverse DNS (IPv4):** during the delivery, we create ARPA zones on our DNS servers, whose names are given in the delivery email. Reverse DNS changes made in the OVHcloud Console or API are applied to these zones, and become public once your RIR has delegated the ARPA zones to our DNS servers. Delegation is optional: you can keep managing your reverse DNS on your own. - **Reverse DNS (IPv6):** not available. OVHcloud does not host any ip6.arpa zone for imported IPv6 ranges: keep managing the reverse DNS of your IPv6 range with your current DNS provider. - **WHOIS:** you cannot customize the WHOIS of your blocks from the OVHcloud Console or API, because OVHcloud does not own them. ## Cancel a BYOIP service **Warning:** Before cancelling an IPv6 range, delete all its /56 blocks (see [Use an IPv6 range](#ipv6-blocks)). Each block must be in the parking area to be deleted. From the IP addresses page, open the `BYOIP Ranges ` tab, click the `⋮ ` button to the right of the range, then select `Terminate range `. The `My offers and services ` page opens in a new tab, filtered on your range: continue from step 3 below. You can also cancel the service from your account: 1. Open the "My offers and services" page of the OVHcloud Console. 2. In the search bar at the top right of the table (next to the filter button), type `byoip`, then press "Enter". 3. Click the "..." button to the right of the service, then select "Cancel my subscription". 4. In the confirmation window, choose whether to cancel the service immediately or on the expiry date, then click "Yes, cancel". ## FAQ ### Is it possible to import an IPv6 range? Yes, from /48 to /32, with a prefix length that is a multiple of 4. See [Supported sizes](#supportedsize). ### Is it possible to import an IP range smaller than a /24 (IPv4) or a /48 (IPv6)? No. See [Supported sizes](#supportedsize). ### Is it possible to import an IP range bigger than a /19 (IPv4) or a /32 (IPv6)? Not at the moment, but feel free to contact us to discuss this. See [Supported sizes](#supportedsize). ### Can I split an imported /24 into smaller blocks (/25 to /30) or into /32 addresses? Yes. See [Slice and aggregate blocks](#range-slicing). ### Can I create IPv6 blocks of another size than /56? Not at the moment. See [Use an IPv6 range](#ipv6-blocks). ### Can I import an IP range and an AS number that are not managed by the same RIR? Yes. See [Proof of ownership](#proveownershipip). ### Can I import an IP range or AS number managed by AFRINIC or LACNIC? Not at the moment. See [Supported RIRs and WHOIS types](#supportedrir). ### Can I use an IP range in more than one region, or change its region? No: a range is used in the region chosen at order time. To change it, cancel the service and order it again. IPv4 /24 blocks have an exception for Gravelines, Roubaix and Strasbourg. See [Region](#choosearegion). ### Which OVHcloud DNS servers handle the ARPA zone of my imported IP range? Their names are given in the delivery email. This only applies to IPv4 ranges. See [Reverse DNS and WHOIS](#reverse-dns). ### When does OVHcloud announce my imported range? Only while at least one of its IP blocks is routed to a service. See [When your range is announced](#announcement). ### Can I order the service while my IP range is still announced from another site? Yes, but you must stop that announcement as soon as the service is delivered. See [Announcement elsewhere and reputation](#notinuseontheinternet). ## Go further Join our [community of users](https://community.ovhcloud.com/).