IPv4 Transfer Holding Period: Rules by Registry

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

One thing to consider when planning an IPv4 acquisition is the transfer holding period .

The major registries all enforce a holding period for IPv4 transfers, but there are big differences between ARIN, RIPE NCC, APNIC, and LACNIC. Organizations transferring resources to or from the american registry must account for its twelve-month restriction when structuring their acquisition timeline.

The holding period affects more than resale timing, it shapes lease terms, BYOIP deployment windows, and the conditions around RIR transfers. Factor in both the holding period for inter-RIR transfers and the time needed to put newly acquired IP addresses into production.

In all cases, there is considerable impact should the holding period have been misconfigured. This article will detail current holding periods for all registries. It will examine holding period impacts for various modes of acquisition and provide a number of best practices to ensure that your plans unfold as scheduled from the time that a transfer is completed.

What is the IPv4 transfer market holding period

A holding period is the time a recipient organization has to wait before it is able to re-transfer recently received IP address space. This rule affects people actively trading IP address space and can result in a later transfer being declared invalid. Organizations must carefully track when they can legally transfer their remaining space to avoid compliance issues.

Why the rule exists for IP addresses

Holding periods for IP address space were introduced by registries to combat address flipping. The intention of transfer restrictions on assigned IP address space was to use IP address space for operational purposes and prevent IP space from becoming a speculative commodity that can be sold at higher value within a very short time frame after acquisition by a recipient. Registries distinguish between direct allocations made to end users for their own networks and transfers intended purely for resale.

This policy is aimed at short-cycle arbitrage situations. In order to ensure that space is used by organizations with real operational needs instead of by intermediaries trying to make a quick profit, each of the relevant regional Internet registries involved in inter RIR transfers locks transferred resources to the recipient for a set period of time. These policies help maintain the integrity of internet resources by ensuring they serve legitimate operational requirements rather than speculative trading purposes.

Who the rule applies to by IP addresses

The holding period obligation binds the recipient of a transfer of IP number space, not the transferor organization. As the restriction only becomes into force after the transfer has taken place and the space has been registered in the name of the recipient. Organizations receiving number resources must therefore track the registration date carefully to avoid compliance issues with subsequent transactions.

How holding periods differ by registry

The window for hold periods is set by each regional internet registry. The RIPE NCC does not currently have a post-transfer waiting period for transferred number spaces. LACNIC and AFRINIC have their own rules for number space held post transfer. Policy variations across these registries reflect the distinct governance approaches adopted in different regions.

The consultants at Prefixx map the correct policy to each IPv4 transfer market deal before closing and inform the recipient of the free transferable date of the address block in question.

Holding period rules across every RIR: ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC

Each registry has its own policies regarding the period of time that must pass before space that has been transferred can be re-transferred. For inter-RIR transfers, the gap between the two sides’ policies must be compatible. Transfers involving recipients in Latin America fall under LACNIC's jurisdiction and must comply with that registry's specific timeline requirements.

ARIN region: the 12-month rule

ARIN’s policy to impose a 12-month holding period for previously transferred numbers before they can be transferred by the new holder (whether to another party within the RIR or to a party in another RIR) applies equally to both inter-RIR and intra-RIR number transfers. Also, there is a waiting list for number resources that a company needs but cannot acquire on the secondary market directly.

RIPE NCC and direct allocations

The ripe policy does not impose a post-transfer holding period for address space, but the address space can only be held by a party with active RIPE NCC membership.

Each member can request a maximum of one /22 from this /8, and such space carries its own transfer restrictions.

APNIC mirrors ARIN space for 12 months before re-transfer.

Similar holding-period restrictions for Autonomous System Numbers (ASNs) apply at the RIR level.

If you're on a tight timeline, RIPE NCC is likely your best starting point. ARIN and APNIC deals require a 12 month holding period built into any resale plan. Organizations pursuing ARIN space should also account for time on the ARIN waiting list before allocation.

Prefixx manages transfer of address space across all 5 RIRs and tracks holding period compliance from day one.

How the holding period affects inter RIR transfers

Transfers between RIRs have a dual-compliance characteristic that is not present with transfers within a single RIR. Both the source registry’s transfer policies (outbound) and the destination registry’s transfer requirements (inbound) apply, and the holding period is determined by the terms of the specific agreement(s) in question. Organizations pursuing cross-registry transactions must account for these dual requirements when planning their acquisition strategy and any subsequent geographic expansion.

