IPv4 Procurement Roadmap: Planning Address Needs for the Next 12 Months

Planning IPv4 resources one year ahead helps a company estimate required address space, sourcing time, and whether leasing or purchasing is more appropriate. It also reduces shortage risk before launches, migrations, or regional expansion.

An IPv4 procurement roadmap is a 12-month plan that connects address demand with procurement timing, budget, and technical preparation. Its purpose is to show how much IPv4 capacity the organization will need, when new blocks should be acquired, and when those resources must be ready for production use.

How should an address needs forecast be calculated for the next 12 months?

The forecast should begin with actual utilization, not the nominal size of the current pool. IPAM data should be compared with live assignments, reserves, planned decommissioning, and approved projects so stale records do not distort demand.

The calculation should include:

current utilization of each prefix and subnet;
expected growth in customers, services, and infrastructure;
new data centers, cloud regions, CDN nodes, VPN gateways, and NAT pools;
fixed IP requirements for APIs, allowlists, and partner connections;
reserve capacity for migration, failover, or incident isolation;
addresses expected to return after systems are retired.

Demand should also be separated by region or product when growth patterns differ. A company-wide total can hide a local shortage while capacity remains elsewhere.

How does forecast demand become a real IPv4 capacity requirement?

Forecast demand does not translate directly into the same number of addresses to procure. Subnet boundaries, segmentation, routing policy, and reserve can increase the space required, while separate projects may need independent subnets even if their hosts would fit inside one aggregate.

The roadmap should model deployable capacity and identify blocks for confirmed projects, expected growth, and reserve. If permanent capacity is required, the company can buy IPv4 addresses early enough to include transfer and preparation.

When should a company lease IPv4 space instead of buying it?

Leasing usually fits temporary, seasonal, pilot, or uncertain demand, while purchase suits long-term infrastructure where changing the range later would create reconfiguration. The decision should compare duration, cost, migration effort, and control.

The sourcing review should compare:

expected duration of use and forecast utilization;
total lease cost versus purchase and transfer cost;
future re-IP or migration effort;
dependence on fixed IPs in DNS, firewall rules, and allowlists;
reputation history of the range;
need for direct control of RIR and RPKI records.

A mixed model can keep owned blocks for stable workloads while companies rent IPv4 addresses for temporary growth. This reduces the risk of buying space that later remains unused.

Why must technical preparation time be included in the procurement roadmap?

Commercial access does not mean that a block is production-ready. The team may still need to verify reputation, update ROA or IRR data, configure rDNS, confirm geolocation, and coordinate upstream filtering before use.

Purchased resources may also require an RIR transfer and supporting documentation. The roadmap should distinguish the procurement start date from the production-ready date, especially for fixed launch windows, because a late acquisition can still delay deployment.

How should different demand scenarios be represented in annual planning?

A single forecast is too rigid for a full year because demand can change when a major customer is added, a project is delayed, or a new region grows faster than expected. Scenario planning should separate committed demand from likely growth and from additional capacity needed only if expansion accelerates.

A useful roadmap can maintain three planning levels:

committed demand from approved projects;
expected demand based on normal growth;
contingency capacity for accelerated expansion or unplanned requirements.

This allows procurement to be staged instead of committing capital or lease costs before demand is certain.

How should actual IPv4 consumption be monitored during the year?

The roadmap should be revised when real consumption diverges from the forecast. Fast-growing pools can be reviewed monthly, while the wider forecast can be compared with actual utilization each quarter.

The team should track available capacity, operational reserve, lease expiration dates, and the threshold for starting the next sourcing cycle. Procurement should begin while enough space remains to cover approval, sourcing, transfer, and technical preparation without forcing an emergency purchase.

Why should regional demand be tracked separately?

Regions can have different growth rates, routing requirements, geolocation needs, RIR conditions, and resource availability, so a surplus in one location may not solve a shortage in another. Separate regional forecasts also help determine whether future demand should be covered through one larger block, several ranges, or a mix of owned and leased resources.

Which planning decisions still require management attention?

Should emergency reserve be counted as available capacity?

No. Capacity reserved for failover, migration, or incident isolation already has an operational purpose.

What should happen if actual demand is lower than forecast?

Future procurement should be reduced or delayed. Owned ranges that remain unused can also be reviewed for leasing or sale.

When should procurement of the next block begin?

Before the remaining free pool falls below the amount needed to cover the full sourcing and technical preparation cycle.

Does every project need its own IPv4 block?

No. Projects can share address space when routing, segmentation, security, and ownership requirements allow it.

Where can additional IPv4 capacity be sourced when the roadmap shows a gap?

When the annual IPv4 roadmap shows that existing resources will not cover planned demand, InterLIR can be used to lease or purchase additional IPv4 blocks. Owners whose forecasts reveal consistently unused address space can also prepare those resources for leasing or sale through the platform.