IPv4 vs IPv6: What Actually Changed and Why It Took 30 Years

The fundamental problem

IPv4 addresses are 32 bits — 2³² ≈ 4.3 billion total. The public internet runs out of them every few years and extends its life with NAT (many private devices sharing one public address). IPv6 addresses are 128 bits — 2¹²⁸ ≈ 3.4 × 10³⁸. Enough to give every atom on Earth's surface 100 unique addresses. The problem is genuinely solved.

Side-by-side

	IPv4	IPv6
Address bits	32	128
Example	192.168.1.1	2001:db8::1
Address space	~4.3 billion	~3.4 × 10³⁸
Header size	20+ bytes (variable)	40 bytes (fixed)
Checksum in header	Yes	No (deferred to L4)
NAT	Ubiquitous	Unnecessary (but possible)
Autoconfiguration	DHCP required	SLAAC built-in
Multicast	Optional	Built-in
Fragmentation	Routers can fragment	Only senders fragment
Adoption (2026)	100%	~45% of global users

Why the migration took so long

IPv6 was finalized in 1998. It's 2026 and only 45% of users have it. The reasons:

• Not backward-compatible. IPv6 packets are not IPv4 packets; every router and host needs native support.
• NAT let IPv4 survive. Hiding thousands of devices behind one public IP postponed the address exhaustion crisis.
• No user-visible benefit. Pages don't load faster on IPv6 unless you're on a network where IPv4 is congested.
• Carrier-grade NAT. ISPs deployed CG-NAT to extend IPv4 further, adding one more layer.

Why IPv6 is actually better (beyond more addresses)

• Simpler headers. Fixed 40-byte header; extensions are chained. Routers process packets faster.
• No NAT hell. Every device gets a real address. Peer-to-peer applications (VoIP, gaming, video calls) work without NAT traversal tricks.
• SLAAC (Stateless Address Autoconfiguration). Devices configure their own addresses from the router's prefix advertisement — no DHCP server required for basic networking.
• Built-in multicast. One packet to many recipients, in-network.
• Privacy extensions. Random temporary addresses prevent cross-session tracking via MAC-derived suffixes.

Notation quirks to know

• Eight groups of 4 hex digits separated by colons: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
• Leading zeros droppable: 2001:db8:85a3:0:0:8a2e:370:7334
• Consecutive zero groups collapse to :: (once per address): 2001:db8:85a3::8a2e:370:7334
• Loopback: ::1 (vs 127.0.0.1)
• In URLs: wrap in brackets — http://[2001:db8::1]/

Does your server need IPv6?

Yes, ideally. For consumer-facing services, serving IPv6 improves access for users on IPv6-only networks (common in parts of Asia and on mobile carriers). Major clouds give you AAAA records with a checkbox. There's no downside.

Inspecting addresses

For IP lookups (country, ASN, organization): IP address lookup. For converting IPs to binary (rare but useful for subnetting): IP to binary.