This is an old revision of the document!
Every member has 1 public IPv4 address and 32 IPv6 addresses available. Additional public IPv4 addresses are subject to a fee, IPv6 addresses are given upon request.
Due to the type of virtualization used, addresses can only be assigned one at a time, or /32 IPv4 and /128 IPv6 addresses. This means that it is not possible to assign the whole IPv6 subnet.
Private IP addresses access the internet using NAT and are therefore not accessible from the outside. Private addresses are useful if you divide the allocated resources between several VPSs. The public IPv4 address is often unnecessary. However, functioning with only an IPv6 is problematic since some servers still don’t support it.
Currently it is necessary to request private addresses from our support and you should also count with the possibility that they can change in the future.
In the production environment, we use a concept of IP address ownership. As soon as an address is first assigned to a VPS, its owner is set. Afterwards, even if the address is removed from the VPS, the owner of the address remains the same. When assigning addresses to VPSs, it is necessary to first assign pre-owned addresses and only then to choose new ones.
Ownership prevents people from taking temporarily unused addresses while also preventing people from misusing IP addresses by getting them on blacklists and then taking new ones. The address with a damaged reputation would then be given to someone else.
The concept of ownership does not apply to the playground.
A list of addresses is available in the “Networking → IP addresses” menu. This is where you can see addresses that are owned or assigned to VPSs, as well as addresses that are available. It is possible to assign addresses to VPSs directly from this list.
The TX and RX columns display the maximum possible data flow in Mbps.