IP Address Capacity Planning: How to Forecast Subnet Growth and Avoid Running Out of Addresses

February 4, 2026

IP Address Capacity Planning: How to Forecast Subnet Growth and Avoid Running Out of Addresses

You find out your subnet is full at the worst possible moment. A new server won’t come online, a VoIP phone can’t register, or a critical device throws a duplicate IP error during a Monday morning rush. The scramble to carve out addresses or re-subnet under pressure is something no network admin wants to repeat.

IP address capacity planning is the practice of tracking how your subnets fill up over time and predicting when you’ll need more space — before that panicked Tuesday morning ever happens. And with connected devices growing 14% year-over-year to reach 21.1 billion globally in 2025 (according to IoT Analytics), even small and midsize networks are feeling the squeeze faster than expected.

This guide walks through a practical approach to subnet capacity planning — from baselining your current usage to setting up alerts that give you weeks of lead time instead of zero.

Why Subnets Run Out Faster Than You Think

Most network admins size their subnets based on what they need right now, plus some breathing room. A /24 gives you 254 usable addresses, which feels like plenty for a department of 40 people. But here’s what chips away at that space:

DHCP reservations for printers, access points, and IoT sensors

Static assignments for servers, switches, and management interfaces

BYOD devices — employees connecting phones, tablets, and personal laptops

Forgotten allocations for devices that were decommissioned but never reclaimed

Shadow IT devices that nobody documented

A Cisco study found that using the same subnet mask across all segments can waste over 50% of available address space. Meanwhile, over 40% of industrial network failures trace back to IP address allocation issues, according to networking industry research. The math catches up with you. And when it does, the cost isn’t trivial — network downtime now averages $8,600 per minute for midsize businesses, up from $5,600 just three years ago (The Network Installers).

Step 1: Baseline Your Current Subnet Utilization

You can’t plan for growth if you don’t know where you stand today. Start by documenting every subnet in your environment and answering three questions for each:

How many total addresses does this subnet have?

How many are currently assigned (static + DHCP leases)?

How many are truly in use right now?

That third question matters more than you’d think. DHCP lease tables often show addresses “in use” that are actually tied to devices that left the network weeks ago. A stale lease isn’t a used address — but it blocks a real one from being assigned.

What to Capture in Your Baseline

For each subnet, record:

Subnet CIDR and address range

Total usable addresses

Currently assigned addresses (static and dynamic)

Active addresses confirmed by network scan

Purpose (servers, workstations, IoT, guest Wi-Fi, etc.)

Growth trend over the past 6-12 months if data exists

If you’re tracking this in a spreadsheet, you already know how quickly it becomes unmanageable across 10 or 20 subnets. This is exactly where a dedicated IPAM tool earns its keep.

With Subnet24, every IP assignment updates in real time across all users, so your baseline is always current — not a snapshot from last week’s manual audit. The built-in network scanner can also find undocumented devices that your spreadsheet doesn’t know about.

Step 2: Identify Your Growth Drivers

Subnet growth doesn’t happen in a vacuum. Specific business and technology changes drive IP address consumption. Understanding your growth drivers helps you build realistic forecasts instead of guessing.

Common Drivers That Eat IP Addresses

Headcount growth. Every new employee typically means 2-3 IP addresses — a workstation, a VoIP phone, and often a mobile device on the corporate Wi-Fi.

IoT and smart building devices. Security cameras, badge readers, environmental sensors, smart lighting. These devices are multiplying fast. IoT devices are projected to exceed 25 billion globally by early 2026 (IoT Analytics), and your building is part of that count.

Cloud and hybrid infrastructure. VPN tunnels, cloud gateways, and containers all consume addresses from your on-prem subnets even when the workloads live elsewhere.

Mergers and acquisitions. Absorbing another company’s network almost always means absorbing their IP address needs — often with overlapping ranges that complicate everything.

BYOD policies. Once you allow personal devices on the network, address consumption per employee can double.

Talk to your facilities team, HR, and project managers. They often know about upcoming office expansions, new hires, or building automation projects months before IT gets looped in. That intel is gold for capacity planning.

