Choosing the Right VPS IP in 2026: Dual-Stack vs. IPv6-Only Explained

The technical difference between IPv4 and IPv6 is actually pretty easy to grasp. What trips people up when choosing a VPS isn't the protocol itself — it's figuring out which one their specific situation actually calls for. So let's start with the practical implications, then get into the technical side.

Why IPv4 Keeps Getting More Expensive

IPv4 uses 32-bit addressing, which caps the theoretical maximum at around 4.3 billion addresses. Sounds like a lot — but global connected devices passed that number a long time ago. IANA exhausted its top-level IPv4 pool in 2011, and regional registries followed in the years after. Today, acquiring a fresh batch of IPv4 addresses means either buying on the secondary market or waiting for reclaimed blocks. Neither is cheap.

That cost flows downstream to users. AWS started charging for all public IPv4 addresses in 2024 — roughly $0.005 per hour, which adds up to nearly $3.60 per month per address. Google Cloud and Azure have made similar adjustments. European providers like Hetzner, OVHcloud, and Netcup offer IPv6 for free while billing IPv4 separately.

If your current VPS plan "includes a public IP," that IP is almost certainly IPv4, with the cost bundled into the plan price. But the trajectory here is clear — IPv4 will keep getting more expensive, IPv6 will keep expanding. Worth factoring into any longer-term planning.

What IPv6 Is, and How It Differs

IPv6 uses 128-bit addressing. The address space is, for all practical purposes, inexhaustible. More importantly, IPv6 was designed without the need for NAT (Network Address Translation) — every device can have its own globally unique public address, which means more direct communication paths.

A typical VPS can be assigned a /64 IPv6 prefix, giving you 2⁶⁴ addresses to work with — far beyond anything you'd ever actually use. Hetzner, for instance, assigns a /64 block to every server by default.

Core differences at a glance:

The Real Limitations of IPv6 VPS

Better to cover the limitations first — picking wrong here can be genuinely painful.

The core issue: not every network supports IPv6. Some payment gateways, third-party APIs, and older SaaS services still only expose IPv4 endpoints. If your VPS only has IPv6 and you try to call one of those services, the request will fail outright.

IPv6 connectivity in mainland China is uneven. Some carriers and regions have inconsistent IPv6 support, and the experience for Chinese users accessing a pure IPv6 server overseas can be unpredictable at best.

Then there's tooling. Most modern Linux distributions handle IPv6 fine at the system level, but older scripts and configuration templates sometimes default to IPv4-only listeners. It usually requires a manual fix — not difficult, but if you hit it unexpectedly, expect some debugging time.

What Dual Stack Means

Dual stack simply means the server has both an IPv4 address and an IPv6 address simultaneously. It's the most widely recommended configuration — full compatibility with both network types, no compromises on either side.

Most mainstream providers include dual stack in their standard plans: one IPv4 address plus a /64 IPv6 prefix. DigitalOcean, Vultr, Linode, and Kamatera all default to this. Hetzner enables IPv6 by default; whether IPv4 is included depends on the specific plan.

If this is your first VPS and you don't have a specific reason to do otherwise, just go with dual stack. It's the path of least resistance.

Who Should Actually Consider IPv6-Only

IPv6-only means the server has no independent public IPv4 address. These plans are typically cheaper, and some providers use them as entry-level offerings.

Honestly, I'd only recommend this setup in a narrow set of scenarios: learning Linux and server basics, personal experimental environments, internal Docker or Kubernetes networking tests, or backend workloads that don't need public-facing access.

Running WordPress, WooCommerce, a public-facing API, or anything that needs to be broadly accessible? The compatibility risk with IPv6-only will create problems. Not worth it.

IPv6-Only VPS with Cloudflare WARP

There's a well-known workaround: install Cloudflare WARP on an IPv6-only server to add IPv4 outbound capability. WARP is a free Cloudflare tool — once installed, the server can reach IPv4 resources through Cloudflare's network.

Setup on Debian/Ubuntu:

#  Cloudflare WARP 
curl -fsSL https://pkg.cloudflareclient.com/pubkey.gpg \
  | sudo gpg --yes --dearmor \
  --output /usr/share/keyrings/cloudflare-warp-archive-keyring.gpg

echo "deb [arch=amd64 \
  signed-by=/usr/share/keyrings/\
cloudflare-warp-archive-keyring.gpg] \
  https://pkg.cloudflareclient.com/ \
  $(lsb_release -cs) main" \
  | sudo tee /etc/apt/sources.list.d/cloudflare-client.list

# install
sudo apt update && sudo apt install cloudflare-warp -y

# register
warp-cli register
warp-cli connect

# verify IPv4 
curl -4 ifconfig.me

One thing to be clear about: WARP's outbound IPv4 comes from Cloudflare's shared address pool — it's not a dedicated IPv4 assigned to you. Some platforms have restrictions on Cloudflare IPs. This solution works well for occasional IPv4 access needs, but it's not a substitute for a dedicated IPv4 address in any business-critical context.

IPv6 Support Among Major VPS Providers in 2026

Matching Protocol to Use Case

WordPress and WooCommerce: IPv4 or dual stack. Plugin compatibility, payment integrations, and third-party services all depend on IPv4 availability. Pure IPv6 here is asking for headaches.

Corporate websites and public APIs: dual stack, no question. Covers every visitor's network environment without making any compromises.

Docker and Kubernetes internal services: dual stack is sufficient. If the workload is purely internal, IPv6-only is viable.

AI model deployment and inference services: dual stack. The model itself doesn't care about the protocol, but pulling container images and calling external APIs requires IPv4 compatibility.

Learning Linux and personal experiments: IPv6-only is fine. Good opportunity to get familiar with IPv6 configuration, and you save a bit on cost.

Provider Recommendations

Hetzner offers the best price-to-performance ratio in this space. European data centers, IPv6 enabled by default, and you get significantly more compute for your budget compared to US-based alternatives. Strong fit for individual developers and workloads where European latency matters.

DigitalOcean is the easiest on-ramp for users who want straightforward setup. Dual stack by default, solid documentation, and mature one-click deployment options for WordPress and Docker.

Vultr has the widest geographic coverage — 30+ cities globally. When you need a node in a specific region that others don't cover, Vultr is usually the answer.

OVHcloud suits European enterprise requirements well. IPv6 support is mature, and the platform has a strong track record for long-term stability.

Kamatera is the right call when you need a non-standard resource configuration. CPU, RAM, and storage are independently adjustable — useful when fixed-tier plans from other providers don't match your requirements.

Contabo is worth considering when budget is the primary constraint and you need generous RAM or storage. IPv6 is included in plans, and the value-per-dollar ratio is among the better options in its tier.

A Simple Decision Framework

Before choosing, ask yourself two questions: Does my setup depend on any third-party services that only support IPv4 — payment processors, SMS gateways, specific APIs? And are any of my target users on networks that don't yet support IPv6?

If either answer is "yes" or "not sure," go dual stack. The money saved by going IPv6-only is not worth the compatibility troubleshooting that comes with it.

If both answers are genuinely "no" and the use case is learning or experimentation, IPv6-only works fine. Pair it with WARP for the occasional IPv4 access need, and you're covered.