InterRIR IPv4 transfers: 4 regions allow them

Trading IPv4 blocks between Regional Internet Registries is legal, provided you stay out of Africa. Four of the five global bodies permit these moves; AFRINIC does not. What started as a regulatory curiosity has hardened into standard operating procedure for any organization needing address space outside its home jurisdiction. As IPv4 scarcity forces buyers to look globally, the divergent policies of ARIN, RIPE, APNIC, and LACNIC dictate success or failure.

This guide cuts through the compliance noise. You need to know that pre-approval workflows differ wildly: ARIN, APNIC, and LACNIC demand proof of need before you even talk to a seller, while RIPE handles justification during the transaction. We will cover the negotiation phase, where escrow agents and transfer dates get locked into an Asset Purchase Agreement.

Finally, we walk through the transfer request workflow. The seller initiates the move, often covering fees mandated by their local registry. The seller's RIR then coordinates directly with the buyer's RIR to finalize the handover, ensuring IPv4 addresses cross policy zones legally. Miss a step here, and you face costly delays in a market where geographic flexibility defines access.

The Role of Inter-RIR Transfers in Global IPv4 Redistribution

Inter-RIR Transfer Definition and AFRINIC Policy Exclusion

An inter-RIR transfer legally moves IPv4 blocks across regional boundaries between owners in different registries. This mechanism is the only way organizations can access global supply when local IPv4 resources run dry. Trading and transferring addresses between RIRs is a validated practice that has operated for some time. Four substantial registries including ARIN, LACNIC, RIPE, and APNIC actively support these cross-border transactions through established frameworks.

Africa remains the outlier. AFRINIC currently lacks a policy allowing inter-RIR transfers, effectively isolating its address space from global market flows. Buyers cannot source blocks directly from this region, and sellers within its jurisdiction cannot export addresses to satisfy demand elsewhere.

Transfer justification requirements vary notably by jurisdiction. An ARIN to RIPE NCC move requires strict adherence to both policy sets simultaneously. Failure to align documentation standards across both regions results in immediate disqualification. The absence of a unified global standard creates a complex compliance environment where procedural errors block asset utilization.

Applying ARIN and RIPE Needs-Based Rules to Inter-RIR Requests

Recipients within the ARIN region must demonstrate a documented need for up to a 24-month supply of IPv4 addresses to qualify. This strict justification protocol ensures that available resources address genuine infrastructure expansion rather than speculative holding. The operational burden involves submitting detailed network diagrams and growth projections before any transaction proceeds.

Transfers subject to needs-based policies often mandate a utilization plan covering at least 50% of the acquired space within a five-year timeframe. This requirement forces organizations to align address acquisitions with concrete deployment schedules rather than immediate stockpiling. Failure to meet these utilization milestones can jeopardize future resource requests or trigger audits.

Market activity reflects the complexity of navigating these divergent regulatory environments. In April 2022 alone, ARIN statistics recorded 19 specific requests for inter-RIR transfers, distinct from merger-related movements. This volume indicates sustained demand despite the administrative overhead required for cross-regional compliance. Organizations failing to align their internal planning with these specific temporal constraints face delayed deployments.

Pre-Approval Timing Differences Between APNIC, ARIN, LACNIC, and RIPE

APNIC, ARIN, and LACNIC mandate that buyers complete justification processes before any transfer request initiates. Organizations in these regions must apply for pre-approval to demonstrate legitimate operational need prior to negotiation. In contrast, RIPE integrates this validation directly into the transfer workflow rather than requiring upfront certification. This structural divergence means buyers in the RIPE region face a single procedural step where peers elsewhere manage two distinct phases.

The operational impact creates a distinct planning horizon for network architects managing global inventory. Some registries delay transaction initiation until need is proven. Others validate intent concurrently with asset movement. Fee structures also diverge, with some regions charging a fee per party while others levy no specific transfer costs. This variance requires careful budget alignment before engaging sellers across different zones.

Delaying documentation until a seller is found often results in missed acquisition windows. The lack of upfront validation in Europe allows quicker deal closure but demands rigorous internal audit readiness.

Executing Seller-Initiated Requests and RIPE Inter-RIR Templates

