OVHcloud BYOIP: bring your own IPv4 addresses to OVHcloud

You prove control of the range with a token in its registry record and a route object for the AS that will announce it, then order the import in the Control Panel. The range comes back as Additional IP blocks.

What OVHcloud accepts

From OVHcloud's documentation, on the day we checked (the BYOIP guide is dated 1 June 2026):

• Size. A /24 up to a /19, delivered as one to 32 /24 blocks; for anything larger, OVHcloud asks you to contact it.
• Registry. ARIN, the RIPE NCC and APNIC, with support for APNIC's national registries still "experimental". IPv4 only.
• Status. For the RIPE NCC: ALLOCATED PA, LIR-PARTITIONED PA, SUB-ALLOCATED PA, ASSIGNED PA, ASSIGNED PI or LEGACY. The guide lists the ARIN and APNIC types too.
• An exact record. The registry object must match the range. A parent or child block "will leave you unable to use that range".
• Who originates. OVHcloud's AS16276, which it recommends, or your own AS number, which may come from a different registry than the range.
• Reputation. OVHcloud may refuse a range or AS with a bad reputation, and stop announcing one that harms its own (keeping a block clean).
• One region per range, chosen at order: Paris, Milan, Gravelines, Roubaix, Strasbourg, Limburg, Warsaw, Erith, Vint Hill, Hillsboro, Beauharnois, Toronto, Singapore, Sydney or Mumbai.
• Products. Bare Metal, Hosted Private Cloud, Public Cloud, VPS, IPLB and the vRack private network.
• Price. The product page lists BYOIP as "Included at no extra cost".
• Timing. "Usually available within one business day" with OVHcloud's ASN; with your own AS number, it may take a few business days.

Before you start

The token. OVHcloud proves control with a token tied to your account, shown in the IP section of the Control Panel and returned by GET /me/bringYourOwnIp/token in the API. It goes on a line of its own, must be in the record before you order, and stays until delivery is complete.

A route object that matches the range exactly, with AS16276 or your own AS number as origin.

A ROA for the same origin. OVHcloud's guide does not mention RPKI, but if the block has a ROA for another ASN, networks that validate RPKI will drop OVHcloud's announcement (RPKI and ROAs).

OVHcloud's guide asks for no letter of authorization.

Step by step

01Update the registry. For a RIPE NCC block announced from OVHcloud's AS:

inetnum:   203.0.113.0 - 203.0.113.255
descr:     Example B.V.
descr:     <your OVHcloud token>

route:     203.0.113.0/24
origin:    AS16276

Check both before you order:

whois -h whois.ripe.net 203.0.113.0/24 | grep descr
whois -h whois.ripe.net -- "-T route 203.0.113.0/24"

02Order. In the Control Panel, open Network > Public IP Addresses and click + Bring Your Own IP. Select the registry, the region and the range, then the OVHcloud AS or your own, with its registry and number. Click Next, confirm the requirements are met, then Confirm.

03Wait for delivery. The /24 blocks appear among your Additional IPs, tagged BYOIP, and the delivery email names OVHcloud's DNS servers for the reverse zones.

04Assign a block. OVHcloud starts announcing once you assign a block to an eligible service, in the Control Panel or the API. Blocks move between services in the same region like any Additional IP.

05Split, if you need to. A /24 in the parking area, with no task pending, can be cut into blocks down to /30 or into single addresses: Segment in the Control Panel, or POST /ip/{ip}/bringYourOwnIp/slice with a slicingSize such as 26. Combine merges them back.

Mistakes that cost a day

• A record that does not match. A leased /24 inside the holder's larger object, with no inetnum of its own, fails the exact-match rule; the holder has to create one.
• The token in the wrong field. For the RIPE NCC it goes in descr, on its own line; remarks is the APNIC field.
• Two announcements. OVHcloud lets you order while the range is announced elsewhere, but you "must immediately cancel" the other announcement once delivery is done. Otherwise you risk connectivity problems, for which OVHcloud "cannot be held responsible".
• The wrong region. It cannot be changed; you would release the range and order again. Only /24 blocks ordered after 1 January 2023 in Gravelines, Roubaix or Strasbourg can move between those three, and not once split and merged again.
• Expecting to edit the record. OVHcloud cannot change the WHOIS of a block it does not own, and its reverse DNS goes public only once the reverse zones are delegated to its DNS servers.
• Mixing up BYOAS and BGP Service. BGP Service, for running BGP from your own servers, is a separate product in alpha that uses private AS numbers. OVHcloud says it is "not intended to be used in a production environment".

If you lease the block

OVHcloud speaks of blocks you own but defines a valid one by registry status, including ASSIGNED PA and SUB-ALLOCATED PA, the statuses a leased block usually has in the RIPE Database. Its proof is the token, and the guide does not say the record must name your organization. The holder does the registry side, since only the holder's maintainer can edit the objects: an exact-match inetnum, the token on its own descr line until delivery, the route object, and a ROA for the same origin. For reverse DNS through OVHcloud, the holder also delegates the reverse zones to the servers named in the delivery email.

Where RTM Networks fits

We lease /24s and larger from our own RIPE NCC address space, and sell blocks in the RIPE NCC, ARIN and APNIC regions. For space leased from us, we register the block as its own object in the registry, add your OVHcloud token to it, and create the route object and the ROA for AS16276 (lease IPv4). If you want your own AS number and do not run an LIR, we sponsor one (ASN sponsorship). For fewer than 256 addresses, we announce a block and deliver it to your OVHcloud server over GRE or WireGuard, down to a single address (GRE and WireGuard tunnels). Other providers: BYOIP guides.