IPv4 Free Pool: Why ARIN's 2015 Shift Changed Everything

ARIN's IPv4 Free Pool officially depleted on 24 September 2015. The registry still processes limited requests, but the rules have changed fundamentally. You cannot simply ask for space anymore. Modern acquisition relies entirely on navigating reserved micro-allocations or secondary market transfers. Traditional free pool distribution is dead. To qualify for any remaining direct resources, organizations must now prove critical infrastructure status or immediate IPv6 deployment needs.

Efficient utilization is no longer a best practice; it is the gatekeeper. Under NRPM 4.4, eligibility for micro-allocations granted to core DNS providers and exchange points hinges on this metric. The registry maintains a dedicated /10 block specifically to enable IPv6 deployment through NAT-PT translators and dual-stack configurations, but the documentation bar is high. If standard paths are closed, your only options are the Waiting List or private transfers.

The numbers tell the real story. Current data from ARIN indicates the remaining pool sits at a negligible 0.0001 /8s as of 29 June 2026. This is near-total exhaustion. This scarcity forces network operators to justify every single address request with immediate technical necessity rather than projected growth. Direct allocations are effectively historical artifacts. The path forward requires precise adherence to policy nuances that prioritize existing internet stability over expansion.

The Role of Efficient Utilization in Modern IP Resource Management

Defining IPv4 Micro-allocation and NRPM 4.10 Constraints

The landscape shifted on 24 September 2015. ARIN exhausted its IPv4 Free Pool, pushing standard requests to the Waiting List or transfer markets. Policy NRPM 4.4 now directs remaining micro-allocations exclusively toward critical Internet infrastructure providers. Public exchange points and core DNS operators receive these reserved blocks to maintain global routing stability. Commercial expansion no longer qualifies for such direct support.

NRPM 4.10 governs a different beast: a dedicated contiguous /10 block reserved specifically to enable IPv6 deployment transitions. Under policy NRPM 4.10, a contiguous /10 IPv4 block has been set aside and dedicated to enable IPv6 deployment. Applicants must prove immediate requirements for dual-stack DNS servers or NAT-PT translators instead of general growth. The rules mandate that no other allocation source can satisfy these specific transition needs before approval occurs.

A mandatory six-month waiting period separates subsequent allocations under this deployment policy. Previous assignments must maintain strict utilization rates to retain eligibility for future resources. Organizations holding re-allocations must show efficient utilization consistent with NRPM sections 4.2.3 and 4.2.4. Slow renumbering processes sometimes delay necessary infrastructure upgrades despite these efficiency mandates. Auditing existing inventory prevents wasted cycles during the application phase. This documentation framework limits hoarding while supporting the global migration to next-generation protocols.

Applying ISP vs End User IPv4 Request Criteria

Your classification determines your fate. Distinguishing ISP status from end-user classification decides immediate eligibility for initial /24 allocations without prior utilization history. All ISP organizations without direct allocations, direct assignments, re-allocations or reassignments automatically qualify for a /24. Service providers reassign these blocks to external customers as their primary business function. End users deploy similar resources strictly for internal employee networks and private infrastructure. The destination of the addresses defines the regulatory path each organization must follow.

The math is unforgiving. Applicants seeking additional capacity beyond initial grants must provide data demonstrating at least 50% utilization of each allocation and 80% of the sum of all allocations to prove efficient management. This threshold forces organizations to exhaust existing inventory before accessing the scarce remaining supply found on the Waiting List. ISPs holding re-allocations must show efficient utilization of their resources consistent with policy requirements. Network diagrams require rigorous auditing to ensure the request category matches actual deployment architecture. Accurate classification simplifies approval and secures necessary IPv4 assets for sustained connectivity.

Risks of Non-compliance with NRPM 4.10 Justification Requirements

Do not bother applying if you cannot prove immediate IPv6 deployment needs. Staff use their discretion when evaluating justifications under NRPM 4.10 scrutiny, and failure to meet the bar results in rejection. This policy governs a dedicated /10 block reserved exclusively for transition technologies like dual-stack DNS servers. Applicants cannot receive resources if they obtained space under this specific rule within the preceding six months. Strict temporal gating prevents hoarding of these critical transition assets by limiting access frequency.

