IPv4 vs IPv6 on a VPS: what actually matters

When you rent a VPS, the IP address feels like a boring technical detail — until a plan charges extra for it, or a visitor cannot reach your site, or an outbound connection mysteriously fails. IPv4 and IPv6 are the two addressing systems your server can speak, and the choice between them is really a choice about cost, reach, and how much fiddling you are willing to do. This guide explains what each protocol is good for and how to pick a VPS plan that keeps you reachable without overpaying.

Why there are two, and why it costs you money

IPv4 is the original internet addressing scheme, and it uses 32-bit addresses — the familiar four-number form like 203.0.113.5. That design allows for about 4.3 billion addresses, which sounded infinite in the 1980s and ran out years ago. To stretch the remaining pool, the industry now buys and sells IPv4 addresses on a genuine market, and that scarcity is why a dedicated IPv4 address has become a line item on your bill. When you compare plans and one looks suspiciously cheap, the missing dedicated IPv4 is often the reason — worth checking against our cheap VPS checklist before you commit.

IPv6 was created to end that shortage. Its 128-bit addresses give a number so large it is effectively unlimited — every VPS can have not just one address but an entire block — so providers hand out IPv6 freely and rarely charge for it. The catch is that IPv6 is a separate protocol, not a drop-in replacement: a machine with only an IPv6 address cannot talk directly to an IPv4-only host, and vice versa. That single fact is behind most of the confusion, and it is why the practical question is almost never "which one" but "how do I get both".

What this means when you pick a VPS plan

Most of the internet still reaches you over IPv4. A large share of home connections, corporate networks, and older APIs remain IPv4-only, so if you host a public website or a service that strangers must connect to, a dedicated IPv4 address is close to mandatory. The good news is that a modern VPS almost always ships dual-stack — one dedicated IPv4 plus a block of IPv6 — and that is the configuration you want by default. When you are sizing a plan, treat the IP allocation as one more spec alongside CPU, RAM, and disk; our how to choose a VPS guide and the sizing calculator help you weigh the whole package rather than fixating on one number.

Some budget plans now offer IPv6-only or shared-IPv4 (NAT) options to keep the price down, and for the right job they are fine. A build server, a background worker, an outbound scraper, or anything that only makes connections rather than receiving them can live happily behind a shared or IPv6-only address. But a shared IPv4 means you do not control the reputation of that address — a noisy neighbour can get it onto a spam blocklist — and an IPv6-only box will need a translation layer to reach the IPv4-only parts of the web. If price is the driver, scan the current VPS deals and read the fine print on what kind of IP is actually included.

The gotchas that eat an evening

The most common surprise is an application that works for some visitors and silently fails for others. Nine times out of ten this is a DNS mismatch: you have an AAAA record pointing at an IPv6 address, but your web server or firewall is not actually listening on or allowing IPv6, so IPv6-capable clients get sent to a door that never opens. The fix is to make sure every layer agrees — DNS, the server's listen directives, and the firewall rules — or, if you are not ready to support IPv6 end to end, to simply not publish the AAAA record yet. The same care applies to latency and routing: a clean dual-stack setup will not save a server that is on the wrong side of the planet, which is why location still matters more than the protocol.

The second gotcha is outbound: services that connect to yours, or licence checks and webhooks that call home, may assume IPv4 and fail from an IPv6-only host. This is exactly the kind of thing that bites specialised workloads — a VPS running a VPN where clients expect a stable IPv4 exit, or a game server whose players connect from IPv4-only home networks. The safe rule is boring but reliable: for anything user-facing, insist on a dedicated IPv4 and enable IPv6 alongside it; save the IPv6-only and shared-IP plans for internal or outbound-only machines where you fully control both ends. Get that right up front and the IP address goes back to being the boring detail it should have been all along.