Skip to content
Fresh IPv4 news just dropped — 🎉 see what you’re missing

Inter-RIR IPv4 Transfers: Eligibility and Handover

An inter-RIR IPv4 transfer moves resource registration from one regional registry to another. Both RIRs must accept the route and approve their respective side. The source’s restrictions apply before completion; the receiving RIR’s policies govern the resource after the registry handover.

Supported IPv4 routes

Source / recipientRIPE NCCARINAPNICLACNICAFRINIC
RIPE NCCIntra-RIRSupportedSupportedSupportedNo implemented route
ARINSupportedIntra-RIRSupportedSupportedNo implemented route
APNICSupportedSupportedIntra-RIRSupportedNo implemented route
LACNICSupportedSupportedSupportedIntra-RIRNo implemented route
AFRINICNo implemented routeNo implemented routeNo implemented routeNo implemented routeIntra-RIR

IPv4 policy snapshot checked 8 November 2026 against the registries’ published transfer guidance. “Supported” describes policy compatibility, not approval of a specific block, organization or NIR procedure. Do not reuse this matrix for IPv6 or ASNs.

The RIPE NCC inter-RIR guidance documents its supported counterparts, resource types and receiving requirements. Account for national-registry steps where either party holds resources through an NIR.

Which recipient needs test applies?

Receiving registryPreparation
RIPE NCCFor arrivals from a region requiring compatible needs-based policy, document use of at least 50% within five years
ARINApply NRPM 8.5, including the initial-block rule and the relevant utilization route
APNICPrepare a detailed 24-month use plan and previous-use evidence where applicable
LACNICDemonstrate initial or additional allocation/assignment need under the applicable policy

Use the needs-justification worksheet to make the figures reconcile with current holdings and deployment dates. Approval at the source does not waive recipient assessment.

Establish the route before filing

Confirm the current registry from an authoritative record, not a geolocation result. Record the prefix, holder, resource status and recipient organization. Check the source and resource restrictions, including recent receipts and special-pool history.

The receiving entity must qualify for the destination account and intended resource status. A company incorporated in another country, a new BGP origin or a datacenter move does not itself move registration between RIRs.

Coordinate two registry reviews

The source side establishes authority and eligibility to release the resource. The receiving side establishes recipient eligibility, agreements and resource acceptance. The registries coordinate their approvals and completion; the parties should track both case references and outstanding questions.

Two registries coordinate one registration handoverThe source RIR checks holder authority and resource restrictions. The receiving RIR checks recipient eligibility, need and agreements. Both approvals are required before the coordinated registration handover. The receiving RIR's rules apply after completion. Review order and timing are not represented.REGISTRY / INTER-RIRIPV4.ONLINEBoth approvalsSource RIRReceiving RIRRegistry handoverReceiving RIR rulesSource RIRHolder authorityResource restrictionsReceiving RIRRecipient eligibilityNeed and agreementsRegistry handoverCoordinated record updateReceiving RIR rulesApply after completion
Two registries coordinate one registration handoverThe source RIR checks holder authority and resource restrictions. The receiving RIR checks recipient eligibility, need and agreements. Both approvals are required before the coordinated registration handover. The receiving RIR's rules apply after completion. Review order and timing are not represented.REGISTRY / INTER-RIRIPV4.ONLINEBoth approvalsSource RIRReceiving RIRRegistry handoverReceiving RIR rulesSource RIRHolder authorityResource restrictionsReceiving RIRRecipient eligibilityNeed and agreementsRegistry handoverCoordinated record updateReceiving RIR rulesApply after completion

Both RIRs must approve their respective side before the coordinated registration handover. The destination’s rules govern the resource after completion. This diagram does not prescribe review timing; routing, ROAs, IRR and reverse DNS still need their own operational handover.

View full diagram

Do not treat one approval email as the completed transfer. Preserve the completion notices and verify the new authoritative holder record. A referral or placeholder in the former registry is normal; two independently active holder records are a problem to resolve.

Plan the operational handover separately

Before the completion date, record who will manage the new resource certificate, ROAs, IRR entries and reverse DNS. An inter-RIR transfer can remove source-side objects or services. The origin ASN can remain unchanged, but authorization must be valid under the new holder’s control.

Follow the post-transfer checklist for verification after registration changes. If the resource is legacy space, agree its destination status before filing; legacy treatment is not portable by default.

For an IPv4 acquisition across regions, make completion depend on both registries’ approval and the agreed handover evidence, with routing acceptance tested as a separate milestone.

Frequently asked questions

Can IPv4 resources be transferred to or from AFRINIC through the ordinary inter-RIR process?
The published AFRINIC policy does not implement an inter-RIR route. Its CPM 5.7 covers transfers within the AFRINIC region. Do not treat a proposal or an overseas routing arrangement as an approved inter-RIR transfer.
Does RIPE require a needs plan for an incoming transfer?
For transfers from regions requiring compatible needs-based policies, RIPE requires a plan to use at least 50% of the transferred resources within five years. Its ordinary intra-region transfer rules differ.
Must the origin ASN change when a prefix moves between RIRs?
Not necessarily. The resource holder, registry and route origin are different roles. Preserve or replace the origin as planned, and ensure the new holder’s ROAs and IRR records authorize it.
Last updated on
Transfer policiesNeeds justification