IPv6 Subnet Calculator

Understanding IPv6 Subnetting

IPv6 addresses are 128-bit identifiers written as eight groups of four hexadecimal digits separated by colons (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). The vast address space of 2^128 addresses eliminates the need for NAT and provides enough subnets for every organisation to have a /48 prefix (65,536 subnets) with /64 subnets for each network segment. Two shorthand rules simplify IPv6 notation: leading zeros within each group can be omitted, and one contiguous sequence of zero groups can be replaced with ::.

Subnetting in IPv6 follows a similar principle to IPv4 but with significantly more flexibility. The prefix length (e.g., /64) determines how many addresses belong to the subnet. Common prefix lengths include /64 (standard for most networks, providing 18,446,744,073,709,551,616 addresses per subnet), /56 (typically assigned to customer sites by ISPs), /48 (assigned to organisations), and /32 (assigned to larger ISPs). The /64 boundary is especially important because SLAAC (Stateless Address Auto-Configuration) requires a /64 subnet to generate host addresses from the interface identifier.

Our IPv6 subnet calculator takes any valid IPv6 CIDR notation, expands it to the full 32-character address with all leading zeros, and then intelligently shortens it using the :: notation for the longest sequence of zero groups. It also displays the prefix length and the total number of addresses in the subnet, which can be extremely large due to the 128-bit address space. This tool is essential for network engineers planning IPv6 deployments, auditing existing allocations, and understanding the relationship between different prefix lengths in hierarchical addressing schemes.

IPv6 Address Types and Allocation

IPv6 defines several address types with distinct scopes. Global Unicast Addresses (GUA) start with 2000::/3 and are routable on the public internet, analogous to public IPv4 addresses. Unique Local Addresses (ULA) use fc00::/7 and are the IPv6 equivalent of RFC 1918 private addresses — intended for internal networks, they are not routable on the global internet. Link-Local addresses (fe80::/10) are automatically assigned to every IPv6 interface and are used exclusively for communication on a single network segment, such as Neighbor Discovery Protocol (NDP) operations and routing protocol adjacencies.

Unlike IPv4, IPv6 mandates that every interface can have multiple addresses simultaneously — a link-local address for local communication, potentially a ULA for internal reachability, and one or more GUAs for global connectivity. The /64 boundary is critically important: SLAAC (Stateless Address Auto-Configuration) requires a /64 subnet to derive the interface identifier from the EUI-64 or privacy extension mechanism. Using smaller prefixes such as /68 or /72 breaks SLAAC compatibility and may cause connectivity issues with hosts that expect a /64 boundary. When planning IPv6 deployments, always allocate on nibble (4-bit) boundaries for clean summarisation, and reserve sufficient space for each site or region using a hierarchical scheme that mirrors your organisational structure.