Step 3: Set Utilization Thresholds That Actually Work

Waiting until a subnet is 100% full is like waiting until your car runs out of gas. You need warning thresholds that give you time to act.

Industry best practice follows a tiered alerting model:

These thresholds align with how major platforms handle it. AWS documentation recommends setting alerts at 80% subnet utilization. Infoblox, one of the largest enterprise IPAM vendors, defaults to a 95% critical trigger with an 85% reset value (Infoblox Documentation). Google Cloud’s Network Analyzer flags subnets as high-utilization when the allocation ratio exceeds 75% (Google Cloud).

For small and midsize networks, 75-80% is the sweet spot for a first-level warning. It gives you enough runway to plan without creating alert fatigue.

Step 4: Build a Simple Forecasting Model

You don’t need sophisticated predictive analytics software to forecast subnet growth. A straightforward approach works for most SMB environments.

The Basic Formula

Take your current utilization data and overlay your known growth drivers:

Projected utilization in 6 months = Current assigned addresses + (Monthly growth rate × 6)

Here’s a practical example:

You manage a /24 subnet (254 usable addresses) for your main office floor. Currently 185 addresses are assigned. Over the past 6 months, you’ve added an average of 5 new devices per month.

Current utilization: 185/254 = 72.8%

Projected in 3 months: 200/254 = 78.7% (hits warning threshold)

Projected in 6 months: 215/254 = 84.6% (hits critical threshold)

Projected full: roughly 14 months out

That tells you something concrete: you have about 3 months before you should start planning and about 6 months before things get uncomfortable.

Factor In the Spikes

Linear growth models work most of the time, but watch for step-function jumps:

A new office floor coming online (30-50 addresses overnight)

A building automation project (dozens of IoT sensors)

Seasonal workers or contractors during busy periods

A company acquisition bringing new devices onto your network

When you know about these, add them to your forecast as one-time bumps on top of the baseline growth rate.

Step 5: Plan Your Expansion Strategy Before You Need It

Once your forecast shows a subnet approaching its threshold, you have several options. Pick the one that fits your situation:

Option A: Supernet or Re-Subnet

If adjacent address space is available, you can expand a /24 to a /23, doubling your capacity from 254 to 510 usable addresses. This is the cleanest option but requires that the neighboring block isn’t already allocated.

Option B: Add a New Subnet and Route Between Them

When you can’t expand in place, create a new subnet for the same segment and set up routing between them. This is more work from a network configuration standpoint, but it avoids disrupting existing assignments.

Option C: Reclaim Wasted Space

Before expanding, audit for waste. You might find:

Static assignments for devices that were decommissioned months ago

DHCP ranges that are oversized relative to actual dynamic device counts

Subnets allocated to projects that never launched

Reclaiming even 15-20 addresses in a /24 can buy you months of runway.

Option D: Right-Size with VLSM

If some of your subnets are oversized while others are packed, Variable Length Subnet Masking lets you reallocate. That /24 assigned to a server closet with 8 devices could be a /28, freeing the remaining space for subnets that actually need it. VLSM can save over 50% of wasted address space compared to fixed-length subnetting.

Practical Example: A Growing MSP’s Capacity Plan

Consider a managed service provider handling 12 client networks. Each client has between 2 and 8 subnets, totaling roughly 50 subnets across the practice. Here’s what a practical capacity planning workflow looks like:

Monthly review: Pull utilization numbers for all 50 subnets. Flag any above 70%.

Quarterly deep dive: For flagged subnets, calculate growth rate and forecast when they’ll hit 80%. Cross-reference with client conversations about planned expansions or new projects.

Client communication: When a forecast shows a subnet hitting capacity within 6 months, proactively bring it to the client. “Your main office subnet is on track to run out of addresses by August. Here’s what I recommend.” That’s the kind of conversation that builds trust and prevents emergencies.

Annual planning: Roll subnet capacity forecasts into the annual technology review for each client. Use the data to justify infrastructure investments before they become urgent.

