Understanding IPv6 on Contabo VPS: Why You May Only See One Usable Address
Your Contabo VPS has a /64 IPv6 block, but only ::1 works? Learn why, how to test if your subnet is routed or NAT66, and how to get real IPv6 rotation.
- IPv6
- Contabo
- VPS
- Networking
- Linux
Many VPS providers advertise IPv6 with a full /64 block. In theory that gives your server billions of unique IPv6 addresses. But many users on Contabo EU nodes report a confusing situation: the assigned subnet is /64, yet only one IPv6 address actually works.

The issue users run into
A common case goes like this:
- The VPS is given an IPv6 subnet (such as
xxxx:xxxx:xxxx:xxxx::/64). - The server automatically sets the first address in that block (usually ending in
::1). - That primary IPv6 works well. Pings to Google's IPv6 DNS succeed, latency looks fine and inbound traffic is routed correctly.
- But when you manually add other addresses from the same block (
::2,::3,::10), things break.
- On some nodes, the extra addresses cannot make any outbound connection (100% packet loss).
- On other nodes, the addresses can be added locally, but outbound traffic is masqueraded (NAT66). Whichever address you use, the world only sees one fixed IP.
How to test if your IPv6 block is routed
To check whether your Contabo IPv6 block supports multiple addresses:
1. Add some test IPv6 addresses
# Add extra IPv6 addresses from your /64
for i in {10..15}; do
ip -6 addr add xxxx:xxxx:xxxx:xxxx::$i/64 dev eth0
done
2. Send outbound requests from each IPv6
for i in {10..15}; do
echo "Testing ::$i"
curl -6 -s --interface xxxx:xxxx:xxxx:xxxx::$i https://ifconfig.co/ip
done
3. Read the results
- Every test returns a different IPv6: you have a routed /64.
- Only the first address works: only the primary address is usable, the subnet is not routed.
- Every test returns the same external IPv6: the provider uses NAT66, so real IPv6 rotation is not possible.
Visual explanation
Case A: Routed IPv6 /64 (ideal)
Your VPS (eth0)
├── ::1 → Seen as ::1
├── ::2 → Seen as ::2
├── ::3 → Seen as ::3
Each IPv6 is unique and visible on the internet.
Case B: Non-routed /64 (common on Contabo)
Your VPS (eth0)
├── ::1 → Seen as ::1
├── ::2 → X (not reachable)
├── ::3 → X (not reachable)
Only one IPv6 is usable.
Case C: NAT66 / masqueraded setup
Your VPS (eth0)
├── ::10 → Seen as ::15
├── ::11 → Seen as ::15
├── ::12 → Seen as ::15
All addresses collapse into one external IPv6.
Why it matters
For most users a single IPv6 address is not a problem. Simple web hosting, mail servers and application backends all work fine with one address.
But some workloads need many addresses, for example Lavalink audio nodes, load balancing, or IP rotation for rate-limited services. For those, one usable address out of a /64 is a real limitation.
The solution
If you need real IPv6 rotation on a Contabo VPS, open a support request and ask specifically for a routed IPv6 subnet. With a routed block:
- You can assign several IPv6 addresses to your server (
::2,::3,::100...). - Each address is reachable on the internet.
- Apps that depend on IP rotation can use the full /64.
Takeaway
Contabo EU VPS nodes technically come with an IPv6 subnet, but depending on how the node is configured you may get only one practical IPv6 address. If your project needs real IPv6 rotation, the safest route is to ask Contabo support for a properly routed block.
This is not a bug in Ubuntu or Docker networking. It comes from how the provider routes IPv6. Knowing this up front saves hours of troubleshooting and helps you pick the right plan.