IPv4 vs. IPv6: Address Exhaustion and the Path Forward

Every device connected to the internet needs an address. For over four decades, that address came from a pool of roughly 4.3 billion possibilities defined by IPv4. That sounds like a lot. Then you consider that there are now over 15 billion connected devices worldwide. Phones, laptops, smart TVs, thermostats, industrial sensors, and everything in between. The math simply does not work anymore.

IPv6 was designed to fix this. It expands the address space from 32 bits to 128 bits. This creates a number of addresses so large the human brain cannot meaningfully comprehend it. But IPv6 is not just about more addresses. It also introduces a simplified header, mandatory security features, and built-in autoconfiguration. These changes reflect lessons learned from decades of running IPv4 at scale.

The transition reached a milestone in early 2026. On March 28, 2026, IPv6 traffic on Google’s network exceeded 50% for the first time in history. After 18 years of measurement, the majority line was finally crossed. This guide breaks down the IPv4 vs IPv6 comparison in practical terms. This guide covers six topics. How each protocol works. Why IPv4 ran out. How the transition is happening. Where adoption stands today. And what it all means whether you are a regular user, network administrator, or software developer. To start with address structure basics, our guide to IP address formats is a useful primer.

What Is IPv4?

IPv4 is the fourth version of the Internet Protocol and the first to be widely deployed. Defined in RFC 791 in 1981, it has been the backbone of internet communication for over 40 years. Addresses are 32-bit numbers written in dotted-decimal notation, giving a maximum of about 4.3 billion total addresses.

Internet Protocol version 4 (IPv4) is the fourth version of the Internet Protocol and the first to be widely deployed. Defined in RFC 791 in 1981, it has been the backbone of internet communication for over 40 years.

An IPv4 address is a 32-bit number, typically written in dotted-decimal notation. Four octets are separated by dots. Each octet represents 8 bits, giving each a range of 0 to 255:

192.168.1.1

In binary: 11000000.10101000.00000001.00000001

With 32 bits, IPv4 provides a theoretical maximum of 2³² = 4,294,967,296 addresses. In practice, large blocks are reserved for private networks, loopback, multicast, and documentation. The usable public address space is significantly smaller.

  192   .   168   .    1    .    1
   |         |        |        |
 Octet 1  Octet 2  Octet 3  Octet 4

Each octet: 8 bits = values 0 through 255
Total:      4 octets × 8 bits = 32 bits
Max value:  255.255.255.255 = 4,294,967,295

Key characteristics of IPv4 include:

• Variable-length header (20-60 bytes) with optional fields that complicate router processing.
• Checksum in the header, recalculated at every hop, adding processing overhead.
• Fragmentation by routers. Intermediate routers can fragment packets, which causes reassembly complexity.
• Broadcast support. A single packet can be sent to all devices on a subnet.
• No built-in security. IPsec is available but optional and was retrofitted after the original design.
• Manual or DHCP-based configuration. Devices need a DHCP server or static configuration to obtain addresses.

To see how IPv4 addresses translate between decimal, binary, and hex, try our IP to binary converter. For a deeper look at the notation and format rules, see our IP address formats guide. To look up your current IP address, see our guide on finding your public IP. It walks through five methods plus what to expect when CGNAT is in play.

What Is IPv6?

IPv6 is the successor to IPv4, defined in RFC 8200. Addresses are 128-bit numbers written as eight groups of four hexadecimal digits separated by colons. This provides about 340 undecillion unique addresses. IPv6 also redesigns the protocol header for simpler routing. It adds built-in IPsec, SLAAC autoconfiguration, and multicast in place of broadcast.

Internet Protocol version 6 (IPv6) is the successor to IPv4, defined in RFC 8200. It was designed in the 1990s when it became clear that IPv4 addresses would eventually run out. Widespread deployment did not begin until the 2010s.

An IPv6 address is a 128-bit number, written as eight groups of four hexadecimal digits separated by colons:

2001:0db8:85a3:0000:0000:8a2e:0370:7334

With 128 bits, IPv6 provides 2¹²⁸ = 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses. That number is commonly described as 340 undecillion. To put it in perspective: roughly 6.5 × 10²³ addresses for every square meter of the Earth’s surface.

