IPv6-only VPS: practical in 2024?

Back when I started in this business, IPv4 was plentiful and IPv6 was the future that was always coming. Twenty years later, I am still waiting.

For science, I leased an IPv6-only instance from HostHatch last month. $1.50 for 1GB, tempting enough to test. The theory: NAT64 or DNS64 handles legacy, modern stacks prefer v6, costs drop as providers conserve v4 space.

The reality: GitHub pushes fail half the time. Docker registry pulls timeout. My monitoring dashboard—hosted on legacy infrastructure—cannot reach the instance. I spent more hours debugging connectivity than the savings justified.

The final insult: HostHatch's "IPv6-only" actually runs CGNAT fallback for v4 egress. So I am sharing a v4 address with hundreds of instances, blacklisted on every reputation list, unable to send email or even apt-get reliably. The point of v6-only is supposed to be purity. This is pollution wearing a v6 hat.

Kids these days will call this progress. Mark my words: v4 scarcity will drive prices up, but v6-only remains a toy for enthusiasts until the last legacy service dies. That day is not 2024. Perhaps not 2030.

Ipv6 only but who cares at that price!! My wireguard endpoint is v6, tracker works fine, seedbox basically free

BUT yeah github is pain, had to mirror to codeberg first then pull from there

Price history: was $18 in 2023, $15 in 2024, now $12. Trend is YOUR FRIEND

https://www.wireguard.com

Hey folks, just a gentle reminder to keep provider naming factual and avoid speculation about network architecture we cannot verify.

@svendeal appreciate the enthusiasm, but if you're using it as a seedbox, please review our terms on acceptable use—P2P policy varies by provider and we do not want members caught off guard.

On topic: I ran IPv6-only for a personal blog for six months. Worked fine with Cloudflare in front for v4 gateway. Without that layer, pain was real. Would not recommend for production unless your entire stack is v6-native.