Operators must demonstrate that existing allocations cannot meet the technical requirement before requesting new space. Staff discretion applies heavily when evaluating whether a request truly supports IPv6 deployment versus general expansion. If your justification smells like general growth, it will be denied.

Inside ARIN's Allocation Mechanics and Documentation Requirements

Defining ARIN ISP Allocations vs End User Assignments

The distinction between ISP allocations and end user assignments determines whether an organization reassigns address space to customers or operates infrastructure exclusively for internal employees. ARIN allocates blocks of IP addresses to ISPs specifically for the purpose of reassigning that space to their customers under NRPM Section 4.2. Conversely, an end user operates a network solely for its workforce and does not provide internet services to external clients. This classification dictates the applicable policy framework, with ISPs adhering to NRPM 4.2.2 for initial requests and subsequent expansion. Operators must demonstrate efficient utilization by providing reassignment information for customer blocks via SWIP or RWhois protocols.

The primary failure mode in request submissions involves providing summary statistics instead of the requisite per-pool utilization metrics. While operators often assume total network usage suffices, policy mandates showing utilization for each discrete block. This granularity ensures that scarce resources are not hoarded but actively deployed. Organizations ignoring these specifics face delays, especially when justifying needs that extend toward a 24-month supply within the transfer market. The requirement for recipients to demonstrate such extended need implies that initial documentation sets the baseline for all future growth claims. Precise alignment between technical reality and submitted spreadsheets remains the single most effective strategy for accelerating approval timelines.

Validating Exemptions for New ISP /24 Qualifications

Automatic qualification for a /24 allocation applies strictly to ISPs lacking prior direct assignments or reassignments from ARIN. These entities bypass standard efficiency metrics because they hold no historical inventory to evaluate against NRPM 4.2.2 thresholds. Verification requires confirming zero existing direct allocations, direct assignments, re-allocations, or reassignments before submission to qualify for this exemption. Under policy NRPM 4.3.2, the minimum size for an end-user assignment is a /24. Operators must validate their status against four distinct documentation pillars before filing if they seek allocations larger than the automatic /24 or hold prior resources.

The administrative burden of proving need increases significantly after the first allocation, as organizations must then demonstrate efficient use of that initial block. Regional dynamics vary globally, with some registries maintaining large reserved pools, yet ARIN applicants holding re-allocations or reassignments must show efficient utilization of their resources. This strategic check prevents disqualification from the very pool designed to accelerate market entry.

Executing IPv4 Requests Through Transfers and Waiting Lists

ARIN Online Account Prerequisites for IPv4 Requests

Accessing the ARIN Online portal demands a verified account linked explicitly to an authorized Admin or Tech POC. The system rejects any submission attempt lacking this specific credential hierarchy tied to a valid Org ID. Operators navigate the menu to select "IP Addresses" followed by "Request" to start the workflow. This digital gateway serves as the only entry point for the Waiting List or a Specified Recipient Transfer. Despite the 2015 free pool exhaustion, ARIN continues processing approved customer requests through these alternative mechanisms. Precise alignment between the user profile and the organization's recorded authority figures is mandatory. A mismatch in the POC record causes immediate administrative delays rather than simple automated rejections. Analysts typically review complete submissions within two business days, though they will request additional documentation if justification data lacks depth. Organizations must factor in the cost of compliance and validation processes required to prove the "24month supply" need. This administrative overhead adds complexity not present in pre-depletion eras of simple resource acquisition. Neglecting the POC linkage creates a hard block that no amount of technical justification can bypass.

Step-by-Step IPv4 Transfer and Waiting List Submission

Navigate the ARIN Online portal by selecting "IP Addresses" then "Request" to initiate any acquisition workflow. This single entry point gates access to both the Waiting List and Specified Recipient Transfer mechanisms, forcing operators to choose between queued recovery or immediate market purchases. The decision hinges on deployment urgency versus budget constraints, as transfers require proving need for a 24month supply while waiting list slots arrive unpredictably.

1. Log in with an authorized Admin or Tech Point of Contact record linked to your Org ID.
2. Draft a justification document detailing immediate IPv6 deployment needs like dual-stack DNS or NAT464 translators.
3. Upload evidence showing no other allocations can meet this specific technical requirement.