IPv6 was not just about adding more addresses. It was an opportunity to redesign the protocol header and fix long-standing issues with IPv4:

• Simplified fixed-size header (40 bytes) with no optional fields in the base header. Routers process packets faster because they do not need to parse variable-length options.
• No header checksum. Link-layer and transport-layer checksums handle error detection. The per-hop checksum recalculation is eliminated.
• No router fragmentation. Only the source host can fragment packets. Routers that receive oversized packets send back an ICMPv6 “Packet Too Big” message. The source then adjusts.
• Mandatory IPsec support. IPsec was designed alongside IPv6 and is built into the protocol specification. End-to-end encryption is native rather than retrofitted.
• Stateless Address Autoconfiguration (SLAAC). Devices can automatically configure their own addresses using the network prefix advertised by routers, without needing a DHCP server.
• Multicast replaces broadcast. IPv6 has no broadcast address. It uses multicast and anycast for one-to-many and one-to-nearest communication, reducing unnecessary network traffic.
• Built-in flow labeling. The Flow Label field in the header helps routers identify packet flows for quality-of-service handling without inspecting the payload.

IPv4 vs. IPv6: Key Differences

Ten major technical differences separate the two protocols. The differences span ten dimensions. These are address length, format, total space, header size, NAT, IPsec, autoconfiguration, broadcast, fragmentation, and checksum. These distinctions matter most when you configure networks, study for certifications, or decide what to support in applications.

The following table summarizes the major technical differences between the two protocols. These are the distinctions that matter most in practice. Whether you are configuring a network, studying for a certification, or deciding what to support in your application.

The elimination of NAT is one of the most significant practical changes. NAT was a clever workaround that allowed thousands of devices to share a single public IPv4 address. But it broke the end-to-end connectivity model that the internet was built on. Peer-to-peer applications, VoIP, online gaming, and IoT devices all work better when every device has a globally routable address. IPv6 restores that model.

Our subnet calculator lets you work with both IPv4 CIDR notation and subnet masks. Use it for a hands-on understanding of how addresses break into network and host portions. If you are new to the concept entirely, start with our beginner’s guide to subnetting.

Why IPv4 Addresses Ran Out

IPv4 had 4.3 billion possible addresses when it was designed in 1981. The internet was an academic research network with a few hundred hosts. Nobody anticipated smartphones, IoT devices, or households with 20+ connected devices. Exhaustion happened gradually as Regional Internet Registries depleted their pools between 2011 and 2020.

When IPv4 was designed in 1981, 4.3 billion addresses seemed virtually unlimited. The internet was an academic research network with a few hundred hosts. Nobody anticipated smartphones, IoT devices, or the fact that a single household might have 20+ connected devices.

The exhaustion happened gradually, then all at once. Here is the timeline of when each Regional Internet Registry (RIR) exhausted its free pool of IPv4 addresses:

The internet did not collapse when addresses ran out. Several stopgap measures had been deployed over the preceding decades:

• CIDR (Classless Inter-Domain Routing). Replaced the wasteful classful allocation system in 1993. Instead of handing out entire Class A, B, or C blocks, CIDR allows allocations of any size. Prefix notation handles sizing (like /22 for 1,024 addresses). This dramatically improved address utilization. For more on variable-length techniques, see our guide to VLSM and supernetting.
• NAT (Network Address Translation). Allows an entire private network to share a single public IP address. Your home router almost certainly uses NAT right now. It translates between your private addresses (like 192.168.x.x) and your single public IP.
• CGNAT (Carrier-Grade NAT). Takes NAT a step further. ISPs use CGNAT to put multiple customers behind a single public IP address. This means your home router’s “public” IP might itself be a shared address. CGNAT works but introduces complications for gaming, VoIP, hosting services, and any application that needs inbound connections. Mobile carriers use CGNAT almost universally. To check if you are behind it, our find your public IP guide walks through the detection method.

The IPv4 Market in 2026

Because IPv4 addresses are scarce and IPv6 adoption is incomplete, an active secondary market exists for IPv4 blocks. Prices fluctuated significantly over the past decade. As of early 2026:

