ARIN Specified Transfer Policies vs RIPE & APNIC Rules

ARIN specified transfer policies govern how IPv4 blocks move between organizations in the North American region, and they differ in important ways from the frameworks used by RIPE NCC and APNIC. For network engineers and IT managers planning to buy, sell, or lease address space, these regional differences matter — a lot. Get the strategy wrong and you can end up with months of delays, a rejected application, or a block that simply won’t route globally.

Why Regional Transfer Policies Matter in the IPv4 Market

The IPv4 free pool is exhausted in every RIR region. Virtually all new supply now comes from the secondary market, and each Regional Internet Registry enforces its own transfer rules, eligibility criteria, and documentation requirements. A /24 that moves smoothly under ARIN rules may hit entirely different hurdles under RIPE or APNIC oversight.

Picture a practical scenario. A U.S.-based cloud provider wants to sell a /22 to a European hosting company. The transaction must comply with ARIN’s specified transfer policies on the seller’s side and RIPE NCC’s requirements on the buyer’s side. If the buyer cannot demonstrate a justified need for the addresses, the transfer stalls — no matter how clean the seller’s holdings are. I’ve seen deals fall apart exactly there, at the documentation stage, because someone ignored the receiving region’s rules.

What varies by region?

• Need justification requirements for the receiving organization
• Holding periods before newly transferred blocks can be moved again
• Maintenance fee structures and ongoing registration costs
• Eligibility of the receiving organization type (LIR membership, direct assignment, etc.)

Working with an experienced marketplace partner such as IP4 Market helps both parties navigate these overlapping requirements. Verified sellers and pre-screened buyers reduce the risk of a failed or delayed transfer — and in this market, that risk is not trivial.

Understanding ARIN Specified Transfer Policies

ARIN’s transfer framework rests on the Number Resource Policy Manual (NRPM), particularly section 8, which defines both M&A-based transfers and specified transfers between unrelated organizations. Under the ARIN specified transfer policies, the receiving organization must demonstrate an immediate need for the address space, typically justified by current or near-term infrastructure requirements documented in the request.

Key Requirements Under ARIN Rules

• Need justification: The recipient must show utilization projections supporting the block size requested, generally reviewed against ARIN’s utilization thresholds.
• Eligible recipients: Organizations must qualify under ARIN’s registration criteria, or be members of another RIR where inter-RIR transfers are permitted.
• Transferee listing: ARIN publishes approved transfers publicly. Transparency, yes — but also a waiting period for processing.
• Blacklist screening: Blocks listed on abandoned or known-abusive ranges may face additional scrutiny before approval.

A word of practical advice: prepare your justification documentation before listing a block or making an offer. Buyers should gather network diagrams, growth plans, and current utilization data in advance. ARIN review times can stretch several weeks, and an incomplete submission restarts the clock. Sellers, for their part, should verify that their registration records are accurate and free of legacy disputes before engaging buyers.

RIPE NCC Transfer Rules: The Contrasting Approach

RIPE NCC handles transfers between Local Internet Registries (LIRs) rather than between arbitrary organizations. Under RIPE policy, an entire LIR holding is transferred with the membership itself, and intra-RIR transfers require the receiving LIR to justify the address space through documented needs. Notably, RIPE does not impose the same utilization-based need thresholds for all block sizes, and its “last /8” policies add further complexity for smaller allocations.

Take the European buyer acquiring a /23 from an ARIN seller. The transfer typically routes through an LIR structure, which changes the cost model: RIPE membership fees and setup charges add recurring overhead that ARIN direct assignments may not carry. RIPE has also historically been more permissive about leasing arrangements within its region — which is one reason it has become a hub for lease-based IPv4 supply.

These structural differences between the ARIN and RIPE frameworks are the foundation for evaluating APNIC’s distinct rules, which we will examine next.

APNIC Transfer Requirements and Eligibility Criteria

APNIC’s framework stands apart from both ARIN and RIPE in one key respect: it only allows intra-regional and inter-regional transfers under tightly defined conditions. The transferring and the receiving organization must both be current APNIC members or holders of APNIC-registered address space. The receiving organization may acquire a /22 block at minimum under APNIC’s needs-based policy, and here’s the part that catches people off guard — APNIC will let entities receive space even if they already hold other IPv4 allocations, as long as they can show a documented usage plan covering the requested size.

Then there’s the waiting period. Twenty-four months, mandatory. An organization that receives transferred address space cannot transfer it again within two years, except in cases of insolvency or mergers. This anti-speculation clause has no direct equivalent in the ARIN specified transfer policies, where transferred space can generally be re-transferred whenever. Is your source block clean of APNIC restrictions? Buyers working across the Asia-Pacific region should confirm this before committing any funds. Any funds.

• Eligibility check: verify the holder’s membership status and block history in the APNIC whois database.
• Size limits: receiving organizations are capped at a /22 per transfer application under current policies.
• Fees: APNIC charges an administrative processing fee per transfer, separate from broker costs.

M&A Transfers, Legacy Holdings, and Documentation Differences

Certified transfers arising from mergers and acquisitions follow a distinct track in all three regions. Under ARIN specified transfer policies, M&A activity is handled as a reassignment of resources rather than a market transfer, which means the 24-month restrictions don’t apply and the process tends to move faster. RIPE NCC treats M&A transfers similarly, processing them as changes of legal entity — you’ll need consolidation agreements, articles of association, and proof of the corporate transaction.

Legacy holdings complicate things further. Space registered before the RIRs even existed can often be transferred more freely, but the paperwork requirements vary noticeably. ARIN demands a Legacy Registry Agreement or RSA conversion first. RIPE legacy holders, meanwhile, may need to establish a contractual relationship with the NCC before a transfer can be validated. In practice, buyers should ask for chain-of-custody evidence, updated registration data, and written confirmation from the relevant RIR that the block isn’t under dispute, validation review, or litigation hold — before closing anything.

Conclusion: Choosing the Right Path for Your IPv4 Transfer

Working through the ARIN specified transfer policies alongside RIPE and APNIC rules really comes down to three things: regional eligibility, waiting-period restrictions, and documentation readiness. ARIN offers the most liquid market with clear two-year reclaim limitations. RIPE gives you flexibility through its minimum-allocation model. APNIC imposes the strictest anti-speculation safeguards of the three. Whichever region governs your transaction, engaging a RIR-accredited facilitator early and validating every document before payment remains the surest way to close safely.

For organizations after a streamlined experience, IP4 Market offers a trusted platform for IPv4 transactions with verified sellers, transparent pricing, and full support for transfers across ARIN, RIPE, and APNIC regions. Buying your first /22 or divesting a larger portfolio — either way, working with an experienced partner ensures your transfer complies with every applicable regional policy from start to finish.