ENTRDEESFRPTIT
OVHcloud

OVHcloud BYOIP — Bring Your Own IP Addresses to OVHcloud

Use your own IPv4 addresses as Additional IP blocks on OVHcloud infrastructure. Compatible with Bare Metal, Hosted Private Cloud, and Public Cloud services.

What is OVHcloud BYOIP?

OVHcloud BYOIP lets you bring your own IPv4 address ranges and use them as Additional IP blocks across OVHcloud infrastructure. Your addresses integrate with OVHcloud's network and benefit from their included anti-DDoS protection. Supported on Bare Metal dedicated servers, Hosted Private Cloud (VMware), and Public Cloud instances.

All OVHcloud datacenters — Europe (France, Germany, UK, Poland), North America (Canada), Asia-Pacific (Australia, Singapore)

AS16276
OVHcloud ASN
/24
Minimum Prefix
/19
Maximum Prefix
~72h
Setup Time
75%
Cost Savings

OVHcloud BYOIP Requirements

Ensure you meet these prerequisites before submitting your BYOIP request to OVHcloud.

Minimum /24, Maximum /19 Prefix

OVHcloud accepts prefix sizes between /24 (256 addresses) and /19 (8,192 addresses). Prefixes outside this range are not supported.

ROA Configuration

A Route Origin Authorization must be created authorizing AS16276 (OVHcloud) to announce your prefix via RPKI.

ARIN/RIPE/APNIC Registration

Your prefix must be registered with a recognized RIR (ARIN, RIPE NCC, or APNIC) with up-to-date WHOIS records.

Dedicated Server or Hosted Private Cloud

An active OVHcloud service (Dedicated Server, Hosted Private Cloud, or eligible Public Cloud project) to assign the BYOIP addresses to.

IP Failover Compatibility

BYOIP addresses are managed as IP Failover blocks within OVHcloud. Your services must support IP Failover assignment.

OVHcloud BYOIP Setup Process

Follow these steps to bring your own IP addresses to OVHcloud infrastructure.

1

Submit BYOIP Request via Control Panel

30 min

Log into the OVHcloud Control Panel and submit a BYOIP request specifying your IP range, RIR, and the OVHcloud service you want to associate the addresses with.

2

OVHcloud Verification Process

24-48 hours

OVHcloud's network team manually reviews your request, verifying ownership through RIR records and WHOIS data. This includes a Letter of Authorization (LOA) verification.

3

Configure ROA

2-4 hours

Create a Route Origin Authorization in your RIR portal authorizing AS16276. Wait for RPKI propagation to complete before OVHcloud can begin announcement.

4

IP Block Segmentation into /24s

Automated

OVHcloud automatically segments larger prefixes into /24 blocks for internal management and assignment to individual services via their IP Failover system.

5

Assign to OVHcloud Services

1-2 hours

Once the prefix is active, assign individual IPs or sub-blocks to your Dedicated Servers, Hosted Private Cloud VMs, or Public Cloud instances via the Control Panel or API.

Total: Approximately 72 hours (longer due to manual verification)

OVHcloud BYOIP Cost Comparison

Compare the cost of OVHcloud Additional IPs versus bringing your own addresses.

OVHcloud Additional IP

Per IP/hour~$0.004
Per IP/month$2.50–$4.50
/24 Monthly~$768/month

OVHcloud Additional IP pricing varies by region (€2–€4/IP/month). Costs add up quickly for /24 blocks.

BYOIP via IPv4Center

Per IP/month$0.50
/24 Monthly$128/month

Lease a /24 block and bring it to OVHcloud — no Additional IP charges for BYOIP addresses.

Your Savings

75%
cost reduction
/24 Monthly~$640/month
/24 Annual~$7,680/year

Benefits of BYOIP on OVHcloud

Why bringing your own IPs to OVHcloud gives you maximum value.

No Additional IP Charges

Eliminate OVHcloud's per-IP monthly fees entirely. BYOIP addresses are not billed as Additional IPs once onboarded.

Anti-DDoS Protection Included

Your BYOIP addresses automatically benefit from OVHcloud's infrastructure-level anti-DDoS protection at no extra cost.

Bare Metal & Private Cloud Compatibility

Use your addresses across Dedicated Servers (Advance, Scale, High-Grade), Hosted Private Cloud (VMware), and eligible Public Cloud instances.

BYOAS (Bring Your Own AS)

OVHcloud also supports bringing your own ASN alongside your IP prefixes for customers who need full routing autonomy.

Regional IP Movement

Move your BYOIP addresses between OVHcloud datacenters and regions at no additional cost, providing flexibility for disaster recovery and load distribution.

OVHcloud BYOIP FAQ

Common questions about bringing your own IP addresses to OVHcloud.

What prefix sizes does OVHcloud accept for BYOIP?

OVHcloud accepts prefixes between /24 (256 addresses) and /19 (8,192 addresses). Prefixes smaller than /24 or larger than /19 are not supported through their BYOIP program.

Can I use BYOIP with OVHcloud Public Cloud instances?

Yes, BYOIP addresses can be assigned to eligible Public Cloud instances as Additional IPs. However, primary support is for Dedicated Servers and Hosted Private Cloud environments.

Why does OVHcloud BYOIP take longer than other providers?

OVHcloud includes a manual verification step where their network team reviews ownership documentation and LOA. This adds 24-48 hours compared to fully automated providers like AWS or GCP.

Does OVHcloud anti-DDoS protection cover BYOIP addresses?

Yes. All IP addresses announced through OVHcloud's network — including BYOIP — automatically benefit from their infrastructure-level anti-DDoS mitigation at no extra cost.

Can I bring my own ASN alongside my IP addresses?

Yes, OVHcloud supports BYOAS (Bring Your Own AS Number) for customers who need routing autonomy. This is useful for multi-homed setups or when maintaining your own BGP policies.

Can I move BYOIP addresses between OVHcloud regions?

Yes. Unlike OVHcloud-owned Additional IPs which may have regional restrictions, BYOIP addresses can be reassigned between datacenters and regions at no additional cost through the Control Panel or API.

Ready to Bring Your IPs to OVHcloud?

Get a /24 block from IPv4Center and start using your own addresses on OVHcloud within 72 hours. We assist with ROA configuration and LOA documentation.

Free ROA setup and LOA preparation included with every purchase