The seller initiates an online request with their local registry to begin the official inter-RIR transfer workflow. This action triggers a verification sequence where the Transfer Request moves between regional databases. Operators must recognize that specific documentation standards differ by region, creating a potential bottleneck for unprepared applicants. RIPE specifically mandates that sellers complete a dedicated inter-RIR template rather than relying on standard intra-regional forms. This requirement ensures that cross-border data fields are captured correctly before the buyer's registry engages.

Private transactions often apply an Asset Purchase Agreement to define commercial terms separate from regulatory validation. Parties frequently negotiate the choice of escrow agent during this phase to secure the financial component. The divergence in documentation creates a friction point where a missing template halts the entire Negotiation process regardless of buyer readiness.

1. Seller submits the specific RIPE inter-RIR template to their local registry.
2. Registry validates the seller's authority and template completeness.
3. Seller's registry contacts the buyer's registry to initiate cross-checks.

Strict adherence to these forms prevents delays that often extend beyond the typical one-month processing window observed in other regions. Successful execution depends on treating these forms as binding technical specifications rather than simple paperwork.

Validating Membership Documents and Director Details for RIR Submission

Successful validation hinges on submitting accurate membership documents and verified director details to satisfy regional legitimacy checks. Operators must compile proof of registration alongside specific information regarding the company director or equivalent role, as omissions here frequently trigger immediate request rejection. The RIR may request additional buyer information and a signed confirmation form to finalize the verification stage.

Legacy resources present unique challenges when the receiving party opts out of a contractual relationship with the RIPE NCC. A confirmation letter signed by a legally authorized company director is mandatory in these cases, showcasing specific legal workflows for legacy blocks. This strict requirement means that even minor discrepancies in director names between corporate registries and RIR databases can halt an entire transaction.

Defining RIR Transfer Fees and Administrative Costs

Administrative costs vary notably because specific fee structures are noted for ARIN, RIPE, LACNIC, and APNIC. This variation creates distinct financial considerations for operators engaging in cross-regional trades. While some regions impose transaction expenses, others apply different models that affect the total cost of acquisition.

Minimizing immediate transaction costs often conflicts with securing long-term asset liquidity in preferred regions. Operators focusing solely on fee avoidance might overlook critical operational delays inherent in lower-cost jurisdictions. Cost efficiency is a factor, yet the lack of upfront fees does not guarantee quicker processing compared to models that prioritize expedited review. Organizations should engage InterLIR to navigate these divergent financial landscapes and optimize total acquisition costs. Detailed fee schedules often change, so verifying current rates through official RIR documentation remains necessary before finalizing budgets. Unprepared applicants risk stalled transactions if funding does not align with specific regional deposit mandates.

Application: Executing Seller-Initiated Requests Using RIPE Templates

The seller initiates the process by populating the mandatory inter-RIR template provided by the registry. This specific document captures cross-regional data fields that standard intra-regional forms omit, ensuring all necessary routing information is present.

Execution requires strict adherence to the following workflow:

• Access the registry portal to download the current inter-RIR template.
• Input precise director details and organizational registration data.
• Submit the completed file through the assigned online request interface.
• Await validation confirmation before the buyer's registry engages.
• Verify buyer utilization plans align with long-term compliance timelines.

Compliance with utilization mandates remains a prerequisite, as recipients acquiring space under needs-based policies must demonstrate a plan to use the resources within a set period. The timing of this justification varies; unlike regions where buyers prove need upfront, others integrate this validation during the transfer, shifting the burden of proof to the execution phase. This structural difference means sellers cannot rely on buyer pre-approval status alone to guarantee success. Network architects must verify that the buyer's utilization plan aligns with these long-term compliance timelines before finalizing negotiations. Properly executed, this mechanism unlocks global inventory without requiring new address creation.

Application: Validating Membership Documents and Director Details

Submitting verified membership documents and accurate director details prevents immediate rejection during the RIR legitimacy review phase. Operators frequently overlook that legacy resource transitions often mandate a confirmation letter signed by a legally authorized company director if the recipient opts out of a new contractual relationship. This specific legal workflow preserves legacy status but introduces a single point of failure if the signatory lacks proper corporate authority. Balancing legacy advantages against modern administrative verification standards is essential for cross-region validity.

Necessary documentation for successful validation includes:

