APNIC IPv4 transfers: Your 24-month usage plan

Recipients without existing IPv4 resources must prove a detailed 24-month usage plan to satisfy APNIC policy criteria. This mandate defines the modern reality of IPv4 address transfers, where regulatory compliance outweighs simple market availability. Successful execution requires strict adherence to APNIC transfer policies rather than relying on legacy assumptions about address liquidity.

Regional Internet Registries like AfriNIC, ARIN, LACNIC, and the RIPE NCC operate under IANA authority to manage these finite assets. The text details the four specific scenarios permitted for moving resources, including transfers between current account holders and cross-region exchanges involving other RIR regions. It further clarifies the distinction between Local Internet Registry entities and holders of historical IPv4 addresses lacking an APNIC account.

The guide outlines the mechanical steps for validating registration data in the APNIC Whois Database to ensure network integrity during mergers or acquisitions. Demonstrating legitimate need remains the primary hurdle for new entrants seeking address space. Understanding these regulatory constraints is necessary for any organization attempting to secure or divest public Internet address space in the current environment.

Defining the Scope of APNIC IPv4 Transfers and Historical Resources

APNIC IPv4 Transfer Scenarios and LIR Roles

APNIC defines four distinct scenarios for moving IPv4 blocks to maintain registry accuracy. The process strictly governs transfers between current account holders, cross-regional exchanges with other RIRs, organizational mergers, and the integration of legacy assets. A Local Internet Registry typically acts as the ISP managing these assignments for downstream networks. Distinct protocols apply when moving historical IPv4 resources from entities lacking active accounts to current members. These legacy transfers require submitting a specific template via email rather than using standard market forms.

• Transfers between current APNIC account holders
• Exchanges involving organizations in other RIR regions
• Integration of legacy addresses from non-account holders
• Resource movement during mergers or acquisitions

Inter-RIR movement is limited to partnerships with RIPE NCC, ARIN, and LACNIC. The APNIC Whois Database records every transaction to prevent speculation and verify legitimate ownership. Operators must recognize that legacy holders without the agreements face different validation steps than current members holding current resources. This separation ensures that unregulated legacy assets do not bypass policy checks designed for the modern market. Recipients that already hold IPv4 resources must provide evidence of compliance with APNIC policies regarding their past delegations before a new transfer can be approved. InterLIR assists networks in navigating these specific pathway requirements to secure valid title.

APNIC permits inter-RIR transfers exclusively with RIPE NCC, ARIN, and LACNIC regions.

This restriction defines the global liquidity boundary for IPv4 assets, preventing speculative movement into regions lacking compatible policy frameworks. This procedural step validates the authentic holder status before APNIC reviews the recipient's eligibility. Without this upstream verification, the transfer sequence cannot proceed, creating a hard dependency on cross-regional administrative alignment.

Recipients that do not already hold IPv4 resources must demonstrate a detailed plan for the use of the transferred resource within 24 months of the transfer. Such organizations must submit this utilization plan to justify the request. This requirement prevents warehousing by entities without immediate infrastructure needs. Rapid acquisition goals often clash with the necessity of proving technical readiness within this fixed window.

Network architects must treat regulatory alignment as a prerequisite equal to technical configuration. Ignoring the limited list of eligible regions wastes cycle time on impossible transactions.

Risks of LIR Closure and 103/8 Free Pool Transfer Restrictions

IPv4 blocks delegated from the 103/8 free pool face a mandatory five-year transfer lock following their original assignment date.

This restriction prevents immediate resale, ensuring that resources allocated for specific infrastructure needs remain active within the intended network rather than entering the secondary market prematurely. Operators attempting to move these assets before the timeline expires will find the transaction blocked by registry policy enforcement. The limitation acts as a protective measure for remaining free pool assets, prioritizing genuine network expansion over speculative trading.

• If an LIR ceases internet connectivity services, all current resources including IPv4, IPv6, and AS numbers must be returned to APNIC.
• Addresses from the 103/8 range cannot be transferred for a minimum of five years after delegation.
• Liquidators must advise customers that renumbering is necessary upon resource return.

The operational risk here involves the sudden loss of asset liquidity should an organization's LIR status terminate. Unlike historical resources which may carry different stipulations, current allocations must be returned to APNIC if the LIR ceases to provide Internet connectivity services. This creates a critical dependency where the validity of ownership ties directly to active service provision.

Authentic Holder Verification and Dispute Resolution in Inter-RIR Transfers

The registry rejects any transaction where the authentic holder identity fails to match the source account without active disputes. APNIC mandates that the resource remains under the management of the RIR where the source maintains their account to validate ownership. This strict alignment prevents speculative transfers involving contested assets, ensuring that only verified owners initiate cross-regional moves. APNIC currently recognizes inter-RIR transfers only with three specific counterpart regions: RIPE NCC, ARIN, and LACNIC.

Meanwhile, the verification workflow requires distinct steps depending on the origin of the assets involved in the exchange.

1. The source organization confirms their account status with their local registry.
2. Administrators verify that no third-party disputes exist regarding the specific IPv4 blocks.
3. The initiating party contacts their each RIR to begin the handshaking process.
4. A transfer fee must be paid before the IPv4 transfer is executed and the resources are received.