An ARIN Customer Service Resource Analyst typically reviews submissions within two business days, requesting clarification or granting approval based on the strength of the provided data. The waiting list offers a path to resources without direct purchase costs, yet the opacity of queue progression creates planning uncertainty for time-sensitive infrastructure projects. Organizations must weigh the certainty of transfer pricing against the indefinite wait for recovered blocks.

NRPM 4.10 Justification Checklist for IPv6 Deployment Blocks

Validate immediate dual-stack DNS requirements before drafting your NRPM 4.10 submission to prevent automatic rejection. This policy reserves a contiguous /10 block strictly for IPv6 transition mechanisms like NAT-PT translators, rejecting general expansion claims. Operators often overlook that re-applying before the mandatory six months elapses voids previous progress, creating a self-inflicted moratorium on critical infrastructure updates.

The constraint here is absolute: a single /24 represents the maximum initial grant, regardless of projected growth curves. Applicants must accept that subsequent approvals may mandate renumbering out of earlier non-contiguous blocks to preserve registry hygiene. This limitation ensures the reserved pool serves genuine transition projects rather than acting as a secondary market loophole.

Strategic Outcomes of Optimized IPv4 Acquisition Strategies

ARIN Waiting List vs Transfer Market Mechanics

ARIN recorded the exhaustion of its IPv4 Free Pool on 24 September 2015, ending direct allocations from primary reserves. The Waiting List now depends entirely on reclaimed addresses, a finite supply governed by strict policy requirements for unmet requests. Market transfers operate differently by allowing buyers to acquire specific blocks if the buyer justifies a 24-month supply. This distinction creates a clear tension between cost efficiency and deployment speed. Operational risk defines the Waiting List because infrastructure projects cannot schedule around unknown availability dates. Transfers demand rigorous NRPM 8.5 compliance yet provide certainty for time-sensitive rollouts. Many operators miss that waiting list participation does not preclude simultaneous transfer negotiations. Receipt of an allocation from reserved pools does not affect eligibility to be on the Waiting List for Unmet Requests. Companies holding excess space should release it to specified recipients to optimize regional IP Management. This choice defines network scalability for the coming fiscal year.

Applying NRPM 4.10 for Critical Infrastructure IPv6 Deployment

Network architects invoke NRPM 4.10 when dual-stack DNS servers or NAT-PT translators need dedicated IPv4 space. Under this policy, a contiguous /10 IPv4 block has been set aside and dedicated to enable IPv6 deployment. Operators must prove that no other existing resources meet these critical infrastructure needs before ARIN staff evaluate the justification. Since the global trigger in February 2011, regional registries have managed scarcity by isolating such transition enablers from the general market. Applicants receiving space under this clause face a strict six-month moratorium on subsequent requests. Resources must drive actual migration rather than hoarding. The operational constraint involves potential renumbering mandates where ARIN staff may require shifting previous transition blocks. This measure maintains contiguous address space for future applicants. Previous allocations/assignments under this policy must meet the utilization requirements of end user assignments to remain compliant. InterLIR advises verifying that infrastructure projects strictly align with dual-stack or translation use cases before submission. The policy remains a narrow pathway for core internet services to sustain connectivity during prolonged exhaustion. Successful navigation requires precise documentation proving standard micro-allocation channels are insufficient for the specific transition architecture.

Operational Risks of RIR Regional Scarcity Variance

Organizations facing ARIN's near-zero inventory must choose between indefinite waiting lists or premium-priced transfers based on deployment urgency. AFRINIC maintains a reserve of over 4 million addresses, creating distinct global market dynamics unlike the fragmented recovery model in North America. This disparity forces operators to decide whether to wait for reclaimed space or purchase immediately via the secondary market. Strategic risk emerges from assuming uniform global availability. Some regions offer limited direct allocation while others rely entirely on private transactions. Relying solely on waiting lists introduces project timeline uncertainty that transfer markets can bypass, albeit at higher capital expense. Regional policy divergence creates compliance friction for multinational corporations managing unified addressing schemes across borders. InterLIR enables navigation of these complex transfer protocols to secure necessary IPv4 blocks efficiently. Executives must evaluate whether their specific use case tolerates the latency of reclamation or demands the immediacy of market procurement. Ignoring this regional variance jeopardizes network expansion plans in saturated markets.

References

• ARIN organizations may qualify for the transfer of a
• IPv4 Transfer Market: How Does It Work and Is