Additional IP
Add flexibility to your applications with Additional IP
Most OVHcloud products include a pre-configured static IPv4 address. For outstanding flexibility, those products can also be used with Additional IP (previously known as Failover IP), which are IP addresses that can be easily assigned and moved from one service to another, and are available in 2 different formats:
- Additional IPv4 - an individual address (/32) or address blocks (up to /24)(/32)
- Additional IPv6 address blocks (/56)
Key Highlights
With Additional IP, you can switch from one service to another quickly and keep the entire configuration linked to that IP. This means you get an uninterrupted hosting solution, and easily handle infrastructure-related issues (hardware failures, system overruns, etc.).
Additional IP provides a solution that removes interruption or downtime if servers are overrun and can be used in this way for “Always On” availability.
By adding IP blocks, you can configure multiple IP addresses to your services. You can assign IPs into groups of 4, 8, 16, or up to 256 per server, with unlimited block publications. This makes upgrades simple, as you can reroute your IP to new hardware, rather than having to reconfigure the static IP. With multiple IPs grouped into blocks, you can manage your platforms more efficiently — upgrading and migrating from one service to another with ease.
With our IP announcement service, you can expand your project for a global audience by linking additional geolocated IPs. Those IPs can be geolocated in 14 available destinations. This considerably improves the ranking of your projects in popular search engines, radically improving your webpage SEO status.
You can use your own IP adresses as Additional IP address blocks. Bringing your own IP addresses instead of using OVHcloud IP addresses allows you to easily migrate your infrastructure to OVHcloud, notably by allowing you to maintain existing IP related configuration and IP reputation. Discover the OVHcloud BYOIP service.
Dual-stack addressing
Your clients can contact your services using IPv4 and IPv6 address types. This option provides native end-to-end connectivity for performance and next-generation IP protocol support.
Additional IP to meet your needs
Native IPv6 addressing brings additional value
You can gain low latency connectivity by leveraging Additional IPv6 native end-to-end service without any address translation in between. For example, you can expose your applications using Additional IPv6 and reach the other side directly using a next-generation network. This option can be a driver for latency-sensitive applications like media streaming.
Business continuity with dual-stack addressing
Following the growing availability of IPv6 addressing adoption, some parts of the "new internet" are available only using IPv6 addressing. Thus, some customers may prefer to reach your services through IPv6 addressing. Now, you can prepare for this new era by leveraging dual-stack with both: IPv4 and IPv6 address reachability.
Even more accessible IP addressing
Over the last few years we've observed exponential growth of various internet services. Every service requires an address to be accessed in the public internet space. As IPv4 addresses are becoming a limited resource and their price has been rising over recent years, free IPv6 may be a real alternative. Particularly in the countries with the highest IPv6 adoption rate (like France, Germany or India), this option adds value. This can be also a real enabler for your business in these markets and allows you to anticipate tomorrow's needs.
Full integration with other products
We understand that your infrastructure can be heterogeneous, including Public Cloud Instances, Hosted Private Cloud, Bare Metal servers, or simply VPS. You can use Additional IP with all those product families for scalability, disaster recovery, deployment environment switching, or more.
You can also use Additional IPv4 or Additional IPv6with our unique private networking vRack technology. Routing your Additional IP block to the vRack gives you more flexibility on public addressing and provides the ability to use high-availability protocols like VRRP for you public-facing services. Such combination allows no service interruption during maintenance periods or failure situations. For more details, please visit vRack page.
Finally, you can also use Additional IP as public-facing address for our OVHcloud Load Balancer. For more details, please visit OVHcloud Load Balancer page.
How to purchase additional IP addresses?
Go to your OVHcloud control panel and make the most of Additional IP.
List of available regions
| Region location | Region name | Region code (aka trigram*) |
|---|---|---|
| Europe (France - Paris) ** | eu-west-par | PAR |
| Europe (France - Gravelines) | eu-west-gra | GRA |
| Europe (France - Roubaix) | eu-west-rbx | RBX |
| Europe (France - Strasbourg) | eu-west-sbg | SBG |
| Europe (Germany - Limburg) | eu-west-lim | LIM |
| Europe (Poland - Warsaw) | eu-central-waw | WAW |
| Europe (UK - Erith) | eu-west-eri | ERI |
| North America (US - East - Vint Hill) | us-east-vin | VIN |
| North America (US - West - Hillsboro) | us-west-hil | HIL |
| North America (Canada - East - Beauharnois) | ca-east-bhs | BHS |
| North America (Canada - East - Toronto)** | ca-east-tor | YYZ |
| Asia Pacific (Singapore -Singapore) ** | ap-southeast-sgp | SGP |
| Asia Pacific (Australia - Sydney) ** | ap-southeast-syd | SYD |
| Asia Pacific (India – Mumbai) ** | ap-south-mum | YNM |
* The naming convention is no longer in use. It's displayed only for reference purposes.
** Additional IPv6 can only be attached to your services using vRack network. It adds flexibility, however, it's not currently available in APAC, TOR and 3AZ regions.
Limitations
Additional IPv4
OVH DS | SYS DS | KS DS | VPS*** | PCI*** | |
|---|---|---|---|---|---|
| Number of IP* | 256 | 128 | 0 | 16 | 256 |
| Number of slots** | 64 | 16 | 0 |
*: Off main server IP.
**: Slots represent the number of routes available for addressing your IPs and IP blocks. A slot can host 1 IP or 1 block of several IPs.
***: VPS and PCI instances do not allow IP blocks to be added.
Additional IPv6
The nature of Additional IPv6 addresses means they behave slightly different from the IPv4 version.
Here are the main differences:
- To operate, Additional IPv6 addresses can only be used with the vRack network. This is the biggest difference compared to Additional IPv4 that can also be directly attached to servers or instances.
- Due to the nature of the hierarchical design of IPv6 address space, Additional IPv6 blocks are specific to the region in which they were issued. This means there is no option to move them between regions.
- A bridged and routed mode is available for subnets defined inside the /56 block.
- Multiple /56 blocks can be routed into a vRack network (in multiple locations) but SLAAC (Stateless Autoconfiguration) can only be enabled on one IPv6 block at a time. This leads to unpredictable results (including losing connectivity) when enabled on multiple IP blocks inside the same vRack.
In terms of limitations:
- there are up to 3 Additional IPv6 blocks (/56) per region location allowed (a single Additional IPv6 block per vRack in a region location)
- up to 128 active IPv6 addresses in bridged subnet per block
- up to 128 routed subnets declared per block
* Additional IPv6 is not available in APAC, TOR, 3AZ regions for the time being.
FAQ
What is the failover feature with Additional IP addresses ?
Additional IP addresses, also called Failover IP or Floating IP addresses in the cloud industry, enhance service continuity (“failover”) 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, and switching services to a backup server in the event of an incident. Additional IP addresses are available as individual addresses (/32) or as IP address blocks (up to /24).
What are the available locations for my geolocalized IP addresses?
At OVHcloud you can choose the geolocation of your IP block. 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.
When releasing my Additional IP, what happens if they're found to be blacklisted (RBL)?
As detailed in the T&C for your Additional IP, OVHcloud reserves the right to charge a 10-euro fee upon termination, to cover the costs for unblacklisting.
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 IP block sizes can be attached per server?
Additional IPv4 address blocks of sizes 4, 8, 16, or up to 256 can be attached per server.
Additional IPv6 addresses are offered as blocks of size /56. They can be attached to a single vRack in a specific location.
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 new product. If you use an IPv6 block connected to your server you still can use it but not with vRack. If you use legacy vrack1.0 IPv6 services, you will need to migrate into a new Additional IPv6 as the old services will be deprecated once the new product reaches General Availability.
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.
Will I be able to keep my Additional IPv6 pool(s) once the product reaches General Availability?
Yes, all IP blocks released during the early stages (Alpha/Beta) will continue to operate once reaching GA.