With Subnet24’s group nesting, an MSP can organize subnets by client, location, and purpose — keeping 50 subnets manageable without drowning in spreadsheet tabs. Real-time updates mean the utilization data is always current, whether you’re reviewing it from the office or a client site.

Common Capacity Planning Mistakes to Avoid

After working with network teams of all sizes, certain patterns keep showing up. Here are the ones that cause the most pain:

Assuming your subnet will last forever. A /24 feels massive until it doesn’t. Networks grow faster than anyone expects, especially with IoT adoption accelerating at 13-14% annually.

Ignoring DHCP lease bloat. If your DHCP lease time is set to 8 days and devices rotate frequently (think: conference rooms, guest networks), you can have hundreds of “used” addresses tied to devices that haven’t connected in a week.

Planning in isolation. The network team can’t forecast growth without input from facilities, HR, and project management. A 50-person hiring plan that nobody mentioned will blow your capacity forecast.

Treating all subnets equally. Your guest Wi-Fi subnet and your server subnet have completely different growth patterns. Apply different thresholds and review cadences based on how dynamic each segment is.

Not documenting the plan. A forecast that lives in one admin’s head is worthless when that person is on vacation during a subnet crisis. Document your thresholds, forecasts, and expansion plans somewhere the whole team can access.

Tools That Make Capacity Planning Easier

Manual capacity planning is doable for a handful of subnets, but it falls apart at scale. The right tooling automates the tedious parts and keeps your data accurate.

What to look for in an IPAM tool for capacity planning:

Real-time utilization tracking across all subnets

Historical data to identify growth trends

Alerting when subnets cross utilization thresholds

Network scanning to find undocumented devices

Multi-user access so the whole team works from the same data

Support for both IPv4 and IPv6 addressing

The IPAM market is growing rapidly — valued at approximately $1.25 billion in 2024 and projected to reach $3.45 billion by 2033 (Verified Market Reports) — because organizations recognize that managing IP addresses with spreadsheets simply doesn’t scale.

Subnet24 was built specifically for this problem. It tracks IPv4 and IPv6 subnets with real-time updates across your team, so utilization data is always current. The on-premises network scanner picks up devices that weren’t manually documented, giving you an accurate picture of what’s actually on each subnet. And because it’s cloud-hosted, you can check subnet utilization from anywhere — not just when you’re sitting at the office.

Getting started takes minutes, not months. Sign up for a free account — no credit card required — and you’ll immediately get access to manage up to four /24 subnets. That’s enough to baseline your most critical segments and start building your capacity plan today.

Your Capacity Planning Checklist

Here’s a quick-reference checklist to get started:

[ ] Inventory all subnets (CIDR, purpose, owner)

[ ] Baseline current utilization for each subnet (assigned vs. active)

[ ] Run a network scan to find undocumented devices

[ ] Identify top growth drivers (headcount, IoT, projects, BYOD)

[ ] Set utilization thresholds (75% warning, 85% critical)

[ ] Calculate growth rate per subnet using 6-12 months of historical data

[ ] Forecast when each subnet will hit its warning threshold

[ ] Document an expansion strategy for subnets approaching capacity

[ ] Schedule monthly utilization reviews

[ ] Share the plan with your team so it doesn’t live in one person’s head

Start Planning Before the Next IP Conflict Hits

IP address capacity planning isn’t glamorous work. But it’s the difference between proactively expanding a subnet during a maintenance window and desperately re-addressing devices while users flood your helpdesk.

The data is clear: network downtime costs are climbing, IoT is putting more devices on your subnets every quarter, and the organizations that plan ahead spend far less time firefighting. With over 40% of industrial network failures tied to IP address allocation issues, this isn’t something to figure out after the fact.

If you’re managing more than a few subnets and your current system is a spreadsheet (or worse, someone’s memory), give Subnet24 a try. The free tier lets you start tracking your most critical subnets immediately, and you’ll have a real capacity baseline within the hour.

What’s your most crowded subnet sitting at right now? If you don’t know the answer off the top of your head, that’s your sign to start planning.

Get Started with Subnet24 for Free