• /24 blocks (256 addresses): about $35-$45 per IP, total roughly $9,000-$11,500
• /22 blocks (1,024 addresses): about $30-$40 per IP
• /16 blocks (65,536 addresses): about $18-$28 per IP, having crossed below $20 for the first time since 2019
• Leasing: platform-wide averages around $0.40 per IP per month, with utilization above 80%

The market has split by block size. Large blocks sit at multi-year lows as institutional supply enters the market. Small /24 blocks have held comparatively firm. Yet IPv4 demand remains strong because of AI workload provisioning, cloud infrastructure expansion, and IoT growth. The market is gradually shrinking, not collapsing. These measures bought time, but they added complexity. NAT breaks the end-to-end model. It complicates DNS resolution and peer-to-peer protocols. It also creates a maintenance burden that grows as networks scale. IPv6 is the real long-term solution.

How IPv6 Addresses Work

IPv6 addresses look unfamiliar at first but follow consistent notation rules. Each address has a 64-bit prefix that identifies the network and a 64-bit interface ID that identifies the device. Several address types exist: Global Unicast, Link-Local, Unique Local, Multicast, and Loopback. Each serves a specific purpose.

IPv6 addresses look unfamiliar at first, but the notation follows consistent rules that become intuitive with practice.

Notation Rules

An IPv6 address is written as eight groups of four hexadecimal digits, separated by colons:

2001:0db8:85a3:0000:0000:8a2e:0370:7334

Two simplification rules make addresses shorter and more readable:

• Leading zeros can be omitted within each group. So 0db8 becomes db8, and 0000 becomes 0.
• One consecutive run of all-zero groups can be replaced with :: (double colon). This can only be used once per address to avoid ambiguity.

Applying both rules to our example:

Full:        2001:0db8:85a3:0000:0000:8a2e:0370:7334
Drop zeros:  2001:db8:85a3:0:0:8a2e:370:7334
Use :::      2001:db8:85a3::8a2e:370:7334

To see how an IPv4 address maps into IPv6 notation, our IPv4 to IPv6 converter handles the translation.

Address Types

IPv6 defines several categories of addresses, each serving a specific purpose:

Example Breakdown: Prefix and Interface ID

A typical IPv6 address is divided into two halves:

2001:0db8:85a3:0001:0000:8a2e:0370:7334
|<---- 64-bit Prefix ---->|<-- 64-bit Interface ID -->|

Prefix:       2001:0db8:85a3:0001
  Routing prefix (48 bits): 2001:0db8:85a3
  Subnet ID (16 bits):      0001

Interface ID: 0000:8a2e:0370:7334
  Identifies the specific device on the subnet
  Can be derived from the MAC address (EUI-64)
  or generated randomly for privacy (RFC 4941)

The 64-bit prefix is analogous to the network portion of an IPv4 address. The 64-bit interface identifier is analogous to the host portion. In most deployments, ISPs assign a /48 or /56 prefix to customers. That gives them 65,536 or 256 subnets respectively. Each subnet contains 2⁶⁴ addresses. You can see your current address assignment by visiting our What Is My IP tool.

The Transition: Dual Stack, Tunneling, and Translation

IPv4 and IPv6 are not directly compatible. Three categories of transition mechanisms allow both protocols to coexist. Dual stack runs both protocols on the same network. Tunneling encapsulates IPv6 inside IPv4 packets. Translation mechanisms like NAT64 and DNS64 let IPv6-only clients reach IPv4-only servers.

IPv4 and IPv6 are not compatible. An IPv4-only device cannot communicate directly with an IPv6-only device. The internet cannot simply flip a switch from one to the other. Three categories of transition mechanisms allow both protocols to coexist during the migration.

Dual Stack

The simplest approach: run both IPv4 and IPv6 simultaneously on the same device, interface, and network. The device gets both an IPv4 address and an IPv6 address. When the device connects to a destination, it checks whether IPv6 is available via DNS AAAA records. It prefers IPv6 if available. It falls back to IPv4 otherwise.

Dual stack is the recommended transition method and the most widely deployed. Most modern operating systems, routers, and applications support it natively. The downside is that network administrators must maintain two complete protocol stacks. Two sets of firewall rules. Two sets of routing tables. Two sets of monitoring configurations.

Tunneling

