A VPS that ships with a single IPv4 address and nothing else: is that still a defensible setup in 2026? The question comes up with every order, and most answers online blur two separate topics — IPv4 scarcity and whether IPv6 actually matters for one machine running a website, a business app, or a store. Here is what happens in practice, what every Open Vista NVMe VPS plan includes, and what you should insist on seeing in writing before you sign a hosting contract.
IPv4 and IPv6: Two Protocols, Two Logics
IPv4 encodes each address in 32 bits, a little over 4.3 billion combinations. That pool has been handed out to the last block, so IPv4 is now a resale market where addresses trade at a premium. IPv6 answers the root problem with 128 bits — a space that will not run out, and enough to give a public address to every machine, container, and phone without any address translation.
In practice the two coexist. A growing share of mobile and residential traffic arrives over IPv6, while plenty of corporate networks, industrial controllers, point-of-sale terminals, printers, and partner APIs are still IPv4-only. A server that listens on one family serves part of its audience — sometimes the wrong part. That is why the reference setup is called dual-stack: the server answers on IPv4 and on IPv6, and the client picks.
Three misconceptions are worth clearing up. IPv6 is not faster: over the same network path the latency is identical — under 5 ms from New York, about 8 ms from Ashburn, 10–20 ms from Montreal, roughly 14 ms from Toronto, on either protocol. IPv6 does not improve security by itself; it moves the rules around, it does not remove them. And a VPS without IPv6 is not obsolete — it is simply missing half of the stack, which is fixable.
Why a Dedicated IPv4 Is Still Hard to Replace
NAT kept the internet standing long after IPv4 ran out: several machines share one public address and a device handles the translation. That clever patch has a cost, and the cost is exactly what makes a dedicated IPv4 valuable on a server.
Four uses make it hard to give up:
- Port forwarding. Behind shared NAT — carrier-grade NAT on mobile networks, for instance — you no longer control redirection. Any service that must be reachable directly (SSH, a site-to-site VPN, a game server, an inbound webhook) assumes a public address you own.
- Reputation. A mail server or an exposed API lives on the trust attached to its address: PTR record, blocklists, history. Sharing an address with strangers means inheriting their reputation, good or bad.
- Allowlists. Many third-party APIs, payment gateways, and corporate firewalls still filter on IPv4 ranges. Without a stable IPv4 address, every integration turns into a negotiation.
- Legacy clients. A ten-year-old fleet, controllers, entry-level network gear: a good part of the field is IPv4 and will stay that way for a while.
Open Vista NVMe VPS plans include one dedicated IPv4 address per server, unlimited bandwidth, root access, a management panel (web console, reboot, reinstall, DNS), automatic backups, a firewall with DDoS protection, 24/7 supervision, support six days a week, a 99.9% SLA on infrastructure, and delivery in under 15 minutes after your order.
What IPv6 Actually Buys You
Three real gains
A public address per machine, with no NAT and no port redirection; routes that aggregate cleanly, which simplifies life for the host; and an end to address sharing between customers, so reputation is genuinely yours. On a server running containers, each one can have its own address instead of hiding behind a port.
What it does not fix
It does not remove IPv4 traffic — your visitors and partners decide that, not you. It does not replace a firewall or supervision, and it does not substitute for a dedicated IPv4 when it comes to mail, allowlists, and inbound ports. Above all, dual-stack costs operational effort: two rule sets, two log sets, two test sets.
Running Dual-Stack Without Breaking Things
If the plan you pick includes an IPv6 prefix — the first question to ask any provider — the order of operations matters more than the configuration itself.
DNS first
One A record for IPv4, one AAAA for IPv6, on the same name, with a short TTL during the cutover. Modern browsers try both families and keep whichever answers faster: an AAAA pointing at a powered-off machine produces intermittent slowness rather than a clean outage. That is the classic trap, and it costs hours of troubleshooting.
Firewall and listeners next
A service listening on 0.0.0.0 answers over IPv4 only: it also needs ::, plus filtering rules in both families. A well-tuned IPv4 firewall next to an open IPv6 stack is an exposed server. Check as well that your management panel and backups cover the IPv6 configuration, or you will not be able to restore it.
Tests last
Query the AAAA record, test with curl -6, then from a mobile network and from a corporate one — usually IPv4-only. Write both paths down: that is what separates a controlled cutover from a Monday-morning surprise.
What to Check in the Hosting Contract
Six points are worth having in writing before you pay:
- How many IPv4 addresses are included, and whether they are dedicated or shared.
- Whether an IPv6 prefix exists, its size, and how it is assigned.
- Reverse DNS: can you edit it yourself, or only on request?
- The reputation policy if the address you inherit is already listed somewhere.
- The price of an extra address, and the terms if you change plan.
- What the SLA covers — here 99.9% on infrastructure — and what it explicitly excludes.
All five NVMe VPS plans include a dedicated IPv4, and the servers run in New York. A Rabat data center has been announced but is not open yet, so do not plan around it. The rate used across the site is 1 USD ≈ 9.46 MAD.
| Plan | vCPU | RAM | NVMe | Dedicated IPv4 | USD/mo | MAD excl. tax |
|---|---|---|---|---|---|---|
| VPS-1G Démarrage | 1 | 1 GB | 30 GB | 1 | 9.99 | 94.48 |
| VPS-2G Business | 1 | 2 GB | 40 GB | 1 | 19.99 | 189.06 |
| VPS-3G Performance | 2 | 3 GB | 50 GB | 1 | 34.99 | 330.93 |
| VPS-4G Avancé | 2 | 4 GB | 80 GB | 1 | 39.99 | 378.22 |
| VPS-5G Ultra | 3 | 5 GB | 100 GB | 1 | 49.99 | 472.80 |
Full configurations, options, and payment methods are on the NVMe VPS page.
FAQ
Do I need IPv6 to rank well?
No. Search engines reach your site over IPv4 just as well as over IPv6; the address family changes neither crawling nor ranking. What counts is load speed, content quality, and server stability. IPv6 is an infrastructure topic, not an SEO one.
Is a VPS without IPv6 outdated?
No, as long as your visitors, customers, and partners are reachable over IPv4 — still true for most corporate networks. A server delivered with a dedicated IPv4 remains perfectly usable. The day a partner or carrier exposes IPv6 only, dual-stack becomes necessary.
Can I get more than one IPv4 address?
Each plan includes one dedicated IPv4. The number of extra addresses and their price are not in the public price list: ask for written confirmation before ordering, and state what you need them for.
What happens if I upgrade my plan?
Moving to a larger plan is possible at any time without a painful migration. Still confirm what happens to your addresses and DNS records during the change — that is a question to ask before, not after.
The Short Version: Keep IPv4, Prepare IPv6
In 2026 a well-delivered server means a dedicated IPv4 you own, a reverse DNS record you control, and IPv6 available the day you need it. Everything else — dual-stack, testing, supervision — is execution. If you are about to order, start from the VPS lineup and check every point in the contract; for the domain name and the A and AAAA records, the domains page covers available extensions and the right habits.