• Current proof of organizational registration from a government authority.
• Verified identity details for the company director or equivalent role.
• Signed confirmation forms explicitly authorizing the specific IPv4 transaction.
• Completed inter-RIR transfer templates where regionally mandated by policy.
• Legal authorization letters for legacy block recipients avoiding new contracts.

Delays or failures in the transfer process due to non-compliance can result in significant financial loss for businesses, extending beyond the standard administrative fees. Processing timelines fluctuate wildly based on region. ARIN post-completion reviews take up to 1 month. RIPE post-completion reviews also take up to 1 month. APNIC follows a similar post-completion window of up to 1 month. LACNIC stands apart with a split payment structure requiring 2–10 months for completion. LACNIC uniquely mandates partial payment before the process begins.

Mitigating Disqualification Risks and Database Update Failures

Defining Disqualification via Unpaid Fees and Database Sync Failures

Unpaid administrative fees stop inter-RIR transactions before resources move. Regulatory bodies enforce strict payment compliance, causing trades to collapse if costs remain unsettled. This financial gatekeeping prevents incomplete records from cluttering regional ledgers while protecting global marketplace integrity. Technical breakdowns happen when operators neglect to update public databases reflecting the new allocation of IPv4 addresses. The database update serves as the definitive chronological marker where legal routing authority transfers to the recipient. Ignoring this synchronization step leaves the IP space legally unannounceable via BGP, effectively rendering purchased assets useless for production traffic.

Common operational failures leading to transfer issues include:

• Non-payment of required registry processing fees by either participating party.
• Neglecting to record the new allocation in the receiving RIR's public registry.
• Attempting to announce routes prior to the official database synchronization event.
• Failing to secure the sign-off from both regional registries before announcing blocks.

Operators must verify both fee clearance and registry updates to secure their investment in scarce IPv4 resources.

AFRINIC Policy Exclusion and Market Liquidity Risks

Four of the five substantial registries actively process cross-border IPv4 transactions, yet AFRINIC remains the sole exception without an inter-RIR framework. This specific policy gap isolates African address space from global redistribution channels, effectively freezing liquidity for operators in that region. Unlike peers in ARIN or RIPE who source blocks globally to meet demand, African entities cannot legally import IPv4 resources through standard inter-RIR mechanisms. The absence of a transfer protocol creates a hard boundary for market participants seeking to optimize asset utilization across continents.

• Sellers cannot route unused African allocations to international buyers needing immediate supply.
• Buyers lose access to potential inventory that could satisfy their 24-month justification requirements elsewhere.
• Regional price disparities widen as local supply remains trapped while demand grows unchecked.
• Intra-regional trade volumes fail to stabilize pricing due to limited local availability.

This exclusion forces organizations to rely entirely on intra-regional trades, which often lack sufficient volume to stabilize pricing or ensure availability. The limitation is structural; without the mechanism to validate need and update records across registry boundaries, no amount of private negotiation can trigger a legal title change. The market waits for AFRINIC to align with global standards, but until then, African IPv4 assets remain illiquid compared to the rest of the world. Operators often miscalculate this window by including reserved but unassigned space in their immediate burn-rate projections, triggering rejection during the technical review. The receiving RIR validates this need against current inventory levels before approving any cross-border movement of assets.

Compliance extends beyond immediate needs to long-term deployment strategies for the acquired block.

• Cross-reference projected growth charts against the five-year utilization plan mandate to ensure logical consistency.
• Confirm that all membership documents align with the entity requesting the transfer to avoid identity mismatches.
• Submit detailed engineering diagrams showing exact router configurations rather than high-level summaries.
• Avoid generic growth templates that lack specific subnet assignments or routing policies.

A common failure mode involves submitting generic growth templates that lack specific subnet assignments or routing policies. Such documentation may require the RIR to request clarifications, extending the timeline while the application sits in a pending state. Delays or failures in the transfer process due to non-compliance can result in significant financial loss for businesses, extending beyond the standard administrative fees. InterLIR recommends pre-validating these technical artifacts against the specific resource transfers guidelines before submission. Detailed engineering diagrams showing exact router configurations carry more weight than high-level executive summaries. Precision in these initial documents determines whether the transfer proceeds smoothly or stalls indefinitely in administrative limbo.

References

• RIPE IPv4 Transfer Process: How to Buy, Sell, and
• IPv4 Transfer Market: How Does It Work and Is