Skip to content
QKQuickKit日本語
ReferenceLOCALRuns in your browser

IPv6 Prefix Cheat Sheet

Quick reference for IPv6 prefix lengths — address counts, /64 subnet counts, typical use — plus the common special-purpose prefixes.

This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.

Prefix lengths

PrefixAddresses/64 subnetsTypical useReference
/02^1282^64Default route / all addresses
/32^1252^61Global unicast space (2000::/3)RFC 4291
/122^1162^52IANA block delegated to a regional registryRIR policy
/202^1082^44Large registry allocationRIR policy
/292^992^35Common initial allocation to an LIRRIR policy
/322^962^32Typical ISP / LIR allocationRIR policy
/402^882^24Large ISP allocationRIR policy
/442^842^20Typical ISP / LIR allocationRIR policy
/482^802^16Common site / enterprise assignmentRIR / ISP policy
/522^762^12Site subdivided into building / department blocksOperational practice
/562^722^8Common residential / small-site assignmentISP policy
/602^682^4Common residential / small-site assignmentISP policy
/642^641Typical /64 subnet and 64-bit IID boundary for most IPv6 unicast links. Addressing architecture: RFC 4291; SLAAC: RFC 4862RFC 4291
/962^32within a /64Point-to-point or infrastructure linksOperational practice
/1122^16within a /64Point-to-point or infrastructure linksOperational practice
/1202^8within a /64Point-to-point or infrastructure linksOperational practice
/1262^2within a /64Inter-router link (older practice)Operational practice
/1272^1within a /64Inter-router point-to-point link (RFC 6164)RFC 6164
/1281within a /64Single host, loopback, or anycast addressRFC 4291

Special-purpose prefixes

BlockNameReference
::/0Default routeRFC 4291
::/128Unspecified addressRFC 4291
::1/128Loopback addressRFC 4291
::ffff:0:0/96IPv4-mapped IPv6 addressRFC 4291
64:ff9b::/96NAT64 well-known prefixRFC 6052
64:ff9b:1::/48NAT64 local-use prefixRFC 8215
100::/64Discard-only address blockRFC 6666
2000::/3Global unicastRFC 4291
2001::/32Teredo tunnelingRFC 4380
2001:2::/48BenchmarkingRFC 5180
2001:20::/28ORCHIDv2RFC 7343
2001:db8::/32DocumentationRFC 3849
3fff::/20DocumentationRFC 9637
2002::/166to4RFC 3056
fc00::/7Unique local address (ULA)RFC 4193
fe80::/10Link-local unicastRFC 4291
ff00::/8MulticastRFC 4291

Assignment and allocation sizes (/29, /32, /48, /56, /60) are RIR / ISP policy or operational practice, not RFC requirements — RFC 6177 deliberately does not define a fixed end-site size. Only /64 and /127 are fixed by a standard. The special-purpose table is a curated subset, not the full IANA registry.

How it works

The first table lists common IPv6 prefix lengths from /0 to /128 with the number of addresses (as a power of two), the number of /64 subnets, and the operational context. Only a few lengths are fixed by a standard: /64 is the typical subnet and 64-bit interface-identifier boundary for most IPv6 unicast links (addressing architecture, RFC 4291; SLAAC itself is RFC 4862 and does not fix the length), and /127 inter-router links follow RFC 6164. Every other length here — /32 or /29 for an ISP, /48 for a site, /56 or /60 for a home — is an allocation or assignment size set by Regional Internet Registry or ISP policy, or by operational practice, and it varies between registries and providers. RFC 6177 (which obsoletes RFC 3177) is often cited here, but it does the opposite of prescribing a size: it withdrew the earlier fixed "/48 to every end site" recommendation and left the choice to the operational community, so this table treats it as the reason there is no single standard size rather than as a source for one. The second table is a curated subset of the IANA IPv6 Special-Purpose Address Registry and the addressing architecture: loopback, unspecified, link-local, unique-local, multicast, documentation, NAT64, and more. This is a static reference; use the IPv6 CIDR Calculator or IPv6 Address Type tool for a specific address.