IP Fragmentation: The Invisible Problem Costing Operators Millions

IP fragmentation rarely appears overnight. Instead, it builds slowly through years of incremental changes, expanding networks, new services, and evolving infrastructure.

Over time, IP space becomes scattered across teams, regions, and systems. What once looked like a clean addressing plan gradually turns into a complex patchwork of subnets, static assignments, and partially documented allocations.

To explore how fragmentation develops and what operators can do about it, IPXO hosted a webinar with Matthew Wilder, Senior Engineer at TELUS and Advisory Council member at ARIN, and Wilhelm Boeddinghaus, CEO at Route 128. The discussion was moderated by IPXO’s Paulius Judickas.

The session explored how fragmentation happens, why it often remains invisible for years, and what practical steps organizations can take to restore visibility and control over their IPv4 address space.

What IPv4 Fragmentation Actually Means

In networking discussions, “fragmentation” can refer to multiple things. In this context, the speakers emphasized that they were not discussing packet fragmentation, but fragmentation of the IP address space itself.

This occurs when address blocks become scattered across systems, teams, or services without a clear structure.

Over time, organizations lose visibility into how their address space is actually being used.

In many cases, network engineers eventually have to investigate historical assignments and ask colleagues across departments where specific addresses are being used and why.

What initially appears to be a minor operational inconvenience can quickly turn into a complex and time-consuming audit.

Why Fragmentation Happens

One of the interesting insights from the discussion is that fragmentation often arises from two opposite planning failures.

Some organizations allocate addresses with almost no planning at all. Others create extremely detailed address plans designed to last decades.

Both approaches can lead to problems.

Without planning, IP addresses are simply assigned wherever they are needed, leading to scattered allocations.

With overly rigid planning, organizations eventually encounter changes in business strategy, infrastructure, or technology that invalidate the original plan. Teams then begin working around it.

Over time, the structured plan is gradually bypassed, resulting in fragmented usage.

Technological change also plays a role. Over the past two decades alone, networks have evolved through major shifts such as:

• MPLS deployments
• large-scale cloud infrastructure
• segment routing
• distributed data centres
• the rapid rise of AI infrastructure

Each new technology layer introduces new operational requirements, which often leads to adjustments in address allocation.

Why Fragmentation Often Goes Unnoticed

Another key question raised during the webinar was why fragmentation often remains invisible for so long.

The answer frequently comes down to IP address management practices.

Organizations without centralized IPAM systems often track addresses through informal processes, spreadsheets, or fragmented documentation.

Without a reliable inventory, engineers cannot easily see which addresses are in use, which ones are unused, and which networks are actually being routed.

As a result, fragmentation gradually accumulates without triggering immediate operational failures.

When Fragmentation Starts Affecting the Network

Eventually, fragmentation begins to show up in operational metrics.

One of the first indicators can be growth in routing tables, particularly in enterprise or government environments where routing hardware may have stricter limits.

In ISP environments, routing hardware typically handles much larger routing tables, so fragmentation may not cause immediate performance problems. Instead, it reduces operational flexibility.

When address space is scattered across many small prefixes, operators lose the ability to easily allocate contiguous blocks for new services or infrastructure expansion.

This loss of flexibility can slow down network deployments and complicate growth strategies.

Why Static IP Assignments Make Defragmentation Difficult

One of the most practical insights from the discussion focused on static IP assignments.

Dynamic allocations can usually be reassigned with minimal disruption, especially in ISP environments where addresses are distributed through DHCP.

Static assignments, however, often create long-term dependencies.

In some cases, IP addresses are embedded directly into application configurations — or even source code.

Industrial systems can present even more difficult cases. Certain devices may have addresses permanently embedded in firmware or deployed in remote locations where physical access is difficult.

These situations make it significantly harder to reclaim or reorganize address space.

Making the Case for Defragmentation

One challenge network engineers frequently face is explaining the importance of fragmentation to leadership.

Because fragmentation rarely causes immediate outages, it can be difficult to justify allocating time and resources to fix it.

However, the speakers pointed out several scenarios where fragmentation becomes visible at the business level:

• cybersecurity assessments
• mergers and acquisitions
• infrastructure expansion projects
• routing capacity limits
• inefficient IP utilization

For organizations managing public IPv4 space, fragmentation may also represent lost monetization opportunities, since unused or stranded addresses could potentially be leased or transferred.

The First Steps Toward Defragmentation

Defragmentation is rarely a purely technical exercise.

It typically requires coordination across multiple teams, including infrastructure, database, application, and security teams.

Network engineers must often collaborate with other departments to modify configurations, update services, or schedule maintenance windows.

Before making any changes, teams should first build a clear inventory of the existing environment.

This means understanding:

• which addresses exist in IPAM records
• which addresses are actually routed
• which systems depend on them
• which ranges can potentially be reclaimed

Without this visibility, defragmentation becomes extremely risky.

What IPv6 Changes And What It Doesn’t

IPv6 introduces a dramatically larger address space, which makes fragmentation less likely to cause immediate scarcity.

However, the speakers cautioned that this does not automatically eliminate fragmentation.

Without disciplined address management, IPv6 networks can still accumulate technical debt over time.

However, IPv6 deployments also provide an opportunity to rebuild addressing architecture more cleanly, especially when organizations design new network segments or data centre environments.

The Long-Term Lesson: Prevent Technical Debt Early

The discussion closed with a reminder that fragmentation is often a form of technical debt.

Small operational shortcuts accumulate over time, eventually creating larger problems that require significant effort to fix.

By implementing proper IP address management, maintaining clear inventory systems, and coordinating allocation policies across teams, organizations can avoid much of the fragmentation that later requires costly cleanup projects.

For network operators, enterprises, and governments alike, maintaining visibility over IP address space is not just a matter of operational hygiene – it is a prerequisite for security, scalability, and long-term network resilience.

FAQ