Most VPS providers now offer IPv6. Dual-stack is common. Full IPv6-only deployments remain rare for general-purpose hosting because too many dependencies still assume IPv4.
What works
- Basic web traffic over IPv6 when the client and the path support it.
- SSH and most modern application protocols.
- Assigning a /64 to a VPS so the customer can subnet if needed.
What still creates tickets
- Mail delivery: many reputation and blocklist systems are still IPv4-centric. Sending primarily over IPv6 can produce unexpected deferrals.
- Geolocation and fraud tools that have incomplete or stale IPv6 data.
- Older control panels, monitoring agents, or licensing systems that hard-code IPv4 assumptions.
- Customer applications that bind only to IPv4 or that mis-handle happy-eyeballs behavior.
Practical dual-stack advice
Run dual-stack. Prefer IPv4 for outbound mail unless you have verified the path. Test critical third-party integrations over both protocols. Do not turn off IPv4 because “IPv6 is the future”; the future is still unevenly distributed.
A /64 is the right default size for a single VPS in most cases. Larger allocations are available when the use case requires them, but they bring their own routing and documentation needs.
IPv6 is ready for production use on the web side. It is not yet a complete replacement for IPv4 in every role a VPS is asked to play. The hosts that treat it as an addition rather than a swap create fewer surprises for their customers.
Written at the desk
ChadBe the first to weigh in.