RIPE Temporary Transfer: Route IPv4 Without Buying

By Savvas Bout, Founder of Prefixx. Last updated 12 November 2026.

RIPE temporary transfers allow you to permanently route IPv4 addresses that you don’t own while only paying for the time that you need them. With the RIPE NCC’s free pool of IPv4 addresses having closed years ago, buying a block of IPv4 addresses to own them outright can cost a lot of capital to use only for a short time, i.e. for a product launch, for a temporary increase in traffic during a season, or for a short migration period.

Organizations can structure their usage on a monthly basis to align costs with actual resource consumption during these temporary deployment windows.

Even though temporary transfers are a real and RIPE-sanctioned way to temporarily use to transfer IPv4 addresses. There are certain conditions and time limits as well as a number of ripe policy rules tied to an organisation's business structure regarding who is eligible to use them that can often surprise the first engineer who tries to use them. These eligibility requirements reflect needs based policies that govern how address space can be allocated and used within the registry framework.

This article describes RIPE NCC member temporary transfers in detail, explains the key differences between a RIPE interim transfer and a lease. Describes step by step the process of a temporary transfer complete with an explanation of where partial blocks usually cause the process to get stuck.

It also explains where RIPE temporary transfers are used in the IPv4 acquisition process and compares them to short-term transfers, leases and purchases of IPv4 address space. Understanding these distinctions helps organizations determine whether a temporary transfer, lease, or outright acquisition best aligns with their operational requirements and budget constraints.

What is a RIPE temporary transfer and why it does not exist as policy

The RIPE NCC does not have a formal mechanism for a temporary transfer of internet number resources. All transfers of internet number resources within the RIPE NCC service region are permanent, i.e. the registration record(s) change and legal custody of the resources is transferred.

Transferring internet number resources and how it works

The transfer of internet number resources between registered holders is recorded in the RIPE policy registry. There is no time limit for expiry of transferred resources, no reversal of those resources, and no way for a block of numbers to be returned to its original holder. The registry also tracks changes in resource holder status that may result from corporate restructuring or further mergers between organizations.

Leases are not inter RIR transfers of internet number resources

Leases do not change the Resource Holder. The original registrant is the owner of that resource within their service region. This means that even when one member leases address space to another entity, the registry records continue to reflect the original holder as the resource owner.

What drives the regional internet registry misconception

Resources transferred via Internet number resources are not to be confused with temporary assignments from the RIPE NCC’s older pools of direct assignments (as opposed to transfers via the service region). On every transaction Prefixx consultants for Prefixx negotiations for the service region thoroughly explain the differences and how a permanent transfer of resources is dealt with under RIPE policies. Understanding these distinctions ensures that parties structure their agreements in compliance with relevant policies governing resource transfers in the service region.

Transferring internet number resources under ripe policy

Intra-RIR transfers within the RIPE NCC service region follow a fixed process.

Who qualifies as a RIPE NCC member in the service region

An offering party and a receiving party must both be either a RIPE NCC member (an LIR) or an end user with allocated PI space held under sponsorship by an LIR. Without this link the sponsoring LIR must establish the necessary contractual tie. The end user must maintain this sponsorship arrangement throughout the duration of the transfer process and afterward.

Submitting the transfer agreement to a regional internet registry

The agreement is signed by both parties and a joint transfer request for complete or partial blocks is submitted to the RIPE NCC portal. This also applies to already allocated resources as well as to legacy space. After checking the eligibility of the parties the RIPE NCC then checks if the registration records are up to date and approves the request. When submitting partial blocks, the registry verifies that each subdivided prefix meets minimum allocation size requirements and aligns with CIDR boundaries.

How the RIPE database reflects regional service changes

After approval, the registry updates the RIPE database to reflect the new resource holder, including the updated routing objects and corresponding RPKI ROAs.

These have to be updated separately from the registry update and are managed by Prefixx as part of the transaction process on behalf of the receiving party. In addition to the registry process, the acquiring organization also becomes responsible for a number of issues related to RPKI and routing within its own service region that should be well understood before the transaction occurs.

What happens to end users in the RIPE NCC service region during a transfer

Transferring a resource at RIPE NCC affects more than just the routing information of that resource. Each resource received must be documented in the registry to reflect the change in holder and maintain accurate allocation records.

What the end user and parties involved must document

1. Organisational eligibility needs to be confirmed. The business structure of an organisation needs to be verifiable. As a rule, a copy of the registration documents for the legal entity in question is required by RIPE NCC. For mergers and acquisitions, proof needs to be provided that links the new legal entity to the original resource holder.
2. Submit the transfer request. The current holder of the resources initiates the transfer via the RIPE NCC portal. Both parties need to authenticate and accept the terms of the transfer before the registry can process it.