Understanding inter-rir policy agreements

ARIN, RIPE NCC, and APNIC have mutually acceptable policies that permit transfer of IP resources between registries. Space held in LACNIC can be facilitated to be transferred to a ripe region or other destination registry, but must be registered under their policies regarding need by the recipient organization. These registries maintain compatible policies that streamline the inter-RIR transfer process for organizations moving resources across regional boundaries.

1. Check if a bilateral agreement is in place. The ARIN-RIPE NCC agreement as well as the ARIN-APNIC agreement are active. Transfers between RIPE NCC and APNIC are also supported. Please check if the agreement is up-to-date before you proceed.
2. Check the source registry’s outbound holding period. There is a 12 month holding period for space issued by ARIN before it can be transferred out. There is a 24 month holding period for space received by the RIPE NCC before it can be transferred out again.
3. Check the incoming requirements of the destination registry. The recipient entity has to fulfill the need-based or justified-use criteria of the destination registry. The requirements for justified use at RIPE NCC and APNIC have to be fulfilled.

How the holding period clock works in inter RIR transfers

Your clock will reset to the holding period at the destination registry and any tenure you had at the source will not carry over.

1. Plan for the reset date. If the recipient plans to resell or re-transfer the space within a reasonable time frame, verify the full holding period of the destination registry from the start date.
2. Document address distribution intent. Check how recipient plans to use allocated space. Vague justification is the most common cause of failure for transfers between RIRs.

Note: Rising transfer volumes have prompted RIPE NCC to scrutinize recipient qualifications more closely. Incomplete documentation delays approval and can restart the review clock entirely.

Prefixx’s process handles the full transfer to your ARIN, RIPE NCC, and APNIC accounts for all LOAs, RPKI ROAs, and IRR route objects needed for the transfer. However, to protect both parties during the transfer period, the asset purchase agreement needs to be structured.

The asset purchase agreement and what it must cover

An IPv4 transfer agreement is more than a formality, its conditions regarding IPv4 addresses must be met between signing and the time the corresponding updates to the registration records at the respective RIR are made.

Core representations the agreement must contain

The source organization must warrant “clean title” i.e.

This category includes blacklist status and routing hygiene.

How the holding period creates timing risk

RIRs only recognize a transfer after they have processed the transfer request and updated their database.

The normal way to solve this problem for transfer of funds is to make the release from escrow pending confirmation by the RIR of the change to the registration records for the domain name and to make the release from escrow triggered by confirmation by the RIR for registration records change and not by the signing of the transfer.

Tixx due diligence as the pre-contract layer

We run Tixx quality control checks on the full transfer process before any block reaches a buyer. This includes ownership verification, transfer verification, blacklisting and full routing verification. We surface any problems with the transfer before you are put into a position to include them in the asset purchase agreement.

We can often catch routing anomalies or even legacy LRSA conflicts in the IP resources at the Tixx stage of the closing process for Clean blocks in any ripe region that close quickly with few post-signing conditions.

However, a clean contract does not necessarily mean a clean budget and it is equally important to scrutinize the fee layers for an IPv4 transfer as one would the terms and conditions in the contract. Clean blocks in other regions follow similar quality control protocols to ensure smooth transfers.

Hidden fees in IPv4 transfers and how to avoid them

Be sure to list all the fees associated with RIR transfers before you sign your letter of intent. That way you will know exactly how your money will be spent and there will be no surprise costs after the holding period.

Hidden fees that catch buyers off guard

The sticker price for a block is a single number. There are many numbers exchanged by both parties before a transfer actually closes.

• RIR fees: Each registry charges an administrative transfer fee. The exact amount depends on the registry and the resource size. These RIR fees are paid directly to the registry, not to a broker.
• LIR account or membership fees: RIPE NCC requires the receiving party to hold an active LIR membership. Annual membership costs are set by the registry and billed separately.
• Escrow and legal costs: Reputable deals route funds through escrow. That service carries its own fee, typically borne by one or both parties depending on the contract.
• Post-transfer routing work: RPKI ROA setup, IRR route-object registration, and LOA issuance are not automatic. Someone has to prepare and submit them.

