RIPE NCC does not publish a fixed completion time for standard IPv4 transfers. Once the seller submits the request and all supporting documents are available, RIPE NCC reviews the transfer, verifies the parties, and checks that the addresses are eligible to move. Straightforward transfers can move quickly once the paperwork is complete, while missing corporate documents, questions about signing authority, or other due diligence can add time. Inter-RIR transfers usually take longer because RIPE NCC must coordinate the approval and registry update with another Regional Internet Registry.

For a standard IPv4 transfer between parties in the RIPE NCC service region, the recipient does not have to pass the type of needs-based utilization test used by some other RIRs. This gives RIPE buyers more flexibility when acquiring IPv4 space. A needs plan can still become relevant in an inter-RIR transfer. If the originating RIR requires needs-based review, RIPE NCC requires the recipient to provide a plan showing use of at least 50% of the transferred resources within five years.

For a standard transfer, RIPE NCC requires recent official registration documents for the organizations involved, a Transfer Agreement signed by both parties, and evidence that the people signing the agreement are legally authorized to act for those organizations. If the recipient is an End User rather than an LIR, an End User Assignment Agreement with a sponsoring LIR is also required. RIPE NCC may request additional information when it needs to verify ownership, authority, or other details connected with the transfer.

RIPE NCC does not currently charge a separate fee for an IPv4 resource transfer. However, that does not mean there are no registry-related costs for the recipient. IPv4 allocations generally need to be held through a RIPE NCC member account, and membership or sponsorship fees can apply depending on the type of resource and how it will be registered. These costs are separate from the price paid to purchase the IPv4 addresses or any broker, escrow, or transaction expenses.

IPv4 addresses subject to RIPE’s transfer policy generally cannot be transferred again for 24 months after the current holder receives them. The restriction also applies when IPv4 resources are received following certain changes in business structure, such as a merger or acquisition. A further merger or acquisition can be an exception to that restriction. Before buying or selling RIPE IPv4 space, it is important to check the block’s transfer history to make sure the 24-month period has expired.

It depends on the type of IPv4 resource being transferred. A standard IPv4 allocation must be transferred to a RIPE NCC member, commonly called a Local Internet Registry or LIR. Provider Independent (PI) IPv4 space can be transferred to a RIPE NCC member or to an End User that has the required contractual relationship through a sponsoring LIR. Legacy IPv4 resources have separate rules and may not require the recipient to become a RIPE NCC member.