Short answer: An IPv6 /32 contains 65,536 /48 blocks, but a /48 can be sufficient for a single organisation or site. Choose based on customer, subnet and routing needs rather than address count alone.
Choose a size from your addressing plan
In IPv6 prefix notation, a smaller prefix-length number describes a larger block. A /32 therefore contains more address space than a /48. That arithmetic does not mean every business needs a /32: the right choice depends on the network and the resource arrangement.
A /32 contains 65,536 /48-sized blocks. A /48 contains 65,536 /64-sized subnets. These are mathematical capacities, not a recommendation to allocate every part or a promise that every subnet can be announced independently.
For ISP customer allocation examples, read the IPv6 addressing plan for ISPs and hosting providers.
For a practical protocol decision, read IPv4 vs IPv6 for small networks in 2026.
When a /48 may be enough
A single organisation or site can often build a substantial internal subnet plan within a /48. If your connectivity provider already supplies suitable IPv6 space, check whether that arrangement meets your addressing, routing and continuity needs before taking on a separate lease.
Address count is only one consideration. Ask whether you may announce the prefix from the intended ASN, what happens if you change upstream, and what renumbering would be needed when the arrangement ends.
When to assess a /32
A hosting provider, ISP or infrastructure operator serving many customers or sites may need room for a hierarchical addressing plan. A /32 allows space to be organised into regions, sites or customer blocks, subject to the resource agreement and applicable policies.
Write down the number of sites and customers, the prefix sizes each needs, and the growth you realistically expect. Leave room for aggregation and expansion. A large block without a workable allocation plan will not solve operational problems.
Addressing and public routing are separate decisions
Subdividing a block for internal use does not mean you should announce every subdivision to the Internet. Agree an announcement plan with your upstream, and align any ROAs and route6 objects with it. Read the IPv6 routing checklist before activation.
A short decision checklist
- How many sites and customers need their own prefixes?
- What space is already available from your connectivity provider?
- Which ASN will originate the route, and will your upstream accept it?
- Who maintains registry records, authorisations and reverse DNS?
- What is your plan for expansion, termination and renumbering?
Where ELISTEKA fits
ELISTEKA’s public IPv6 /32 lease is €29 per month with €87 upfront for the first 3 months. An IPv6 /29 contains eight /32s and is €149 per month, or €134 per month equivalent with €1,608 prepaid for 12 months. All figures exclude VAT. /28 and shorter are quoted on request. Business use, ASN and upstream are reviewed before activation; no prefix is reserved until approval. This page does not offer a separate /48 product.
If your plan calls for a /32, compare the service details and requirements with your network design. If it does not, choose the arrangement that matches your actual needs.
Discuss your IPv6 /32 requirements
Share your company, intended use and proposed origin ASN. Request an IPv6 /32 lease or email sales@elisteka.com. No payment is collected through the application form.