Tunneling encapsulates IPv6 packets inside IPv4 packets. This lets IPv6 traffic traverse IPv4-only network segments. Several tunneling protocols exist:

• 6to4. Automatically creates tunnels using a special 2002::/16 prefix derived from the device’s IPv4 address. Deprecated (RFC 7526) due to reliability issues but still encountered in legacy configurations.
• Teredo. Designed to tunnel IPv6 through IPv4 NAT devices, which 6to4 cannot handle. Uses UDP encapsulation on port 3544. Built into Windows but considered a last-resort mechanism.
• 6in4 (Protocol 41). A manually configured tunnel that encapsulates IPv6 directly in IPv4. Used by tunnel broker services like Hurricane Electric. Reliable but requires static configuration and does not work behind NAT without port forwarding.
• ISATAP. Intra-Site Automatic Tunnel Addressing Protocol. Designed for enterprise networks to carry IPv6 over an IPv4-only internal infrastructure. Uses the IPv4 address as part of the IPv6 interface identifier.

Translation (NAT64 / DNS64)

NAT64 translates between IPv6 and IPv4 at the network boundary. An IPv6-only client sends traffic to a synthesized IPv6 address that maps to the destination’s IPv4 address. The NAT64 gateway translates the packets and forwards them.

DNS64 works alongside NAT64. An IPv6-only client may perform a DNS lookup for a domain that only has an A record (IPv4). The DNS64 server then synthesizes a fake AAAA record. It embeds the IPv4 address within a well-known IPv6 prefix (typically 64:ff9b::/96). The client then sends IPv6 traffic to this synthesized address. The NAT64 gateway handles the translation.

This approach is particularly common on mobile networks. Carriers like T-Mobile in the US run IPv6-only networks for mobile devices. They use NAT64/DNS64 to maintain connectivity to the IPv4 internet. Understanding how DNS works is essential for troubleshooting issues in these environments.

IPv6 Adoption Today

IPv6 reached a historic milestone on March 28, 2026, when it crossed 50% of Google’s traffic for the first time. The single-day reading has not yet held as a daily average. Country-level adoption varies widely. France leads at 86% and India at 72%, while Italy and Spain remain under 20%.

On March 28, 2026, IPv6 crossed a historic threshold. Google began publishing IPv6 adoption statistics in 2008. For the first time since then, more than half of users accessed Google over IPv6. The reading was 50.1%, up from 46.3% a year earlier.

One nuance matters. The crossing was a single-day reading, not a sustained daily average. Google’s dashboard slipped back into the mid-40s in the weeks that followed. A near-miss at 49.56% in June 2025 showed the same pattern. The trend, though, points in only one direction.

Some regions reached majority status years ago. The Asia-Pacific (APNIC) service region passed 50% in 2025. The North American (ARIN) region crossed the line a couple of years before that. The global figure lags because adoption is so uneven country to country.

Leading Countries

At the other end of the spectrum: Italy sits around 17%, Spain at 10%, Egypt at 4%, China below 5%. These laggards have either heavy legacy IPv4 allocations (so less urgency to migrate) or limited ISP investment in dual-stack rollouts. Russia and Australia sit above 30%, climbing slowly.

The Enterprise Gap

Consumer ISPs and mobile carriers have led IPv6 deployment because they face the most direct pressure from address exhaustion. Enterprise networks have been slower to adopt. Many run behind NAT with RFC 1918 private addresses and feel no immediate pressure to change. Internal applications, security appliances, and monitoring tools may not fully support IPv6. This creates a chicken-and-egg problem where nothing gets upgraded because nothing else has been upgraded yet.

CDNs and Content Providers

Major CDNs and content providers, including Cloudflare, Akamai, Google, Facebook, and Netflix, all support IPv6. This matters because a significant portion of internet traffic flows through these networks. When the content side supports IPv6 and the access network supports IPv6, end-to-end IPv6 connections happen automatically. You can verify your own connectivity with our network tools.

What This Means for You

Three audiences face different implications. Everyday users see the transition as invisible because ISPs handle dual-stack deployment automatically. System administrators must maintain firewall rules, DNS records, monitoring, and address planning for both protocols. Developers must update socket programming, address storage, URL formatting, and testing to handle IPv6.

For Everyday Users