However, the cost of maintaining this integrity is a slower transaction timeline compared to intra-regional deals. The limitation is that APNIC inter-RIR transfers are strictly limited to specific counterpart regions, whereas transfers involving other regions are not currently permitted. This procedural friction ultimately protects the global routing table from fraudulent re-assignments.

Applying the 24-Month Usage Plan for New Entrant Recipients

Recipients without existing IPv4 resources must demonstrate a detailed usage plan within 24 months of the transfer. This compliance window fundamentally shifts the verification timeline compared to standard allocations, which typically demand pre-approval of need before any address space is assigned. New entrants operate under a post-transfer validation model where the burden of proof moves to the period immediately following acquisition.

The regulatory focus remains on preventing speculation while ensuring transferred blocks reach active network infrastructure within a reasonable timeframe. Operators can review the specific policy details to understand the strict deadline for submitting utilization evidence. Unlike inter-RIR transfers involving RIPE NCC or ARIN that rely on immediate policy alignment, this mechanism accommodates organizations entering the market without prior holdings.

1. Acquire IPv4 blocks through a verified inter-RIR transfer or regional exchange.
2. Deploy infrastructure to apply the assigned address space effectively.
3. Submit the detailed usage plan to APNIC before the 24-month expiration.

Balancing rapid deployment against accurate forecasting is critical. Recipients that already hold IPv4 resources must provide evidence of compliance with APNIC policies regarding their past delegations before a new transfer can be approved. This approach mitigates the risk of failing the subsequent audit, which could jeopardize future eligibility for additional resources.

LIR Closure Protocol: Customer Renumbering and Resource Return Steps

An LIR ceasing connectivity services triggers an immediate mandate to return all current IPv4, IPv6, and AS numbers to the registry.

This protocol activates strictly when the organization stops providing internet services, requiring the liquidator to advise customers that renumbering is necessary before any assets are released. The operational sequence demands precise execution to avoid policy violations:

1. Notify all downstream customers of the mandatory renumbering requirement.
2. Ensure the LIR or its liquidator advises customers that renumbering is necessary.
3. Return all current resources to APNIC as the LIR ceases to provide Internet connectivity services.

Operators must distinguish this closure scenario from standard market transactions. A transfer moves ownership to a new entity, whereas closure returns space to the registry for future redistribution.

While inter-regional moves allow continued use under a different counterpart RIR, closure offers no such continuity for the specific blocks. If a new LIR takes over, the address space transfer is subject to re-examination by APNIC and may be treated as a new address request.

Defining the Recipient Request and Pre-Approval Workflow

A recipient request formally initiates the change of ownership for IPv4 blocks within the APNIC region. This mechanism distinguishes between current account holders and organizations holding historical resources without active accounts. New entrants lacking existing address space face a distinct compliance path compared to established operators. These organizations must submit a detailed usage plan within 24 months rather than proving immediate need. Operators can avoid transaction delays by requesting a transfer pre-approval to evaluate requirements before identifying a source. Holders of legacy assets must follow a separate submission protocol via email to the administration team for historical resource transfers. The procedural divergence creates a bottleneck where unverified buyers stall deals while waiting for manual policy confirmation.

1. Verify registration data accuracy in the WHOIS database before contacting sellers.
2. Submit the pre-approval application if no current IPv4 resources are held.
3. Coordinate the final transfer submission through InterLIR once a source is confirmed.

InterLIR simplifies this validation to ensure rapid deal closure without administrative rework.

Step-by-Step Execution for Mergers and Acquisitions

Organizational consolidation triggers the transfer between organizations through a merger, acquisition, or takeover to update legal ownership records. This specific mechanism distinguishes corporate structural changes from simple administrative name updates within the registry database. The primary trade-off is the requirement for thorough legal documentation proving the entity succession before any technical records change. Operators ignoring this distinction risk having their assets frozen during due diligence periods.

1. Verify the authentic holder status matches the acquiring entity without disputes.
2. Submit source and recipient requests via the InterLIR portal to initiate the workflow.
3. Update the APNIC Whois Database to reflect the new legal entity name and contact details.

These transactions are recorded in the APNIC Whois Database to ensure network integrity throughout the transition. A frequently overlooked consequence is that failure to update these records invalidates the legal standing of the resource holder during future audits. The acquiring organization assumes full liability for the address block immediately upon registration completion. InterLIR enables this process by validating the registration data accuracy prior to submission.

Validation Checklist for Source and Recipient Registration Data

Accurate registration data verification prevents immediate rejection during the APNIC transfer audit phase. Operators must confirm the authentic holder matches the source account without disputes before initiating any transaction.

1. Validate that current LIR status is active for both parties in the APNIC region.
2. Confirm historical resources lack the agreements if transferring from legacy holdings.
3. Ensure recipients without prior holdings prepare a usage plan for submission within the mandated window.
4. Review compliance evidence regarding past delegation policies for existing resource holders.

