An Inter-RIR transfer moves IPv4 address space from an organization registered with one Regional Internet Registry to an organization registered with another. The source organization begins the transfer with its current RIR. After the source side is approved, that RIR coordinates with the recipient’s RIR, which reviews the buyer and confirms that it qualifies to receive the addresses. Once both registries approve the transaction, they coordinate the registry updates so the IPv4 block is registered to the new holder.

ARIN, APNIC, RIPE NCC, and LACNIC currently support Inter-RIR IPv4 transfers with compatible RIRs. This allows qualifying IPv4 address space to move between North America, the Asia Pacific region, Europe and surrounding regions, and Latin America and the Caribbean. AFRINIC ratified a policy allowing Inter-RIR transfers in February 2026, but implementation is still underway. As of August 2026, AFRINIC’s operational transfer guidance continues to cover intra-regional transfers rather than standard Inter-RIR transactions.

Both registries are involved. The source RIR determines whether the seller and IPv4 block are eligible to leave its registry, while the recipient RIR evaluates whether the buyer qualifies to receive the space. This means a transfer must satisfy requirements on both sides of the transaction. Holding periods, account status, resource history, documentation, and other source requirements can affect the seller, while IPv4 justification and recipient eligibility are generally determined by the buyer’s RIR.

In most cases, yes. The exact test depends on the recipient’s RIR. ARIN evaluates projected IPv4 need over a period of up to 24 months, APNIC requires recipients to justify their need for transferred resources, and LACNIC requires the recipient to demonstrate how the IPv4 space will be used. RIPE NCC normally does not use a needs test for transfers within its own region, but when addresses are transferred into RIPE from an RIR that requires needs-based transfers, the recipient must provide a plan showing use of at least 50% of the transferred resources within five years.

There is no standard completion time for every Inter-RIR transfer. These transactions involve reviews by two separate registries, so they can take longer than a transfer that stays within a single RIR. The source RIR generally reviews the seller first and then sends the approved request to the recipient’s RIR. The receiving registry reviews the buyer, requests any required justification or documents, and issues its approval. The two RIRs then coordinate the final registry update. Pre-approval, accurate organization records, and complete documentation can help avoid unnecessary delays.

Fees and transfer restrictions depend on the RIRs involved. ARIN currently charges a $500 source transfer request fee when the seller is in the ARIN region, and ARIN recipients pay a processing fee based on the amount of IPv4 space received. APNIC charges a transfer fee equal to 20% of the annual fee applicable to the transferred resources, with the responsible party depending on whether the transfer is inbound or outbound. LACNIC applies an administrative transfer fee based on block size, while RIPE NCC does not charge a separate per-transfer fee.

Restrictions also vary by registry. RIPE IPv4 resources generally cannot be transferred again for 24 months after they are received. LACNIC addresses that have already been transferred generally have a one-year re-transfer restriction, while addresses originally allocated or assigned by LACNIC have a separate three-year restriction. APNIC IPv4 space originally delegated from its 103/8 free pool cannot be transferred for five years from the original delegation date. ARIN applies source eligibility restrictions that can also affect when an organization is able to transfer IPv4 space.