How do I calculate IP address utilization?

IP address utilization is the number of used, reserved, and otherwise unavailable host addresses divided by the usable host capacity of the subnet.

What is the difference between used and reserved IP addresses?

Used addresses are currently assigned or active. Reserved addresses are intentionally held for gateways, static devices, VIPs, DHCP reservations, future allocations, or operational policy.

Does this tracker support /31 and /32 IPv4 networks?

Yes. You can count /31 and /32 networks as assignable for point-to-point links and host routes, or use traditional LAN host counting where network and broadcast addresses are not assignable.

Can this replace IPAM?

No. This page is a planning calculator. Validate production records against DHCP, DNS, ARP, router, firewall, cloud, and IPAM sources.

Is this IP utilization tracker private?

Yes. Inputs are processed locally in your browser and are not sent to a backend.

IP Address Utilization Tracker

Track an IPv4 subnet from CIDR size, assigned hosts, reserved addresses, held or excluded addresses, growth buffer, and utilization threshold. Use it to check available host capacity before a VLAN expansion, DHCP scope change, cloud subnet allocation, or IPAM cleanup.

All calculations run locally in your browser. Validate production changes against IPAM, DHCP, DNS, routing, firewall, and cloud inventory records.

Inputs

IPv4 CIDR block Enter any IPv4 address with a prefix. The network address is normalized in results.

Used hosts Active leases, assigned addresses, or IPAM records currently in use.

Reserved hosts Gateways, VIPs, static devices, DHCP reservations, and planned holds.

Other unavailable hosts Quarantine, exclusions, conflicts, decommission holds, or addresses outside service.

Growth buffer (%) Additional hosts to reserve as a percentage of current used hosts.

Alert threshold (%) Warn when total consumed addresses exceed this share of usable hosts.

Addressing convention

Count /31 and /32 as assignable
Useful for point-to-point links and host routes. Traditional LAN host counting leaves /31 and /32 with no assignable host capacity.

Utilization presets

Results

Utilization status-

Available hosts-

Total utilization-

Recommended prefix-

Subnet range

Normalized network:-

Broadcast address:-

Usable host range:-

Total addresses:-

Usable host capacity:-

Utilization breakdown

Used hosts:-

Reserved hosts:-

Other unavailable hosts:-

Total consumed hosts:-

Used-only utilization:-

Addresses until threshold:-

Growth check

Growth buffer hosts:-

Available after buffer:-

Needed usable hosts at threshold:-

Advertisement

How to use this IP utilization tracker

Enter the CIDR block: use the subnet you are tracking, such as 10.20.30.0/24.
Count used addresses: include active leases, static assignments, cloud interfaces, load balancer addresses, and IPAM records that are truly assigned.
Add reserved and unavailable addresses: include gateways, VIPs, exclusions, quarantine holds, conflicts, and addresses intentionally kept out of service.
Set a threshold: use your operational alert ceiling, often 70% to 85% for shared or high-churn networks.
Review the result: compare available hosts, threshold headroom, growth buffer, and recommended prefix before changing address plans.

Formula and assumptions

Total addresses: 2^(32 - prefix)

Usable hosts: total addresses - 2 for traditional IPv4 subnets from /0 through /30.

Small subnet option: when enabled, /31 = 2 usable for point-to-point links and /32 = 1 usable for host routes.

Total consumed: used hosts + reserved hosts + other unavailable hosts

Available hosts: usable hosts - total consumed

Total utilization: total consumed / usable hosts

Recommended prefix: the smallest IPv4 prefix that can hold ceil((consumed + growth buffer) / alert threshold) usable hosts under the selected host-counting convention.

This page models IPv4 address counts only. It does not discover hosts, scan networks, validate ownership, or model IPv6 subnet planning.

Example utilization scenarios

Scenario	What to enter as used	What to enter as reserved or unavailable
Office VLAN	Active endpoints, printers, phones, and static host records	Gateway, HSRP/VRRP addresses, DHCP exclusions, future static ranges
Guest Wi-Fi subnet	Peak active leases or recent high-water DHCP count	Infrastructure addresses, excluded ranges, quarantine or captive portal holds
Cloud VPC subnet	Network interfaces, load balancers, NAT gateways, private endpoints	Provider-reserved addresses, planned expansion blocks, addresses kept for failover
Point-to-point /31	Both link endpoint addresses	Usually none, if your network policy allows /31 point-to-point addressing

Used, reserved, and available addresses mean different things

A subnet can look healthy if you only count active hosts, but become risky after static reservations, DHCP exclusions, provider-reserved addresses, and operational holds are included. This tracker treats those as consumed capacity because they cannot be handed to a new workload without a deliberate change.

The growth buffer is separate from current utilization. It estimates how many additional host addresses you want to leave room for, then checks whether the subnet can absorb that buffer while staying under your alert threshold.

Methodology

The calculator parses the IPv4 CIDR block, normalizes the network address, calculates total addresses, usable host capacity, broadcast address, and usable range, then subtracts used, reserved, and unavailable host counts. Utilization is calculated against usable hosts, not total addresses. The recommended prefix is the smallest prefix from /32 through /0 that can keep consumed plus growth-buffer demand under the selected utilization threshold.

Last reviewed: June 2026. Calculations are client-side arithmetic and do not inspect your network.

FAQs

Should reserved addresses count as utilized?

Yes for capacity planning. Even if a reserved address is not actively passing traffic, it is not freely available for normal assignment without changing the reservation or policy.

Why does the calculator normalize my CIDR block?

If you enter 10.20.30.17/24, that address belongs to the 10.20.30.0/24 network. The tracker shows the normalized network so results match the actual CIDR boundary.

What utilization threshold should I use?

Use the threshold your team alerts on. Stable infrastructure subnets can often run higher than guest, lab, or cloud subnets where bursts and automated provisioning can consume capacity quickly.

Does this support IPv6 utilization planning?

No. IPv6 address planning usually focuses on prefix delegation, route aggregation, security policy, and allocation structure rather than host exhaustion math.

Is this tracker private?

Yes. Inputs are processed locally and are not submitted to a backend.

Disclaimer

This is an infrastructure planning aid. Confirm address ownership, DHCP pools, DNS records, route tables, firewall policy, cloud provider reservations, and IPAM source-of-truth data before making production changes.