How to use the Bring Your Own IP feature

Find out how to easily import your own IP as Additional IP to your OVHcloud account

Last updated 23rd November 2022

Objective

The Bring Your Own IP (BYOIP) feature allows you to use IP addresses ranges that you already own, as Additional IPs directly on the OVHcloud network and products.

These IP addresses will be imported in the form of a /24 IP block size and will behave like a regular OVHcloud Additional IP block product.

Requirements

Your IP range must be in a supported RIR

A Regional Internet registry (RIR) is an organization that manages IP addresses in a given region.

You need to own (see below) a public IPv4 block with one of the following RIRs:

An ARIN block can only be used with OVHcloud services located in Canada or the USA, while a RIPE block can only be used with OVHcloud services located in Europe.

To be considered as a valid owned block, imported blocks must be one of the following types :

  • ARIN (object «Network type »)
    • Direct Allocation
    • Direct Assignment

See https://www.arin.net/resources/registry/whois/#network and https://www.arin.net/resources/registry/reassignments/ for more information on Net Types objects.

  • RIPE (object « status »)
    • ASSIGNED PI
    • LEGACY
    • ALLOCATED PA

See « Description of the INETNUM Object » for more information on status objects.

Your IP range must have a supported size

We accept IP blocks from size /24 up to size /19. Below, is the number of /24 you will receive from the imported range:

CIDR Number of /24 blocks
/24 1
/23 2
/22 4
/21 8
/20 16
/19 32

Your IP range is not in use on the Internet

The range must not be announced or in use on the Internet (no announcement in terms of Border Gateway Protocol (BGP) on at least one public network).

Your IP/AS have a clean reputation

We may refuse using IPs/AS with a bad reputation, and we reserve the right to stop announcing the IPs/AS if their reputation has a negative impact on OVHcloud's reputation.

You need to choose a campus

A campus can be viewed as a list of datacenters where an IP can be used.

You will need to choose one campus where your IP will be used. Once the delivery is done, you will be able to move any /24 size block obtained from the imported range to any OVHcloud services in the same campus as the one chosen at order time.

Below is a list of current campuses:

  • RBX (Roubaix)
    • rbx (1-8)
  • GRA (Gravelines)
    • gra (1-3)
  • SBG (Strasbourg)
    • sbg (1-5)
  • WAW (Warsaw)
    • waw1
  • LIM (Limburg)
    • lim (1,3)
  • ERI (Erith)
    • eri1
  • BHS (Beauharnois)
    • bhs (1-8)
  • SGP (Singapore)
    • sgp1
  • VIN (Vint Hill)
    • vin1
  • HIL (Hillsboro)
    • hil1
  • SYD (Sydney 1)
    • syd1
  • SY2 (Sydney 2)
    • syd2

The list of available campuses will depend on your geographical location, and on the RIR of the IP. Below are listed all IP campuses where we plan to launch the BYOIP product. However, note that not all campuses may be supported at launch:

Customer IPs' RIR is: ARIN RIPE
Available campuses BHS
SGP
SYD
SY2
RBX
GRA
SBG
WAW
LIM
ERI

You must prove ownership of the IP range

To prove that you are the owner of the range, you will be requested to enter a special token which we will provide, into the public whois object corresponding to your range. This will be done via the web portal of the RIR managing your IPs. This token will be provided at order.

  • For RIPE, edit the « descr » field of the « inetnum » object of the IP.
  • For ARIN, edit the « Public Comments » field of the « Network » object.

The token needs to appears in the description field (see above) of the whois object, in a dedicated line. Other lines may be present, as long as the token is present in its own dedicated line in the description. The token must be added before placing the order, and must not be removed until the end of the delivery process.

You must prove ownership of the AS number (required only if you provide an AS number)

To prove that you are the owner of the AS number, you will be required to reuse the same token previously used to prove ownership of the IP range, and insert it into the public whois object corresponding to the AS number. This will be done via the web portal of the RIR managing your AS number. This token will be provided at order (it may also be found directly in the OVHcloud Control Panel, in the IP section).

  • For RIPE, edit the « descr » field of the « aut-num » object of the AS number.
  • For ARIN, edit the « Public Comments » field of the « ASN » object.

The token needs to appears in the description field (see above) of the whois object, in a dedicated line. Other lines may be present, as long as the token is present in its own dedicated line in the description. The token must be added before placing the order, and must not be removed until the end of the delivery process.

You have to allow OVHcloud to announce the IP range

On the RIR where the IP range is registered, you will need to create a route object for it (matching exactly the IP range), with the OVHcloud AS number ("AS16276") or your own AS number in the origin field of the route object.

For more information on route objects, please refer to your RIR’s documentation page :

Instructions

How to use the product

The imported IPs will behave like the current Additional IP product. An imported IP range will be split into /24 blocks that will be movable to any service in the same campus.

Some operations available on the Additional IP product will not be available on the BYOIP product.

For example, you will not be able to customize your blocks' WHOIS via the OVHcloud Control Panel/API, because OVHcloud does not own them.

For the same reason, you will not be able to edit your IP's reverses out of the box via the OVHcloud Control Panel/API.


During the delivery, we will create ARPA zones on our DNS servers and any reverse DNS modification via the OVHcloud Control Panel/API will be applied on them. However, these modifications will be visible to the public when our DNS servers receive delegations of the ARPA zones by the RIR. (This is optional, if you want to continue managing your reverse DNS on your own, you can).

FAQ

Is it possible to import an IP range lower than a /24?

No, the minimum accepted size is a /24.

Is it possible to import an IP range bigger than a /19?

Not at product launch, but feel free to contact us to discuss this.

Is splitting the imported /24 into smaller block size (/25, /26, /27, /28, /29 /30) or into /32 supported?

Not for the moment.

Can I import an ARIN range in campuses accepting only RIPE ranges, and vice-versa?

Not for the moment.

Can I import an ARIN AS number with a RIPE IP range, and vice-versa?

Yes.

Can I import an IP range or AS number managed by APNIC/AFRINIC/LACNIC?

Not for the moment.

Is it possible to use an IP range on more than one campus?

No, an IP range must be used in only one campus.

Is changing the campus of an imported IP possible?

Not at the moment, to achieve this you would have to release the product and purchase it again (this is the only option for now).

How will I know which OVHcloud DNS servers will handle the ARPA zone for my imported IP?

Their names will be communicated in the delivery email.

Is it possible to import an IPv6?

Not for the moment.

Go further

Join our community of users on https://community.ovh.com/en/.


Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community

In accordance with the 2006/112/CE Directive, modified on 01/01/2015, prices exclude VAT. VAT may vary according to the customer's country of residence.