Does GitHub work on an IPv6-only server?

Not directly. As of our check in September 2026, github.com, api.github.com, objects.githubusercontent.com (release downloads) and ghcr.io publish no IPv6 addresses, so git clone, the API and container pulls from GitHub fail. raw.githubusercontent.com does have IPv6.

Can I run a Discord bot on IPv6-only?

No — discord.com and the Discord gateway had no IPv6 addresses in our check. A Telegram bot is fine: api.telegram.org answers over IPv6.

Why are IPv6-only servers cheaper?

IPv4 addresses are scarce and cost providers real money every month; IPv6 addresses are practically free. An IPv6-only plan passes that saving on, at the cost of breaking anything that only speaks IPv4.

How do I check whether a service supports IPv6?

Run 'dig +short AAAA hostname'. No output means no IPv6 address. On a dual-stack machine, 'curl -6 -sI https://hostname' confirms it actually answers over IPv6.

Does EQVPS sell IPv6-only plans?

No. Every EQVPS plan reaches the internet over IPv4: NAT plans connect out through NAT and you reach them on a personal SSH port, and dedicated plans have their own public IPv4. NAT plans start at $3/mo, which covers the budget use case without IPv6-only headaches.

IPv6-only VPS: what works and what breaks in 2026

IPv6-only servers are cheap for a simple reason: IPv4 addresses are scarce and cost money every month, IPv6 addresses don't. So the question isn't whether IPv6-only is cheaper — it is — but whether the things you actually use still work. We checked in September 2026 instead of repeating year-old forum answers.

What we tested, and the result

We looked up the IPv6 (AAAA) records of services a typical server touches on day one. No AAAA record means an IPv6-only machine can't reach it without help.

Service	IPv6 as of 26 Sep 2026
github.com, api.github.com	❌ no
objects.githubusercontent.com (release downloads)	❌ no
ghcr.io (GitHub container registry)	❌ no
raw.githubusercontent.com	✅ yes
Docker Hub (registry-1.docker.io)	✅ yes
PyPI, npm, crates.io, Go module proxy	✅ yes
Debian / Ubuntu / Alpine package mirrors	✅ yes
GitLab	✅ yes
Let's Encrypt (ACME)	✅ yes
Telegram Bot API	✅ yes
discord.com and the Discord gateway	❌ no
OpenAI, Anthropic, Google Gemini APIs	✅ yes
Hugging Face (site)	✅ yes — but its large-file CDN host: ❌ no
ollama.com	❌ no (registry.ollama.ai: ✅ yes)
Binance API	❌ no
Coinbase API	✅ yes

The pattern: package managers, big AI APIs and Telegram are ready. GitHub — the one service nearly every server needs — still isn't.

What that means in practice

On an IPv6-only VPS you'll hit walls in exactly these places:

git clone https://github.com/... fails. So do install scripts that curl a GitHub release, and anything pulling images from ghcr.io.
Discord bots can't connect to the gateway at all.
Some model downloads break: Hugging Face's large-file host and ollama.com had no IPv6 in our check.
Crypto bots on IPv4-only exchanges can't reach the API.

And a quieter one on the inbound side: visitors on IPv4-only networks can't reach a site hosted on an IPv6-only server unless you put a proxy or CDN with IPv4 in front of it.

Test any service in two seconds

dig +short AAAA github.com          # empty output = no IPv6
dig +short AAAA api.telegram.org    # addresses = IPv6 available
curl -6 -sI https://pypi.org | head -1   # on a dual-stack box: proves it answers over v6

Run this against everything your project talks to before you pick a plan.

Workarounds, and their cost

NAT64/DNS64. A gateway translates IPv6 requests to IPv4 destinations. Public ones exist, but you're routing your traffic through someone else's box and depending on their uptime.
Mirrors and proxies. Mirror your GitHub repos to GitLab, push images to Docker Hub, run a small proxy on a dual-stack machine. Workable, but it's plumbing you have to keep alive.
A CDN in front for inbound web traffic, so IPv4 visitors can reach you.

Each fix is fine on its own. Together they eat the few dollars an IPv6-only plan saved.

When you actually need IPv4 — and which kind

For most projects the honest answer is: you want IPv4 connectivity, but not necessarily your own IPv4 address.

If nothing needs to connect into your server — bots, agents, workers, cron jobs — a NAT plan is enough. It reaches every service, IPv4-only ones included, through NAT, and you get in via a personal SSH port. That's the budget option: NAT plans from $3/mo.
If something must connect in — a website, a mail server, a game server, a VPN endpoint — take a plan with a dedicated IPv4.

We don't sell IPv6-only plans for precisely the reasons in the table above: at $3/month for NAT with full IPv4 reach, the savings aren't worth a server that can't clone from GitHub. Still unsure which of the two you need? Here's the one-question test.