New entrants face a strict 24-month deadline to demonstrate detailed usage, whereas established operators must prove historical adherence to policy. This divergence creates a compliance asymmetry where past performance dictates current eligibility speed. InterLIR recommends submitting a recipient request only after verifying your registration information is accurate to avoid administrative loops. Failure to align source and recipient data types results in immediate processing halts.

Strategic Evaluation of InterLIR Services for IPv4 Acquisition

Application: Defining the InterLIR Recipient and Source Request Workflow

Submitting a Recipient request at Interlir.com starts the process for buyers, while sellers initiate a Source request. This division aligns IPv4 verification with the specific role each party occupies. Buyers lacking existing allocations must prepare a detailed usage plan for submission within 24 months, a regulatory window allowing new entrants to secure space before full deployment.

Workflow paths diverge based on asset ownership and counterparty status:

• Existing holders provide evidence of compliance regarding past delegations before approval.
• Organizations lacking prior resources apply the post-transfer period to demonstrate immediate need.
• Buyers with a confirmed seller obtain transfer pre-approval to accelerate the final exchange.
• Sellers verify registration data accuracy to prevent audit stagnation.

Operators often overlook that pre-validating eligibility prevents deal stagnation during the audit phase. InterLIR enables connections, yet the administrative burden of proving authentic holder status remains a strict requirement. Delays frequently occur when sellers fail to verify registration data accuracy before engaging a potential buyer. Parties must verify their registration information is accurate prior to submission to ensure alignment with regional registry records.

Application: Applying the 24-Month Usage Plan for New Entrant Buyers

Organizations entering the market without prior holdings apply a mandated 24-month window to demonstrate detailed usage plans. This regulatory structure shifts the compliance burden from transaction initiation to post-transfer verification, allowing new Local Internet Registries to secure IPv4 blocks before full infrastructure deployment. Operators must submit a Recipient request at Interlir.com to begin this process, ensuring the authentic holder status is validated against the source account without disputes. The primary analytical insight here is that while this timeline accelerates market entry, it creates a strict utilization deadline where recipients must demonstrate a detailed plan for the use of the transferred resource within the specified period.

Key operational steps for new entrants include:

• Submitting the request via Interlir.com to establish buyer intent.
• Drafting a thorough technical roadmap for network integration within the two-year period.
• Ensuring recipient status as a current APNIC account holder to satisfy registry agreements.
• Tracking deployment milestones against the 24-month clock.
• Preparing documentation for the final usage report submission.

The cost of this flexibility is the requirement for rigorous internal tracking to prove actual network usage before the window closes. Unlike standard allocations where need is proven upfront, this model demands that operators treat the acquisition date as the start of a critical deployment countdown. InterLIR enables this by verifying registration data accuracy early, preventing delays when the final usage report becomes due.

Validation Checklist for Historical IPv4 and Registration Accuracy

Verifying registration data accuracy prevents immediate transaction rejection during the APNIC audit phase. Operators must confirm the authentic holder matches the source account without disputes before engaging InterLIR services. A critical constraint involves the 103/8 free pool, where addresses delegated less than five years ago remain restricted from transfer to prevent speculation.

• Validate that current LIR status remains active for both parties within the region.
• Confirm historical resources lack the agreements if transferring from legacy holdings.
• Ensure recipients without prior holdings prepare a usage plan for submission within the mandated window.
• Review compliance evidence regarding past delegation policies for existing resource holders.
• Check delegation dates against the five-year moratorium for free pool assets.

The registry offers flexibility for new entrants, yet the five-year moratorium on specific free pool assets creates a hard barrier for recent delegates attempting to liquidate. This tension between asset liquidity and policy protection means operators holding recently delegated blocks cannot apply the market for redistribution until the time lock expires. Consequently, buyers must scrutinize delegation dates alongside ownership records to avoid wasted due diligence on ineligible blocks. Submit a Recipient request at Interlir.com only after confirming these structural constraints allow the transaction to proceed.

Frequently Asked Questions

Can I sell IPv4 addresses taken from the 103/8 free pool immediately?

No, you cannot sell these addresses immediately because a mandatory lock exists. Blocks from the 103/8 free pool face a transfer restriction for five years after delegation to prevent premature market entry.

Which regions allow cross-border IPv4 transfers with APNIC members today?

Transfers are only permitted with three specific counterpart regions globally. APNIC currently recognizes inter-RIR transfers exclusively with RIPE NCC, ARIN, and LACNIC, blocking transactions with other regions like AfriNIC.

What proof do new entrants need to get their first IPv4 block?

New recipients must submit a detailed usage plan covering a specific timeframe. Organizations without prior holdings must demonstrate a plan for using the transferred resource within 24 months to justify the request.

How do legacy holders without APNIC accounts transfer their historical addresses?

Legacy holders must use a specific email template instead of standard market forms. This distinct process integrates historical IPv4 resources from non-account holders into current member accounts while maintaining registry accuracy.

What happens if my organization fails the compliance check on past delegations?

The new transfer request will be blocked until you prove past compliance. Recipients already holding resources must provide evidence of adhering to APNIC policies regarding previous delegations before approval occurs.