IPv4 subnet calculatorNetwork, host range, broadcast, mask and wildcard for any IPv4 blockIPv6 subnet calculatorPrefix ranges, /64 counts, splits and a ULA prefix generatorVLSM calculatorSize subnets by host count, with AWS, Azure, GCP and OCI rulesVisual subnet plannerSplit and join blocks, label them, then share or export the planCIDR and IP range calculatorTurn any start and end address into the fewest CIDR blocksSupernet and route summarySummarise networks into one route or merge them exactlyWildcard mask calculatorACL wildcards, matched ranges and ready Cisco linesSubnetting practiceExam-style questions, checked instantly with the working shownSubnet mask cheat sheetEvery prefix from /0 to /32 with mask, wildcard and hostsIPv6 cheat sheetPrefix sizes, address types and the reserved rangesGuidesHow subnetting works, explained with worked examples

IPv6 subnet cheat sheet

How big each IPv6 prefix is, how many /64s it holds, what the special ranges are, and how to write addresses the canonical way.

Updated Nov 20, 2026Checked against Python ipaddress24 prefix sizes

Prefix sizes

IPv6 prefixes are usually planned on nibble boundaries (multiples of 4) so that each step is one hex digit and reverse DNS delegation stays clean. The /64 column is the number of LAN-sized subnets the prefix holds.

PrefixAddresses/64 subnetsTypical use
/32^1252^61Global unicast space (2000::/3)
/82^1202^56
/122^1164,503,599,627,370,496Typical regional registry allocation
/162^112281,474,976,710,656
/192^10935,184,372,088,832
/202^10817,592,186,044,416
/242^1041,099,511,627,776
/292^9934,359,738,368Common minimum ISP allocation
/322^964,294,967,296Typical ISP allocation (LIR)
/362^92268,435,456
/402^8816,777,216
/442^841,048,576
/482^8065,536One site or organisation
/522^764,096
/562^72256Typical home or small business delegation
/602^6816Some ISPs delegate this to homes
/642^641One LAN or VLAN (SLAAC needs /64)
/80281,474,976,710,656part of one
/964,294,967,296part of oneNAT64 prefix (64:ff9b::/96)
/11265,536part of one
/120256part of one
/1264part of one
/1272part of onePoint-to-point link (RFC 6164)
/1281part of oneOne address (loopback, host route)

Address types

The first bits of an IPv6 address tell you what kind it is. These are the ranges you will meet on real networks.

PrefixTypeDefined in
2000::/3Global unicast, routable on the internetRFC 4291
fc00::/7 (in practice fd00::/8)Unique local, the private rangeRFC 4193
fe80::/10Link-local, every interface has oneRFC 4291
ff00::/8MulticastRFC 4291
::1/128LoopbackRFC 4291
::/128UnspecifiedRFC 4291
::ffff:0:0/96IPv4-mappedRFC 4291
64:ff9b::/96NAT64 well-known prefixRFC 6052
2001:db8::/32Documentation and examplesRFC 3849
2002::/166to4 (deprecated)RFC 3056

Writing addresses

RFC 5952 defines one canonical text form so that the same address is always written the same way:

  • Use lowercase hex digits.
  • Drop leading zeros in each 16-bit group: 0db8 becomes db8.
  • Replace the longest run of all-zero groups with ::, once. If two runs are equally long, shorten the first.
  • Do not use :: for a single zero group: write 2001:db8:0:1:1:1:1:1.
  • Put the prefix length after a slash: 2001:db8::/32. In URLs wrap the address in brackets: [2001:db8::1]:443.
Written asCanonical form
2001:0DB8:0000:0000:0000:0000:0000:00012001:db8::1
2001:db8:0:0:1:0:0:12001:db8::1:0:0:1
fe80:0:0:0:0:0:0:1fe80::1

Planning on nibble boundaries

Each hex digit is four bits, so a nibble-aligned plan lets people read the hierarchy straight from the address. A common enterprise layout:

  • /48 per site: 2001:db8:acad::/48
  • /52 per building or zone: 16 per site
  • /56 per function or floor: 256 per site
  • /64 per VLAN: 65,536 per site
  • /127 per router-to-router link, taken from a reserved /64

Read our IPv6 subnetting guide for a worked plan, or open the IPv6 calculator to split a prefix.

How we check this page

Every figure on this site comes from the same calculation engine as the tools, and that engine is tested on each build against more than 6,600 cases generated by Python's standard ipaddress module. Rules are taken from the RFCs and vendor documents listed under Sources. Last reviewed November 20, 2026.