There are exactly 4,294,967,296 possible IPv4 addresses in the 32-bit IPv4 address space. This number comes from 232, because an IPv4 address contains 32 binary bits. However, 4.29 billion does not mean that 4.29 billion addresses are available for ordinary public Internet use.
Table of Contents
Large parts of the IPv4 address space are reserved for private networks, loopback communication, multicast, shared address space, documentation, benchmarking, protocol functions, and other special purposes. The remaining globally usable address space has also been heavily allocated over the history of the Internet.
That difference between total IPv4 addresses and publicly usable IPv4 addresses is important. It helps explain IPv4 exhaustion, the continued use of NAT and CGNAT, the growth of the IPv4 transfer and leasing markets, and why businesses still plan IPv4 resources carefully even as IPv6 adoption grows.
How many IPv4 addresses exist?
IPv4 has a theoretical total of 4,294,967,296 unique addresses. The number is fixed by the design of IPv4: each address is 32 bits long, so the protocol can represent 232 different binary combinations.
IPv4 address capacity at a glance
32-bit address space → 232 combinations → 4,294,967,296 total IPv4 addresses
This figure is often rounded to 4.3 billion IPv4 addresses.
The important distinction is that this is the size of the entire mathematical address space. It is not the number of addresses available to companies for websites, servers, VPNs, cloud services, or other public Internet services.
Why are there only about 4.3 billion IPv4 addresses?
IPv4 was designed around a 32-bit address field. A bit can contain one of two values: 0 or 1. With 32 positions and two possible values at each position, the total number of combinations is:
232 = 4,294,967,296
This was an enormous address space when the early Internet was being designed. The Internet later expanded far beyond its original environment, connecting personal computers, mobile devices, servers, cloud platforms, businesses, home networks, data centres, IoT systems, and billions of users.
The 32-bit structure itself did not expand with that growth. IPv4 still has exactly the same theoretical address capacity today.
How does IPv4 addressing create 4.29 billion combinations?
An IPv4 address is normally written as four decimal numbers separated by periods, for example:
203.0.113.25Each of the four sections is an octet containing 8 bits.
Because each octet can represent values from 0 to 255, an IPv4 address contains:
- 8 bits in the first octet
- 8 bits in the second octet
- 8 bits in the third octet
- 8 bits in the fourth octet
That gives a total of 32 bits.
Another way to express the calculation is:
256 × 256 × 256 × 256 = 4,294,967,296
The familiar dotted-decimal format makes IPv4 easier for people to read, but underneath it is still a 32-bit binary identifier.
Why can’t all 4.3 billion IPv4 addresses be used publicly?
Not every mathematically possible IPv4 address is intended to be globally routed on the public Internet. Internet standards reserve multiple address ranges for specific technical purposes.
The IANA IPv4 Special-Purpose Address Registry records blocks used for purposes including private networks, loopback, shared addressing, documentation, benchmarking, protocol functions, and reserved space.
This means the often-quoted figure of 4.3 billion should not be interpreted as 4.3 billion interchangeable public IPv4 addresses.
For example:
- 10.0.0.0/8 is private-use space.
- 127.0.0.0/8 is associated with loopback functions.
- 100.64.0.0/10 is shared address space commonly associated with service-provider environments.
- 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 are reserved for documentation and examples.
- 198.18.0.0/15 is used for benchmarking.
- 224.0.0.0/4 belongs to the IPv4 multicast address space.
- 240.0.0.0/4 remains reserved by protocol.
Some special-purpose blocks contain subranges with different properties, so calculating “usable public IPv4” is more complicated than simply subtracting a few large blocks from 4,294,967,296.
Where does the reserved IPv4 address space go?
IPv4 address space serves several purposes besides normal globally reachable unicast communication.
| Address Category | Example | Typical Purpose | Globally Routable? |
|---|---|---|---|
| Private-use space | 10.0.0.0/8 | Internal networks | No |
| Shared address space | 100.64.0.0/10 | Service-provider shared addressing / CGNAT environments | No |
| Loopback | 127.0.0.0/8 | Communication with the local host | No |
| Documentation | 192.0.2.0/24 | Examples and technical documentation | No |
| Benchmarking | 198.18.0.0/15 | Network testing and benchmarking | No |
| Multicast | 224.0.0.0/4 | One-to-many packet delivery | Not ordinary public unicast space |
| Reserved | 240.0.0.0/4 | Reserved by the IPv4 protocol | No |
IANA maintains separate registries for IPv4 address space, multicast addresses, special-purpose addresses, recovered address space, and related number resources.
This is why there is no meaningful business scenario where all 4.29 billion combinations could simply be placed into one global pool and assigned to public servers.
How many IPv4 addresses are reserved for private networks?
RFC 1918 defines three IPv4 ranges for private networks:
- 10.0.0.0/8 — 16,777,216 addresses
- 172.16.0.0/12 — 1,048,576 addresses
- 192.168.0.0/16 — 65,536 addresses
Together, these ranges contain 17,891,328 private IPv4 addresses.
The important point is that private addresses are reusable. The same 192.168.1.10 address can exist in millions of unrelated home or business networks because it is not supposed to be globally routed across the public Internet.
RFC 1918 formally defines these private-use blocks, while IANA explains that private-use addresses may be used independently by many networks without central registration.
Private addressing has significantly extended the practical life of IPv4 because organizations can operate thousands of internal devices while using a much smaller number of public addresses to reach the Internet.
How many public IPv4 addresses are actually available?
There is no single simple number that represents all currently available public IPv4 addresses. The theoretical IPv4 space is 4.29 billion addresses, but public availability depends on address reservations, historical allocation, registry status, transfers, returns, existing assignments, and operational use.
This distinction is important:
- Total IPv4 address space describes what the 32-bit protocol can represent.
- Globally routable IPv4 space excludes address ranges that are not intended for ordinary global unicast use.
- Unallocated IPv4 space refers to addresses still available for new allocation under a particular registry process.
- Market-available IPv4 space refers to existing resources that holders may be willing and eligible to transfer, sell, or lease.
These categories should not be treated as the same thing.
IANA states that its central supply of unallocated IPv4 address space has been exhausted. Regional availability and policies vary, and businesses seeking additional public IPv4 capacity increasingly rely on existing allocations, provider assignments, transfers, purchases, or leasing rather than expecting a new large block from a free global pool.
Why did IPv4 addresses run out?
IPv4 exhaustion happened because demand for globally unique Internet addresses eventually became larger than the limited supply created by a 32-bit protocol.
The Internet expanded from a comparatively small research and academic network into infrastructure supporting billions of people and enormous numbers of connected systems.
Demand came from:
- Internet Service Providers
- Mobile networks
- Enterprise networks
- Web hosting
- Cloud computing
- Data centres
- Broadband connections
- SaaS applications
- VPN infrastructure
- Connected devices
The central IANA IPv4 pool eventually reached exhaustion. IANA’s Number Resource Allocation Data now explicitly notes that IPv4 is not shown in its utilization chart because IANA’s supply has been exhausted.
For a deeper explanation of the shortage and its impact, see What Is IPv4 Address Exhaustion?
How is the Internet still growing after IPv4 exhaustion?
IPv4 exhaustion does not mean the Internet stopped accepting new users or services. Instead, network operators use several techniques and resource models to keep infrastructure growing.
1. Private addressing and NAT
Network Address Translation allows many devices using private IP addresses to communicate through a smaller number of public IPv4 addresses.
2. Carrier-Grade NAT
Service providers can place large groups of customers behind shared public IPv4 resources using Carrier-Grade NAT, although this introduces operational trade-offs.
3. IPv4 transfers
Existing IPv4 resources can move between eligible organizations under applicable registry transfer policies rather than depending solely on newly created supply.
4. IPv4 leasing
Organizations that need public IPv4 resources for infrastructure may lease address space rather than acquiring it permanently. Leasing can provide additional capacity for hosting, VPN, cloud, SaaS, and data centre deployments where flexible access is useful.
5. IPv6 deployment
IPv6 provides a vastly larger address space and is the long-term protocol designed to remove the address-capacity limitation of IPv4.
In practice, many networks continue operating IPv4 and IPv6 together because users, applications, networks, and devices have not all migrated to IPv6 at the same time.
Who manages IPv4 address allocation?
Internet number resources are coordinated through a hierarchy rather than being controlled by one ISP or cloud provider.
At the global level, the Internet Assigned Numbers Authority (IANA) maintains the top-level IPv4 address space registry and coordinates allocations of number resources to the Regional Internet Registries.
The five Regional Internet Registries are:
- AFRINIC
- APNIC
- ARIN
- LACNIC
- RIPE NCC
These registries maintain resource records and regional allocation or transfer processes. ISPs, network operators, enterprises, hosting companies, and other organizations then use address resources within real networks.
It is important to distinguish registry coordination from actual network routing and operational use. An address record identifies how the resource is registered, while BGP and network configuration determine how traffic is actually routed.
IPv4 vs IPv6 address capacity
IPv6 was designed with a much larger address field than IPv4.
| Protocol | Address Length | Theoretical Address Space |
|---|---|---|
| IPv4 | 32 bits | 232 = 4,294,967,296 |
| IPv6 | 128 bits | 2128 ≈ 3.4 × 1038 |
The difference is enormous. Moving from 32-bit addressing to 128-bit addressing was intended to provide enough address capacity for long-term Internet growth.
However, IPv6 does not instantly make IPv4 irrelevant. Many customer networks, applications, access providers, security policies, hosting environments, and business systems still depend on IPv4 compatibility.
This is why modern infrastructure commonly needs a transition strategy rather than a simple “IPv4 off, IPv6 on” decision.
For a deeper comparison, see IPv4 vs IPv6.
Why businesses still need IPv4 addresses
IPv4 remains relevant because Internet infrastructure must reach the users and networks that exist today, not only those that support the newest protocol.
Businesses continue using public IPv4 resources for:
- Web hosting
- Dedicated servers
- Cloud workloads
- VPN gateways
- SaaS platforms
- Email systems
- APIs
- DNS services
- Data centre infrastructure
- Network appliances
- Enterprise applications
- Customer-facing services
A business may therefore support IPv6 while still maintaining IPv4 for compatibility and operational continuity.
The practical question is no longer simply “Are there any IPv4 addresses left?” It is often:
How should the organization source, route, protect, and manage the IPv4 resources its services still require?
What businesses should consider when planning IPv4 resources
Because public IPv4 resources are finite, businesses should plan requirements based on actual infrastructure needs rather than only address quantity.
Important considerations include:
Required block size
Determine how many public addresses are actually needed. A hosting environment may require a larger block than a single application endpoint.
Routing
Understand whether the provider will announce the addresses or whether the organization needs independent BGP routing.
IP reputation
Addresses used for email, hosting, APIs, or customer-facing platforms may be affected by historical reputation and abuse records.
Reverse DNS
Some applications, especially email infrastructure, depend on proper reverse DNS configuration.
Geolocation
IP geolocation may affect fraud detection, content access, analytics, compliance workflows, or customer experience.
Deployment duration
A temporary infrastructure project and a permanent network deployment may justify different sourcing strategies.
Continuity
Production infrastructure needs renewal clarity, routing stability, provider support, and an appropriate migration or exit plan.
Organizations needing flexible public address capacity can consider IPv4 Leasing, while businesses seeking longer-term control may evaluate options to Buy IPv4 Addresses.
Practical Note from i.lease
The important number is not only 4,294,967,296. For businesses, the more practical question is how much usable public IPv4 capacity is available for a specific network deployment.
A public IPv4 address may support a website, cloud workload, VPN gateway, SaaS application, email server, hosting customer, or other reachable service. That makes address planning an operational infrastructure decision rather than a simple exercise in counting addresses.
i.lease supports organizations that need additional IPv4 capacity through IPv4 Leasing or longer-term acquisition through Buy IPv4 Addresses, depending on deployment duration, routing needs, and infrastructure strategy.
Final thoughts
IPv4 contains exactly 4,294,967,296 theoretical addresses, but the number of addresses available for normal public Internet use is smaller. Private networks, multicast, loopback, documentation, benchmarking, shared addressing, reserved blocks, and other special-purpose functions all use portions of the 32-bit address space.
The theoretical capacity of IPv4 has never changed. What changed was the Internet around it. Billions of users, cloud platforms, mobile networks, data centres, hosting services, and enterprise applications created demand far beyond what early IPv4 deployment anticipated.
IPv6 provides the long-term answer to address-space scale, but IPv4 remains part of real production infrastructure. Businesses therefore need to manage existing IPv4 resources efficiently while planning for increasing IPv6 adoption.
Understanding why IPv4 is limited helps explain why public IPv4 resources remain important for network expansion, customer access, compatibility, routing, and business continuity.
Also Read
Frequently Asked Questions
How many IPv4 addresses in the world?
There are exactly 4,294,967,296 theoretical IPv4 addresses because IPv4 uses a 32-bit address space, giving 232 possible combinations.
Why are there only 4.3 billion IPv4 addresses?
IPv4 addresses contain 32 bits. Since every bit can be either 0 or 1, a 32-bit address space provides 232, or 4,294,967,296, possible combinations.
Are all 4.3 billion IPv4 addresses publicly usable?
No. Multiple IPv4 ranges are reserved for private networks, loopback, shared addressing, documentation, multicast, benchmarking, protocol functions, and other special purposes.
How many IPv4 addresses are reserved for private use?
RFC 1918 reserves 17,891,328 IPv4 addresses across 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These ranges can be reused independently inside private networks.
Have IPv4 addresses run out?
IANA’s central supply of unallocated IPv4 address space is exhausted. Availability at the regional and market level depends on existing allocations, registry processes, transfers, returns, provider assignments, purchases, and leasing.
Can businesses still get IPv4 addresses?
Yes. Businesses can still access IPv4 resources through provider assignments, applicable transfer and acquisition processes, or IPv4 leasing even though the original free central pool has been exhausted.
Why can’t private IPv4 addresses be used on the public Internet?
Private IPv4 ranges are deliberately reusable across independent networks and are not globally unique. They are therefore not intended to be routed across the public Internet.
How does NAT help with IPv4 exhaustion?
NAT allows multiple devices using private IPv4 addresses to share a smaller number of public IPv4 addresses, reducing the number of globally unique addresses required by a network.
Who manages IPv4 address space?
How many addresses does IPv6 have compared with IPv4?
IPv4 has 232, or about 4.3 billion, possible addresses. IPv6 uses 128 bits and provides 2128, or approximately 3.4 × 1038, possible addresses.