Broker commission structures

Secondary market commission models vary greatly and in some cases the broker charges both parties to trade, in other cases no commission is charged to neither party and the broker, acting as a resource holder of the block, simply marks up the block price. Our seller-only commission is 3% to 8% of the sale price (smaller blocks of stock are charged a higher commission).

Why current market prices vary by registry

No official pricing is published by ARIN or RIPE NCC. Market price for IP addresses and address space varies based on conditions, block size, and local scarcity. Pricing fluctuations reflect shifts in market demand as organizations compete for scarce IPv4 resources.

A /24 from ARIN can trade at a very different price from an identical size block of space from RIPE NCC in the same month. Further, the process of transferring space between RIRs (i.e. between different registries) can be very complex and take a long time to complete. This adds a further layer of complexity to negotiating IP addresses and space. Buyers seeking to consolidate resources across multiple RIRs should account for these procedural differences when structuring their acquisition timeline.

Our consultants will map out all fee layers for you before signing off on the deal. In addition, our consultants will draft up the LOA, RPKI ROAs and IRR route objects required for transferring your IPv4 addresses as part of closing the transaction. Once you have a clear picture of the costs involved with a transfer, the next important question is how long does the full transfer process take?

Transfer timelines: from signed agreement to updated registration records

The holding period begins when the RIR confirms the transfer, not when the agreement was signed.

The practical sequence for assigning IP addresses

We follow the same steps for every transfer: Tixx QC and due diligence, agreement execution, escrow funding, RIR transfer request submission, registry review, and update of the records. All parties involved need to act quickly at each step of the process. Most slippage is caused by delays in funding the escrow account or by incomplete documentation.

Pre approval requirements for IP number transfers are set by registries. ARIN, for example, requires both source and destination to hold a current RSA or LRSA before a transfer request is approved. Organizations should verify compliance and request resources only after confirming all pre-approval documentation is complete.

For RIPE NCC managed IP numbers, the recipient of the numbers must be a RIPE NCC member with a valid and current service agreement. The recipient of the numbers initiates a transfer object via the RIPE NCC portal and the numbers are registered in the RIPE database once the numbers have been approved by the registry.

Timeline by registry for IP addresses

Steps after the transfer process

Updating the registration does not mean the end. RPKI ROA, IRR route objects, reverse DNS, geolocation correction etc. follow. The original delegation date of the registry entry for the IP range in question will continue to be displayed in the registry and thus affect the holding period.

Prefixx takes care of all post-transfer routing for you as part of the service, ensuring routing is correct before you cut the block. Knowing the timeline of events above is only half the story, choosing the right transfer path in the first place is the other half.

Transferred resources and the holding period: special considerations

The distribution of legacy IPv4 address space predated the RIRs and the formation of the RIR system. Therefore much of this address space was distributed directly by IANA (or its predecessors) or other early Internet organizations outside the transfer market framework, and holders of these blocks typically do not have services agreements with any of the RIRs.

What makes a block "legacy"

These Legacy allocations were made by ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC before they became the recognized authorities to manage Internet number resources.

With no current services agreement in place, the RIR has limited visibility into this block's status.

Signing requirements before the transfer process

ARIN requires a legacy holder to execute a registration services agreement for the block before initiating a transfer. Without one, ARIN cannot verify the source's authority and the transfer will not proceed.

Once signed, the holder of the block of shares can then attempt to have the shares transferred via the transfer market using 8(a) or 8(b) share transfer procedures as applicable, and the holding restriction is then applied in accordance with the receiving party's standard holding periods.

Holding period applicability for IP resources and addresses

Legacy blocks acquired via formal IPv4 transfer are subject to the same 12-month holding period as all other IPv4 address space, irrespective of the legacy status of the underlying resources. The 12-month holding period commences upon completion of the transfer of the legacy block, not upon the date of original allocation of the resources.

Prefixx verifies legacy and RSA status as part of the Tixx quality control prior to listing the block. In order to prevent deals from stalling mid-escrow due to a missing signature, Prefixx verifies this information as well. If you'd like to have one team handle all of these layers of work around your IPv4 addresses and other IP resources, including the final routing of the corresponding paperwork, here is what working with Prefixx would look like.

Key takeaways: IPv4 transfer holding period at a glance

