Short answer: IPv6 is suitable for many modern network services, but a small network may still need IPv4 for legacy users, partners and applications. Dual stack is often the practical transition; IPv6-only works only after testing dependencies and translation requirements.
For IPv4 onboarding, see the /24 guide for hosting and cloud providers. For IPv6 customer allocations, use the ISP and hoster addressing plan.
What IPv4 and IPv6 solve
IPv4 remains widely used and may be required for services or customers that cannot connect over IPv6. IPv6 provides a much larger address space and supports direct addressing without relying on shared public IPv4 for every endpoint. Neither protocol supplies connectivity by itself; upstream routing, firewall policy, DNS and application support still matter.
When IPv4 is still needed
- Customers, partners or APIs connect only over IPv4.
- Legacy equipment, monitoring, VPNs or management tools do not support IPv6.
- Third-party allowlists or service dependencies require a public IPv4 address.
- You need an IPv4-facing service while migrating clients and infrastructure to dual stack.
When IPv6 may be enough
IPv6-only can work for a service whose users, upstreams, management plane and dependencies are IPv6-capable, or where tested translation provides access to IPv4-only destinations. Check DNS behaviour, monitoring, abuse handling, customer equipment and support procedures. Do not infer IPv6-only readiness from a successful ping or one application test.
Dual stack and CGNAT trade-offs
Dual stack keeps IPv4 reachability while introducing IPv6, but it requires operating two protocol paths, security policies, monitoring and troubleshooting. Carrier-grade NAT (CGNAT) can share a smaller public IPv4 pool among many subscribers. It also introduces translation state, port mapping, logging, troubleshooting and possible application-compatibility work. The actual equipment and operating cost depends on traffic, concurrency, logging requirements, scale and architecture; there is no single universal cost figure.
IPv6 can reduce dependence on shared IPv4 for IPv6-capable traffic, but it does not instantly remove the need for IPv4. Plan a staged migration based on observed dependencies.
Compare the leasing options
Elisteka's published IPv4 /24 reference rate is €105 per month excluding VAT. All current IPv4 space is fully leased, so new requests go to the IPv4 waiting list. This is not an immediate availability offer.
The IPv6 /32 lease is €29 per month excluding VAT, with the first 3 months (€87) paid upfront. See IPv6 /32 leasing, aggregate IPv6 inventory and the published price list.
Frequently asked questions
Can a small network use IPv6 only?
Sometimes, if users, applications, management systems and upstream connectivity are reachable over IPv6 or suitable translation services. Test actual dependencies before removing IPv4.
When is IPv4 still needed?
IPv4 may still be required for legacy customers, partner networks, APIs, monitoring systems or services that are not reachable over IPv6. Requirements vary by application and user base.
Does IPv6 remove the need for CGNAT?
IPv6 can reduce pressure on shared IPv4 addressing for IPv6-capable traffic, but it does not automatically remove IPv4 demand. CGNAT may still be needed for IPv4-only destinations or subscribers.
What are the CGNAT trade-offs?
CGNAT conserves public IPv4 addresses but adds translation state, logging, troubleshooting and application-compatibility work. Evaluate equipment, operations and legal logging obligations for your own network; there is no universal cost figure.
Can I lease IPv4 from Elisteka now?
All current Elisteka IPv4 space is fully leased. New requests go to the waiting list and are not a reservation or guaranteed start date.
What is the IPv6 /32 lease price?
The published price is €29 per month ex-VAT, with the first 3 months (€87) paid upfront.
For IPv4, join the waiting list. For IPv6, request a /32 review. Include your ASN, upstream and intended use so the technical fit can be assessed.