If you are a regular internet user, the IPv4-to-IPv6 transition is mostly invisible. Your ISP handles the dual-stack deployment. Your operating system prefers IPv6 when available. Websites serve content over whichever protocol your connection supports. You do not need to do anything manually.

That said, a few situations exist where awareness helps. If you are troubleshooting connectivity issues, knowing whether you are on IPv4 or IPv6 can narrow the problem. Setting up a home server, port forwarding, or a VPN requires accounting for both protocols. And if your ISP uses CGNAT, your “public” IPv4 address is shared with other customers. That explains why certain services (like hosting a game server) do not work without extra steps. Our guide on finding your public IP covers the CGNAT detection workflow.

For System Administrators

Network administrators face the most work during the transition. Key considerations include:

• Firewall rules. IPv6 requires its own set of firewall rules. Simply enabling IPv6 without configuring your firewall creates a security gap. Every rule you have for IPv4 needs an IPv6 equivalent. ICMPv6 must also be allowed for basic operations like neighbor discovery and path MTU discovery.
• DNS configuration. Add AAAA records alongside A records for all public-facing services. Ensure your recursive resolvers and authoritative servers support both protocols.
• Monitoring and logging. Update monitoring tools to track IPv6 traffic. Ensure that firewalls, IDS/IPS systems, and log analysis tools can handle IPv6 addresses. These are significantly longer than IPv4 addresses and may appear in multiple formats.
• Address planning. Plan your IPv6 addressing scheme before deployment. Unlike IPv4, where you carefully conserve addresses, IPv6 gives you a vast allocation. Use it hierarchically to simplify routing and access control. For block ownership investigation, our WHOIS lookup guide covers the RDAP-era workflow.

For Developers

Software developers must ensure their applications work correctly with both protocols:

• Socket programming. Use protocol-agnostic socket APIs. In most languages, this means using AF_INET6 sockets with dual-stack support. Or use address-family-independent functions like getaddrinfo() instead of hardcoding AF_INET.
• Address storage. IPv6 addresses require more storage space. Database columns sized for IPv4 will not fit IPv6 addresses. IPv4 uses 15 characters for dotted-decimal or 4 bytes for integer. IPv6 needs up to 39 characters or 16 bytes. Use INET6 or VARBINARY(16) column types where available.
• URL formatting. IPv6 addresses in URLs must be enclosed in square brackets: http://[2001:db8::1]:8080/path. This is defined in RFC 2732. It is a common source of parsing bugs when IPv6 support is added to existing code.
• Testing. Test your application on IPv6-only networks, not just dual-stack. Many bugs only surface when IPv4 is unavailable entirely.

Understanding where IP addressing fits in the broader networking model helps contextualize these changes. Our OSI model guide explains how IPv4 and IPv6 operate at Layer 3. It also covers how they interact with the layers above and below.

Related Tools & Resources

NetworkCheckr offers complementary tools for IPv4 and IPv6 workflows. The My IP Address tool shows your current public IP and indicates whether you are on IPv4 or IPv6. The Subnet Calculator handles CIDR math. Companion guides cover IP formats, subnetting, public vs private addresses, and how to find your IP.

• My IP Address — check your current public IP (IPv4 or IPv6) with geolocation and ISP detail.
• How to Find Your Public IP Address — five methods plus CGNAT detection.
• IP to Binary Converter — convert IPv4 addresses between decimal, binary, and hex.
• Subnet Calculator — CIDR math for both IPv4 and IPv6 networks.
• IPv4 to IPv6 Converter — map an IPv4 address into its IPv6 representation.
• CIDR to IP Range — expand any CIDR block into its first and last address.
• IP Address Formats Explained — companion explainer on notation rules.
• Public vs Private IP Addresses — the foundational distinction.
• Subnetting Beginner’s Guide — start here if subnet math is unfamiliar.
• VLSM and Supernetting — variable-length techniques that extended IPv4’s life.
• All NetworkCheckr Tools — the full set of free networking utilities.

Frequently Asked Questions

Seven questions cover the practical edge cases. Whether IPv6 is faster. Whether you need IPv6 right now. Whether IPv4 will stop working. How to check your IPv6 address. Why adoption is slow. Whether the two protocols can coexist. And what IPv4 addresses cost in 2026.