The IPv4 transfer lock period is a recipient-side restriction, not a seller penalty. It exists to stabilize the secondary market by preventing rapid resale of transferred addresses. ARIN enforces a 12-month hold from the original delegation date. RIPE NCC imposes no holding period for intra-RIR transfers, though inter-RIR transfers carry their own compatibility requirements. APNIC and LACNIC apply separate waiting periods tied to membership status and justified need.

The clock starts when the relevant regional internet registry records the transfer and updates domain records. Inter-RIR transfers add complexity: the source organization must confirm transfer eligibility under its own RIR's rules before the recipient organization can proceed. Budget for RIR fees, any legal entity documentation, and broker commission. Understanding these layers up front keeps the entire transfer process on schedule.

Frequently asked questions

Does the entire transfer process reset holding periods when IPv4 moves between RIRs?

Yes, an inter-RIR transfer triggers a fresh holding period at the receiving registry. The destination RIR treats the transferred IPv4 addresses as a new transfer event, so the clock restarts from the date the receiving registry updates its records.

This means a block that already served a holding period under ARIN will face a new restriction window once it lands in the RIPE NCC database, and vice versa. Plan inter-RIR moves with that reset in mind, especially if a follow-on transfer is part of the roadmap.

What if inter RIR transfers of IP addresses are needed before the holding period ends?

The receiving RIR will reject the transfer request until the restriction window closes.

If the business need is urgent, the practical options within the IPv4 transfer market are to restructure the arrangement as a lease rather than a sale, or to wait out the remaining restriction period before submitting the transfer.

Can leasing IPv4 avoid holding periods required for inter RIR transfers instead of buying?

Yes, leasing sidesteps the holding period entirely because no RIR registration change of ownership occurs. The lessor retains the registration record for the IPv4 addresses, and the lessee receives routing rights through an LOA and RPKI ROA without triggering a transfer event.

How does the holding period affect BYOIP deployment timelines?

The holding period itself does not block you from announcing the space via BGP or deploying it through a cloud BYOIP program.

If you acquired a block specifically to bring it into AWS, GCP, Azure, or onto bare metal through a service like Netrouting, you can proceed with BYOIP onboarding immediately after paying any transfer fee and completing the RIR registration update. The routing paperwork, LOA, RPKI ROA, and IRR route objects are independent of the transfer restriction window.

Do legacy IPv4 resources have different holding period rules than standard allocated space?

Legacy resources are subject to the same post-transfer holding period rules as modern allocated space once they enter the transfer system. The distinction matters on the IPv4 transfer market at the point of eligibility: legacy blocks sometimes require additional steps to bring under a registry's transfer policy before the transaction can proceed.

Once the transfer is recorded, the receiving party faces the standard restriction window for that registry. All participating registries, including those handling legacy resources, apply the holding period from the date of the registration update.

When does the holding period clock officially start: at agreement signing or at RIR registration record update?

The clock starts at the RIR registration record update, not at contract signing or escrow close.

Signing a purchase agreement and funding escrow can happen days or weeks before the RIR processes the transfer, so the effective start of the holding period lags behind the commercial close.

RIRs with no post-transfer holding period on available address space

AFRINIC does not currently enforce a post-transfer holding period in the same way ARIN, RIPE NCC, and APNIC do, though its transfer policy framework is less developed and has been subject to governance disputes. ARIN imposes a 12-month restriction, RIPE NCC enforces a 24-month holding period, and APNIC applies a 12-month restriction.

LACNIC's transfer policy is more limited in scope, and Prefixx facilitates rather than registers LACNIC transactions directly. Policy positions at all registries can change, so confirm the current rules with the relevant RIR or with a registered IPv4 transfer market broker before structuring a deal around a specific timeline.

While the holding period may seem like a minor formalism, it is in fact a hard registry rule that can cause delays, failures or even cancellations of a transfer if not respected. The holding period for IPv4 addresses is set by each RIR and must be checked with the specific registry where the resource is registered prior to signing any agreement.

The acquisition agreement must also be non-negotiable and clearly outline the transfer eligibility, holding period and fees.

When transferring between RIRs, the rules of the source registry and the rules of the destination registry must be followed.

If you are planning a transfer and want a team that handles the RIR paperwork, escrow, and Tixx quality checks from start to finish, see how Prefixx runs a deal.