IPv4 Availability Depends on More Than Address Count

IPv4 Availability Planning is no longer only about finding unused address space. As IPv4 resources become increasingly scarce, the way networks organize, aggregate, and announce prefixes has become just as important as the number of available addresses.

Many organizations focus on acquiring IPv4 resources while overlooking fragmentation. However, fragmented address space affects routing, operational flexibility, scalability, and long-term network design. Consequently, network architects, ISPs, hosting providers, and enterprises increasingly consider prefix organization when planning IPv4 deployments.

What Is IPv4 Fragmentation?

IPv4 fragmentation describes a situation where address space becomes divided into many smaller prefixes instead of remaining as larger contiguous blocks.

Fragmentation usually occurs over time because of:

• Customer growth
• Company acquisitions
• Historical allocations
• IPv4 transfers
• Multi-region deployments
• Independent customer assignments

For example, an organization that originally owned a contiguous /20 may eventually manage sixteen independent /24 networks spread across different customers or locations.

Although the total number of IP addresses remains unchanged, operational complexity increases significantly.

Why IPv4 Still Matters

Despite the continuous growth of IPv6, IPv4 remains essential for many production environments.

Many Internet services continue to depend on IPv4 because:

• Legacy applications still require IPv4 connectivity.
• Enterprise environments often operate dual-stack networks.
• Customer equipment may not fully support IPv6.
• Public cloud services continue to expose IPv4 endpoints.
• Many business applications expect globally reachable IPv4 addresses.

As a result, IPv4 availability remains an important planning consideration for ISPs, cloud providers, hosting companies, and enterprise networks.

Why Subnet Size Matters

Subnet size affects far more than address allocation.

It directly influences:

• Route aggregation
• BGP announcements
• Routing policy management
• Future expansion
• Customer assignment flexibility

Choosing the appropriate subnet today can simplify network operations for many years.

Comparison of fragmented IPv4 address space and contiguous IPv4 allocation, illustrating how subnet organization influences BGP routing, route aggregation, and long-term network scalability.
AI-generated illustration created using Google Gemini.

IPv4 Fragmentation and BGP Routing

BGP performs best when networks advertise aggregated prefixes whenever possible.

Consider two scenarios.

Scenario 1: One Aggregated Prefix

An ISP advertises:

• 203.0.113.0/20

The global routing table contains one announcement.

Policy management remains straightforward.

Route objects remain simple.

ROA management is also simplified.

Scenario 2: Fragmented Prefixes

The same address space becomes:

• 203.0.113.0/24
• 203.0.114.0/24
• 203.0.115.0/24
• …
• sixteen individual /24 prefixes

Now the operator must manage:

• Multiple BGP announcements
• Multiple route objects
• Multiple ROAs
• Additional routing policies

Consequently, operational overhead increases even though the number of available addresses stays the same.

/23 vs Two /24s

Network engineers frequently face this decision.

One /23

Advantages

• Better route aggregation
• Fewer BGP announcements
• Simpler routing policies
• Lower operational overhead
• Easier future expansion

Considerations

• Less flexible if customers require completely independent routing policies

Two Independent /24s

Advantages

• Greater allocation flexibility
• Independent customer assignment
• Separate routing policies
• Easier geographic separation

Considerations

• Two route objects
• Two ROAs
• Two BGP announcements
• Higher probability of long-term fragmentation

Neither approach is universally correct. The appropriate choice depends on operational objectives.

/22 vs Multiple /24s

The same principles apply at larger scale.

One /22 typically provides:

• Cleaner aggregation
• Simpler routing
• Reduced operational complexity
• Better scalability

Four separate /24 prefixes provide:

• Greater deployment flexibility
• Independent customer assignments
• Independent announcements

However, they also increase:

• Routing complexity
• Database management
• ROA administration
• Filtering policies

As networks continue to grow, these operational differences become increasingly important.

IPv4 Leasing and Fragmentation

IPv4 leasing also influences fragmentation.

Many organizations assume leasing simply provides additional addresses.

In practice, the structure of leased address space matters just as much.

Receiving a contiguous /22 often simplifies operations compared with managing four unrelated /24 allocations.

Benefits include:

• Better BGP aggregation
• Fewer route objects
• Fewer ROAs
• Simpler routing filters
• Easier network documentation
• More efficient address planning

Consequently, contiguous allocations often improve long-term network scalability.

IPv4 Fragmentation and Long-Term Network Planning

Fragmentation rarely becomes a problem immediately.

Instead, its effects accumulate over time.

Network growth often requires:

• Additional customers
• New services
• More data centers
• Additional upstream providers
• Regional expansion

If address planning ignored aggregation from the beginning, each expansion introduces additional routing complexity.

Conversely, well-organized address space allows operators to expand while maintaining efficient routing.

Best Practices for Subnet Aggregation

Network operators can reduce fragmentation by following several practical guidelines.

• Preserve contiguous address blocks whenever possible.
• Aggregate prefixes before announcing them.
• Minimize unnecessary deaggregation.
• Design allocations with future growth in mind.
• Maintain consistent routing policies.
• Document address assignments carefully.
• Review aggregation opportunities periodically.

These practices improve both operational efficiency and network scalability.

Explained for Network Engineers

From an engineering perspective, IPv4 fragmentation is primarily an operational challenge rather than an addressing problem.

Fragmented address space increases the number of:

• Route objects
• ROAs
• Prefix announcements
• Routing policies
• Operational changes

Meanwhile, aggregated address space reduces administrative effort and simplifies BGP operations.

This difference becomes increasingly significant in environments managing hundreds or thousands of prefixes.

Therefore, effective IPv4 Availability Planning should balance customer flexibility with long-term routing efficiency.

Summary

IPv4 Availability Planning extends beyond acquiring additional address space. As IPv4 resources become more limited, fragmentation, subnet aggregation, and routing strategy increasingly influence operational efficiency.

Comparisons such as /23 versus two /24s or /22 versus multiple /24s demonstrate that subnet organization affects BGP routing, scalability, and administrative complexity long after addresses have been assigned.

For network engineers and infrastructure operators, effective IPv4 planning is not simply about maximizing address utilization. It is about designing address space that supports efficient routing, future growth, and sustainable network operations.

Continue the Discussion

Every network grows differently, and there is no single subnet strategy that fits every environment. If you are planning a new deployment, reorganizing existing IPv4 resources, or evaluating routing scalability, discussing different aggregation approaches with experienced network engineers can help identify the most suitable long-term design.