Skip to content
AdminKit

IPv4 address exhaustion

What is IPv4 address exhaustion?

IPv4 address exhaustion is the depletion of IPv4's roughly 4.3 billion addresses, reached when IANA allocated its last free blocks to the regional registries in 2011. ISPs responded with Carrier-Grade NAT, sharing addresses from the RFC 6598 reserved block instead of moving networks to IPv6-only. AdminKit's CGNAT guide covers the shared-blacklist tradeoff that mitigation causes.

By AdminKit team, Netbase JSC · Updated

IPv4 address exhaustion is the depletion of the roughly 4.3 billion addresses IPv4’s 32-bit address space provides, a limit the internet’s growth reached faster than IPv6 — which uses a 128-bit address space large enough that exhaustion isn’t a practical concern — was deployed to replace it, a rollout Google’s own IPv6 adoption statistics have tracked for years and still show as partial. IANA’s IPv4 address space registry shows its last remaining IPv4 address blocks allocated to the regional internet registries around 2011, and several registries have since run out of their own free pools too — the RIPE NCC, which serves Europe, the Middle East and parts of Central Asia, exhausted its remaining IPv4 pool in November 2019. Rather than switching networks to IPv6-only, most ISPs responded with mitigations that stretch the existing IPv4 supply: Carrier-Grade NAT (CGNAT) shares one public address across many customers, using the shared address block RFC 6598 reserves for exactly that purpose. AdminKit’s CGNAT guide covers why that specific mitigation, adopted because of this exhaustion, causes shared blacklist status and broken port forwarding for affected customers. Every freshly allocated block also needs filter lists updated promptly, since treating that now-legitimate space as an unrouted bogon address would wrongly block its traffic.

AdminKit groups iPv4 address exhaustion under its IP & network cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

When did IANA run out of free IPv4 address blocks?

Around 2011, when IANA's registry shows its last remaining blocks allocated to the regional internet registries; several registries have since exhausted their own free pools too.

How did ISPs respond to IPv4 exhaustion instead of moving to IPv6-only?

Most adopted Carrier-Grade NAT (CGNAT), sharing one public IPv4 address across many customers using the address block RFC 6598 reserves for exactly that purpose.

Does IPv6 solve address exhaustion?

Yes -- its 128-bit address space is large enough that exhaustion isn't a practical concern, which is why it was deployed to eventually replace IPv4.