Additional IP
Flexible application addressing with Additional IP
Most OVHcloud services come with predefined public IP addresses, but Additional IP gives you flexible public addressing that can be moved between servers or instances without changing your applications.
Additional IPv4 and IPv6 addresses make your applications independent from the underlying infrastructure, with easy reassignment across Dedicated servers, Public Cloud and Private Cloud, giving you more control over how you expose your services to the internet.
Public internet addressing made flexible
Additional IP gives you flexible public addresses you can attach to your OVHcloud services and move between servers or instances without changing your application or DNS.
Use individual IP addresses or address blocks, in IPv4 and IPv6, to design resilient, multi-environment architectures or to bring your own ranges when migrating to OVHcloud.
Why use Additional IP?
High availability and failover
Additional IP abstracts application exposition from the underlying infrastructure, helping you build highly available setups without complex renumbering.
Quickly reassign an IP from a failed server to a standby node and restore service with almost no interruption.
Use Additional IP blocks with VRRP on a vRack network to build active/passive or active/active gateways in front of your applications.
Smoothly scale your applications without impacting your business continuity.
Scalable IP blocks for modern applications
With Additional IP blocks, you can allocate multiple IP addresses to the same service or vRack and organise them per tenant, application or environment.
Attach blocks of 4, 8, 16 or up to 256 IPv4 addresses per server, and use them for multi-site hosting, SSL separation or containerised workloads.
Group applications (for example, per customer or per microservice) on dedicated addresses to simplify firewall policies, logging and traffic analysis.
Combine several blocks across environments (dev, staging, production) to model clean, repeatable addressing plans.
Built-in Anti-DDoS protection
Benefit from OVHcloud’s always-on Anti-DDoS protection at the network edge, without extra costs and setup.
Protect services exposed on Additional IPs (including BYOIP) with OVHcloud Anti-DDoS Infrastructure, by default and at no additional cost.
Maintain availability during volumetric or protocol attacks while keeping control over how traffic is routed to your backends with Additional IPs.
- Configure Edge Network Firewall rules for every IP address from your Additional IP blocks for even better attack protection.
BYOIP and IP reputation control
Bring Your Own IP (BYOIP) allows you to announce your own IP ranges from OVHcloud network, while benefiting from the Additional IP flexibility for management of your IP range.
Keep existing IP space and reputation when migrating workloads to OVHcloud, avoiding DNS and ACL rewrites.
Maintain consistent IP-based ACLs and routing policies across hybrid and multi-cloud environments.
Gradually transition services to OVHcloud without changing the public entry points used by partners or customers.
Discover & interconnect Additional IP compatible products
Dedicated servers
Assign Additional IPs directly to dedicated servers to host many websites, appliances or tenant environments on the same hardware.
Use IP blocks to segment customer traffic, separate management and production, or expose virtual appliances and firewalls.
Hosted Private Cloud
Use Additional IP as the public edge for your Hosted Private Cloud clusters, without tying external access to a single node.
Expose management interfaces, VPN endpoints or tenant networks while keeping the underlying ESXi or managed infrastructure private.
Public Cloud services
Attach Additional IP to Public Cloud instances to build flexible front-ends, jump hosts or NAT gateways that can be reattached as you scale.
Combine with autoscaling and infrastructure-as-code to automate blue/green deployments that preserve public IPs.
Virtual Private Servers
Address more players or web domains hosted on your VPS by configuring more Additional IP addresses.
vRack private networks
Use Additional IP blocks as internet gateways for workloads running in vRack, routing public traffic into a private, multi-region L2 network.
Design highly available gateways using VRRP and Additional IP on dedicated network appliances or general-purpose servers.
Load Balancer
Assign Additional IPs to OVHcloud Load Balancer to standardise public entry points across multiple backends and regions.
Keep the same IP when reconfiguring pools, migrating backends to vRack or changing load-balancing algorithms.
How to purchase additional IP addresses?
Go to your OVHcloud control panel and make the most of Additional IP.
Use cases
Additional IP supports multiple architectures, from simple failover setups to complex, multi-region gateways.
Always-on hosting and failover
Switch Additional IP address between primary and backup servers.
Run your production website on a dedicated server or Public Cloud instance and attach an Additional IP as the main public endpoint.
Maintain a standby instance ready with the same configuration; in case of failure, move the IP to the backup to restore service in minutes.
Reuse the same pattern for database replicas, cache layers or application servers that require fast switchover.
Multi-site and multi-tenant web platforms
Host multiple brands, customers or environments on shared infrastructure while keeping clean isolation at the IP level.
Assign different IPs or small blocks to each tenant to simplify per-customer firewalling, traffic shaping and observability.
Use unique IPs for SSL, SNI edge cases or legacy integrations that rely on IP-based identification.
Combine geo-localised IPs with CDN and DNS policies to serve content from locations close to your users.
Internet gateways for vRack applications
Pair Additional IP blocks with vRack to expose regional internet gateways for your global private network.
Route public IPv4 and IPv6 traffic into the vRack in the region of your choice.
Deploy high-availability virtual routers using VRRP and move gateway IPs between nodes during maintenance or incidents.
Combine with BYOIP to publish your own prefixes through gateway nodes placed in specific regions.
- Scale egress public bandwidth following your service dynamics.
IPv6-first and dual-stack architectures
Design modern, dual-stack applications that leverage IPv6 performance and reach while keeping IPv4 compatibility.
Attach Additional IPv6 /56 blocks to vRack and create bridged or routed subnets for your workloads.
Offer IPv6-only paths for latency-sensitive services (such as media streaming) while keeping IPv4 as a fallback.
Use dual-stack addressing to reach newer IPv6-only parts of the internet and future-proof your applications.
Regional availability and limits
Additional IP address blocks are available in multiple OVHcloud regions and can be reassigned between compatible services in the same region. IP blocks can move between datacentres inside a region, but cannot be moved across regions. Exception to this rule is specific IPv4 flexibility between eu-west-gra, eu-west-rbx and eu-west-sbg.
| Region location | Region code | Additional IP availibility | Additional IPv4/v6 for vRack public routing availibility | |
| Europe (France - Paris) | eu-west-par | ✔ | ✔ | |
| Europe (France - Gravelines) | eu-west-gra | ✔ | ✔ | |
| Europe (France - Roubaix) | eu-west-rbx | ✔ | ✔ | |
| Europe (France - Strasbourg) | eu-west-sbg | ✔ | ✔ | |
| Europe (Germany - Limburg) | eu-west-lim | ✔ | ✔ | |
| Europe (Poland - Warsaw) | eu-central-waw | ✔ | ✔ | |
| Europe (UK - Erith) | eu-west-eri | ✔ | ✔ | |
| Europe (Italy - Milan) | eu-south-mil | ✔ | ✔ | |
| North America (Canada - East - Beauharnois) | ca-east-bhs | ✔ | ✔ | |
| North America (Canada - East - Toronto) | ca-east-tor | ✔ | ✔ | |
| North America (US - East - Vint Hill) | us-east-vin | ✔ | ✔ | |
| North America (US - West - Hillsboro) | us-west-hil | ✔ | ✔ | |
| Asia Pacific (Singapore -Singapore) | ap-southeast-sgp | ✔ | ✔ | |
| Asia Pacific (Australia - Sydney) | ap-southeast-syd | ✔ | ✔ | |
| Asia Pacific (India – Mumbai) | ap-south-mum | ✔ | ✔ | |
Additional IPv4: up to 256 addresses off the main server IP and up to 64 slots (one slot per IP block) per dedicated server, 128 addresses and 16 slots for Kimsufi servers. PCI instances and VPS do not support IP blocks and allows connecting accordingly up to 265 (PCI) and 16 (VPS) addresses.
Additional IPv6: up to three /56 blocks per region (one per vRack in a region), with up to 128 active IPv6 addresses in bridged mode and 128 routed subnets defined per block. Additional IPv6 blocks can only be used through the vRack network with other products.
Most popular guides
FAQ
What is the failover feature with Additional IP addresses ?
Additional IP addresses (also called Failover IP or Floating IP addresses) enhance service continuity for your applications and systems. With Additional IP, you can reassign the IP addresses from one service to another quickly, with almost no service interruption for your users. This mechanism can be used during service migrations, moving projects from development to production environments, testing A/B deployments and switching services to a backup server in case of failure of the main one. Additional IPv4 addresses are available as individual addresses (/32) or as IP address blocks (up to /24), while Additional IPv6 addresses are available as /56 blocks.
What are the available locations for my geolocalized IP addresses?
At OVHcloud you can select the geolocation of your Additional IPv4*. Availability of geolocalized IP addresses varies depending on the region where your service is located.
| Regions | Available geolocalized IP addresses |
| France | France, Ireland, Portugal, United Kingdom, Italy, Switzerland, Spain, Poland, Czech Republic, the Netherlands, Finland, Lithuania, Germany, and Belgium |
| Germany | France, Ireland, Portugal, United Kingdom, Italy, Switzerland, Spain, Poland, Czech Republic, the Netherlands, Finland, Lithuania, Germany, and Belgium |
| Poland | Poland |
| United Kingdom | United Kingdom |
| Canada | Canada |
| Australia | Australia |
| Singapore | Singapore |
| United States | United States |
| India | India |
* Additional IPv6 is not available in APAC regions for the time being.
What is a RIPE IP address?
A RIPE IP address is an IP address managed and distributed by European IP Networks (Réseaux IP Européens in French - RIPE). It is an open community that ensures administrative and technical conditions to maintain and develop the Internet. One of the main activities of RIPE is to allocate the IP blocks to European ISPs (Internet Service Providers) and register the data in a public database, including information such as a country’s IP ranges, current IP allocation, and IP geolocation.
What is an ARIN IP address?
The American Registry for Internet Numbers (ARIN) oversees the management and allocation of IP addresses in Canada and in the United States. It is the equivalent of RIPE in North America. An ARIN IP address is an address managed by ARIN.
What is the maximum period of non-assignation of my Additional IP?
If the Additional IP addresses or block of IP addresses are not used (i.e. not assigned to a service) during 30 consecutive days, OVHcloud reserves the right to reclaim them after notifying the user. More details can be found in the Term & Conditions for Additional IP.
What Additional IP block sizes can be attached per server?
Available Additional IPv4 block prefixes are between /30 to /24 (which means block sizes of 4 to 256 addresses per block).
Additional IPv6 addresses are offered as blocks of size /56. They can be attached to a single vRack in a specific location and then used on a server as a whole or as a subnets depends on the needs.
Can I attach my Additional IP block to a Public Cloud instance?
We do not offer Additional IP block support at PCI instance level, but you can still assign Additional IP block to a PCI project and then manage attribution of individual IPs from that block to a specific instances.
Can I move my Additional IPv6 block from one region to another?
Due to the nature of hierarchical design of IPv6 address space, Additional IPv6 blocks are specific to a region. This means there is no possibility to move them betwe en regions (but you can still re-route them to any other vRack-connected backend).
Can I use the same vRack with IP blocks in multiple locations?
Yes, but please check limitations and use with caution.
Can I delegate prefixes via a specific host inside my vRack?
Yes, this is possible, but for now there is no DHCPv6-PD available. This setup must be defined manually using routed subnets and next-hop addresses.
Can I use Additional IPv6 block with a VPS server?
No, it is only available via a vRack network, so it is not possible to use it with VPS.
I already use IPv6 addresses. Can I attach them to a vRack network?
Additional IPv6 and its vRack connectivity is a different product from Primary IPv6 addresses delivered with a dedicated server or a VM. If you use an IPv6 block connected to your server, you still can use it but not with vRack. Using both addresses (Primary IPv6 and Additional IPv6 via vRack) can be a good choice, but additional attention will be needed for routing and interface configuration (Policy Based Routing - PBR - will be needed with different routing tables per interface to ensure symmetric traffic) - please refer to our guides for more details.
How can I create dual-stack setup within vRack with public IPv6 and IPv4 addresses?
This is the default behaviour. Just ensure that the Additional IPv6 and Additional IPv4 are located in the same region/location and attached to the same vRack.
I prefer to use manual setup for IPv6 addressing and don't want to use SLAAC IP auto-configuration. How can I disable it?
It is sufficient to disable SLAAC inside the Control Panel or using an API call for every Additional IPv6 block. This is an option available inside the first /64 subnet of the block.
If you want to be sure your hosts will never reconfigure on an IPv6 address there are two sysctl configurations to be performed (for all interfaces or on a per-interface basis) on your hosts:
ipv6.conf.all.autoconf=0
net.ipv6.conf.all.accept_ra=0
This way your operating system will not reconfigure the interface IPv6 address nor the default routes.
Can I route IPv6 subnets into vlans inside my vRack?
Yes, this is possible, but only using a dedicated host. The host must be connected to a native vlan of vRack, which also has access to inner vlans using QinQ protocol. No direct support from the Control Panel or the API is provided.