Note: Approved changes to legal name or ownership do not automatically transfer resources. A separate registry process is required even when the underlying network stays identical. The registry process ensures that all parties involved formally acknowledge the change in resource holder status.

Legacy resource transfers and receiving party restrictions

The RIPE NCC policies regarding legacy resources within the transfer framework of the RIPE NCC follow the same documentation path as for new resources. Resources with legacy status follow this identical documentation path when entering the transfer framework at RIPE NCC. The ripe policy framework treats legacy resources identically to other address space once they enter the transfer system, ensuring consistent documentation requirements across all resource types.

A block of inventory is considered legacy, but does not get a free pass on post-transfer restrictions. It is bound by the same 24-month holding period as any other block of transferred inventory. The holding period ensures that resources remain stable within the registry for at least five years from the date of any prior transfer.

How Prefixx handles your transferred resources and business structure

We prepare the LOA, RPKI ROA and IRR route objects. We check all blocks before they are sold to a customer. Most errors in the documentation for the registry review can be eliminated by this check. In addition, organizations that only need a partial block derived from a larger address space for a limited time can lease it instead of having to go through a full transfer of ownership.

Leasing IPv4 addresses as the practical alternative to a temporary transfer

RIPE NCC does not allow temporary transfers. The original holder of the IP addresses would remain the current resource holder on record, and you would use them whilst you operate them as if they were your own. The receiving RIR verifies that all documentation confirms a permanent change of holder before updating its registry to reflect the new allocation.

How registration and routing split under a lease

The resource holder keeps the assigned block of address space registered in the RIPE NCC database. A transfer agreement is signed by both parties to a transaction and the lessee is then authorized to announce the assigned prefix. The resource holder retains full registry authority over the block throughout the lease period. The ripe database maintains these registration records to ensure that routing announcements can be validated against the documented resource holder throughout the lease arrangement.

This distinction is significant for independent resources, which cannot be immediately transferred into PI space or legacy blocks, but can be leased by another network and then announced. Independent resources that were previously allocated under a different policy framework retain their original classification during such arrangements.

What "resource originally held" means for routing paperwork

Because the original resource(s) held by the lessor as the offering party never change registry ownership, the LOA and ROA must refer to the Lessee's ASN in their respective policy documents. The registry continues to list the original block under the lessor's account throughout the lease period.

Inter RIR non-revocation and provisioning for IPv4 addresses

Leases at Prefixx come with a non-revocation guarantee for complete or partial blocks, meaning the announced block will remain announced for the entire duration of the lease. Provisioning of all required services will occur within 24 hours of LOA issuance, and the client will receive white-glove service to correct geolocation, reverse DNS, and reputation issues throughout the lease term. However, if a requirement spans multiple registry regions (i.e. is not confined to a single RIR), an inter-RIR transfer may be a better option.

Why Prefixx serves the RIPE NCC service region for transfers and leasing

Prefixx is a registered broker with ARIN, RIPE NCC and APNIC. Prefixx can complete intra-RIR and inter-RIR IP number transfers from the signing of a transfer agreement to the completion of all necessary routing configuration. The team handles all parts of the process for all involved parties, including RIPE NCC member obligations and PI/ASN holder sponsoring as a LIR.

• We apply Tixx quality control to every single block before we transfer ownership, check for blacklists, verify routing and last but not least check RIR information.
• Escrow-secured transactions, zero buyer fees, seller-only commission.
• White-glove LOA, RPKI ROA and IRR preparation included.
• RIPE LIR sponsorship service for independent resource holders.
• BYOIP deployment support onto Netrouting bare metal.

Talk to one of our consultants about the IP address space you need, or to get a quote for a transfer.

We do not offer temporary transfers. All transfers under the RIPE NCC's policies are permanent and include full registration of the transferred objects to the new holder.

A lease provides you with temporary, routable space that includes legacy resources covered by RPKI as RIPE policies mandate, and the space reverts to the lessor of the registered space at the end of the term of the lease. Cross-registry transfers (i.e. between ARIN, the RIPE community via RIPE NCC, and APNIC) are supported but each of the RIRs have their own processes and time frames for such approval.

If you need address space for a defined period, or you are evaluating a permanent acquisition against a lease, Prefixx can walk you through both paths. Every block goes through Tixx quality control before it reaches you, and white-glove routing paperwork with a transfer agreement signed is included. Get in touch with the Prefixx team to discuss what your situation actually requires.