A native IPv6 /56 per instance
Every instance gets its own /56 (256 /64 subnets) from WawaCloud's ARIN-registered 2602:f32a::/40, free to split across containers, virtual interfaces and services.
COMING SOON · PHOENIX, ARIZONA
IPv6-only VPS, with full reach to the IPv4 internet.
On December 26, 2026, WawaNode launches IPv6-only cloud servers in Phoenix. Each instance gets its own native IPv6 block instead of a dedicated IPv4 address; when it reaches an IPv4-only site or API, WawaNode-operated DNS64 resolvers and NAT64 gateways translate the connection.
Pre-registration open · not on sale yet
- Launch date
- Dec 26, 2026
- Datacenter
- Phoenix, US
- IPv6 per instance
- /56
- IPv4 reach
- NAT64 + DNS64
- First-phase capacity
- 600 instances
HOW IT WORKS
IPv6 goes direct; IPv4 is translated at the edge.
IPv6-ready destinations are reached natively. For IPv4-only ones, DNS64 and NAT64 translate at the network edge — nothing to configure on the server.
WHAT YOU GET
One less IPv4 address, nothing else missing.
IPv4 sites still reachable
When a site, package mirror or API only has IPv4, our DNS64 resolvers and NAT64 gateways translate the connection. Images use our DNS64 resolvers by default, so it works from first boot.
Same datacenter, same network
Runs on the same Phoenix hosts and international BGP uplinks as our current US West plans, with the same CPU, memory and disk sizes, starting at 1 core / 1 GB.
A lower price
No dedicated IPv4 address, so each plan costs less than the same dual-stack plan. Prices and launch-sale pricing are published before sales open.
The full VPS toolkit
Full root, plus the same power controls, reinstalls, VNC console, snapshots and traffic stats as our existing VPS plans.
A traceable shared egress
Each instance is mapped to a fixed port range on the shared IPv4 egress, so an abuse report points to exactly one instance and never to its neighbours. Outbound port 25 is closed.
COMPATIBILITY
What just works, and what to watch for.
Works out of the box
- Websites, APIs and package sources reached by name (apt, dnf, pip, npm, Docker images and so on), whether they are IPv4-only or IPv6-ready.
- Outbound SSH, HTTPS, Git and other connections made by hostname.
- Visitors with IPv6 reach your services directly. Home broadband and mobile networks in mainland China now widely hand out IPv6 addresses.
Worth knowing
- Software that dials a hard-coded IPv4 address (not a hostname) bypasses DNS64. 464XLAT (clatd) fixes this; a setup guide ships at launch.
- Switching DNS to a resolver without DNS64 (such as 1.1.1.1 or 8.8.8.8) breaks IPv4-only names. Keep our resolvers, or use a public DNS64 such as 2001:4860:4860::6464.
- IPv4-only visitors can't reach your server directly. Put a CDN in front, or choose one of our existing dual-stack plans.
- No inbound IPv4, and outbound SMTP on port 25 is closed.
LAUNCH PLAN
From pre-registration to launch.
01
November 2026
Pre-registration opens
This page goes live and signed-in customers can reserve. Reserving is free, isn't an order, and can be changed or withdrawn any time.
02
Early–mid December 2026
Internal pilot
We deploy DNS64 resolvers and a redundant pair of NAT64 gateways in Phoenix and run connectivity, compatibility and load tests. Pilot instances are for internal testing only and are not sold.
03
December 26, 2026
On sale in Phoenix
The IPv6-only plans go on sale with launch-sale pricing on day one. Customers who reserved get the launch email first.
04
First three months
First-phase capacity: 600 instances
Gateways, resolvers and the IPv4 egress are sized for 600 instances in the first phase, then expanded with reservations and actual sales.
NETWORK & OPERATOR
Our own address space, our own network.
- Autonomous system
- AS402799
- IPv6 allocation
- 2602:f32a::/40 (registered with ARIN); Phoenix uses 2602:f32a::/44
- Location
- Phoenix, Arizona, United States
- NAT64 prefix
- 64:ff9b::/96 (RFC 6052 well-known prefix)
- Translation design
- Stateful NAT64 (RFC 6146) with DNS64 (RFC 6147), optional 464XLAT (RFC 6877); two gateways in an active/standby pair
- IPv4 egress pool
- Used only for translation and kept separate from the dedicated IPv4 addresses we sell; the exact range is published here before launch
RESERVE
Hold your spot — we'll tell you the moment it opens.
Tell us how many instances you plan to run and what for. We size the first batch from reservations and email reserved customers first.
Checking your reservation…
FAQ
About IPv6-only VPS
Why go IPv6-only?
IPv4 addresses ran out years ago and keep getting more expensive; a dedicated IPv4 is a large part of a VPS's cost. Most servers mainly reach out to other services and don't need to be reachable over IPv4, so for them IPv6-only costs less without giving anything up.
Can I reach IPv4-only websites?
Yes. As long as you connect by name, DNS64 returns a 64:ff9b:: address, the NAT64 gateway in Phoenix carries the connection out over IPv4, and replies come back the same way — transparent to your software.
Does my server get its own IPv4 address?
No. Outbound IPv4 traffic shares an egress address, with a fixed port range reserved for each instance; inbound is IPv6 only. If you need a dedicated IPv4, choose one of our existing dual-stack plans.
Does reserving cost anything?
No. A reservation isn't an order: nothing is charged and no price or stock is held. We email you when sales open and you decide then.
What will it cost?
Every plan will cost less than the same dual-stack plan. Prices and launch-sale pricing are published on this page and the product page before sales open.
This page describes a launch plan; details may change before sales open, and the product page at launch is authoritative. Last updated: 2026-11-10.