IPv4 Transfer Timeline: What Affects How Long It Takes

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

How long does it take to complete an IPv4 transfer?

The ‘cleanity’ of the IP addresses’ history and the readiness of both parties to complete the required paperwork. One missed field on an ARIN 8.3 request or a RIPE NCC due-diligence review and the clock is reset. Ensuring that all parties involved have verified their contact information and organizational records before submission eliminates the most common source of administrative delays.

For individuals looking to add a new subnet to their network, to move a data center to a new facility, or to bring a block of IP addresses into the cloud as part of a BYOIP initiative that may involve inter RIR transfers, the uncertainty inherent in the process can translate into real cost. Organizations should clarify their lease terms early in the planning process to avoid misalignment with transfer timelines.

In this article we will look at the typical timeline to assign IP address space at the RIRs (ARIN, RIPE NCC, APNIC, and LACNIC), highlight the individual steps that can add days to weeks to the process, and detail the differing timeframes for same-RIR and inter-RIR transfers. The complexity increases substantially for inter RIR moves, where policy alignment between registries and additional coordination steps can extend timelines beyond what most organizations anticipate.

Most importantly, we'll outline the steps you can take to ensure your block closes quickly, having a clean routing history and complete documentation for your assigned IP address space.

How long does an IPv4 transfer take from start to finish

Intra-RIR transfers of IPv4 addresses typically take one to three weeks.

There are 4 variables that affect the time needed for an IPv4 transfer: the RIR that is responsible for the block of IP addresses in question, whether the transfer is within one RIR or across multiple RIRs, how fast the source of the IP addresses can produce required documentation in proper format, and whether there are restrictions on the transfer of specific IP addresses. The size and contiguity of the IP range being transferred can also influence processing speed at certain registries.

What a regional internet registry actually controls

Each block of IPv4 addresses is maintained by one registry. That registry sets up the eligibility criteria, the requirements for justifying needs (as stipulated by the registry's policy), and the pre approval queue for transfer applications. For example, the American Registry for Internet Numbers (ARIN) requires proof of need before approving a transfer of IP addresses.

In contrast, the RIPE NCC operates with a much more simple first-come first-serve policy. The american registry maintains detailed records of all resource holders within its service region and enforces its need-based transfer policy through a structured pre-approval process.

The fastest way to conclude a transfer is to stay within the service area of one single registry. Organizations seeking to minimize transfer duration should prioritize intra RIR transfers whenever their network expansion plans permit sourcing addresses from the same regional registry.

Intra-rir versus inter RIR transfers explained

These intra RIR transfers typically take 5 business days or less to close, provided the domain has clean history and the block in question is eligible for transfer.

Specified recipients and documentation readiness

Most registries require the from and to names to be specified in the transfer request. Missing or outdated WHOIS information for a domain, unresolved legacy RSA information for a reseller account, or if a piece of space is blacklisted can all cause a domain to stall in the transfer market queue. We catch most of this in documentation review before the request is even submitted.

• Clean WHOIS and up-to-date contact records.
• Signed transfer agreements between both parties.
• Letter of Offer prepared and submitted prior to the request window opening.

This basic information, which requires no pre approval to understand, helps to explain what a transfer of a domain name actually means at the level of a registry, before going into the details of the respective timetables of all RIRs.

What it means to complete an IPv4 transfer

A transfer of internet number resources is not a routing event but rather an administrative event that gets recorded within the RIR registration systems. Until the registry has updated the records the source organization is still the accountable resource holder for the announced prefix, even if it is announced by a different organization by BGP. The registry must complete the full transfer of administrative control before the receiving organization becomes the official holder of record.

How to transfer internet number resources and pay the transfer fee

Transferring of IP addresses from a sender to a receiver is done by completing a registry transfer process of a RIR. Both sender and receiver fill out required documentation, the RIR handles pre approval by verifying the eligibility of both parties, and after that the WHOIS database is updated with the new holder of the IP addresses.

Then the transfer is completed legally. The registry's role in this process is to verify the legitimacy of the address distribution and ensure that the updated records accurately reflect the change in resource holder.

Registration records vs. Routing: why the distinction matters

Changes to routing address blocks occur in minutes (or even seconds), whereas those who request resources through registration may wait days to weeks, depending on the RIR and the degree to which all required paperwork has been completed.

Which registries support transfers of address space

IPv4 space can be transferred from one organization to another, including legacy Internet space.

We handle transfer paperwork for all 5 registries, with transfer processing times for intra-RIR moves detailed in the following section.

Intra-rir transfers: timelines within a single registry

Intra-RIR transfers are movements of address space between two organizations within the same registry.

ARIN: pre-approval and account requirements

ARIN pre-approval requires the recipient organization to hold an active ARIN account and complete pre-approval for the block size requested prior to submission of the transfer request.

1. Create a new ARIN Online account or verify that you already have an account and accept the registration services agreement.
2. Submit a needs-justification request. The request will go through ARIN for review of your proposed utilization and current holdings.
3. After receiving pre-approval, the source of the IP addresses initiates the transfer on ARIN Online. Both parties to the transaction must confirm the transfer.
4. This request is reviewed by ARIN staff. Processing of complete requests typically takes two to four weeks.

Note: Missing or outdated contact records on either side are the most common delay. Verify both organizations' POC records before submitting.

RIPE NCC IPv4 transfer agreement and direct allocations

To do a RIPE NCC transfer, both parties need to have active LIR accounts.

1. Both organizations agree to the transfer by signing a transfer agreement in the RIPE NCC portal.
2. RIPE NCC checks if resources are eligible and the status of the LIR. Processing time is about 3 to 5 business days.

Note: Blocks under a 24-month holding lock after a previous transfer are ineligible until the lock expires.

APNIC region: asset purchase agreement and WHOIS database updates

Both buyer and seller must be current APNIC members in good standing, and a signed asset purchase agreement is required.

1. Both parties submit a transfer request via MyAPNIC, with a copy of signed agreement attached.
2. We verify eligibility and update the APNIC WHOIS database within 5-10 business days after approval.

Note: APNIC requires the recipient to demonstrate a plan for use within 24 months. Incomplete justification is the leading cause of delays.

When the source and destination for the transfer are in different registries, an additional approval step is required. Inter-RIR transfers are therefore quite different from intra-RIR transfers listed above.

Inter-rir transfers: what changes when IPv4 addresses cross registries

Inter-RIR RIR transfers of address space involve two separate registries, each with its own policies. These cross region transfers require coordination between the administrative procedures of both registries.

How the dual-approval mechanism works

Both the sending RIR and receiving RIR must approve the request. The sending RIR verifies the applicant’s ownership of and eligibility for transfer of the IP addresses. The receiving RIR verifies that the recipient(s) meet(s) the needs-assessment criteria of that RIR. This dual-approval structure introduces a further layer of administrative overhead compared to intra-RIR transactions.

Our transfer process is set up to run two sequential reviews.

Compatible policies and specified recipients

Today’s live corridors include ARIN-to-RIPE NCC, ARIN-to-APNIC, and RIPE NCC-to-APNIC. LACNIC facilitated transfers rather than native policy. So each of these corridors requires corresponding policy on both ends of the corridor. That means that for example RIPE NCC needs to have formally adopted inter-RIR transfer policy within their own environment before the corridor can open. The corridor framework ensures that inter RIR transfers maintain consistent policy enforcement across both the source and destination registries throughout the entire process.

ARIN's Policy 8.3 covers outbound IP addresses, such as those from an APNIC account holder with organizations in the ARIN region, and lists specified recipients that must qualify under the policy's eligibility criteria.

Transfer fee restrictions and documentation requirements

Transfer restrictions for IP number ports vary by region, and areas such as Latin America impose distinct requirements on both source and destination organizations involved in the transaction.

Inter-RIR inbound transfers do not get placed on the ARIN waiting list for space. Therefore, for example, blocks moved in from other registries across the world can be acquired by an organization for use within ARIN's region through the transfer market, providing one of several reasons organizations pursue cross-registry acquisitions.

Prefixx deals with the full set of documents necessary for PEering handshakes. We take care of contacting the sending and receiving registries, setting up the LOA, RPKI ROA and IRR objects necessary for approval, and tracking the approval process for each of the documents necessary.

When transferring resources between regions within a single RIR (intra-RIR), or between different RIRs (inter-RIR), the same variables influence whether the transferred resources are processed quickly, within a few days, or whether the transfer takes longer to complete, in weeks.

Key IPv4 transfer market factors that determine transfer time

While delays in inter RIR transfers are caused by many factors, such as documentation gaps, the impact of other variables, like registry queue depth, block size and routing setup, will either increase or decrease depending on how good the initial documentation was.

Documentation and entity eligibility for transferred IP resources

To initiate a transfer of IP numbers, a complete transfer request is required: an asset purchase agreement, a registration services agreement, and an exact matching org id for the receiving organization as specified in their RIR record.

The recipient entity must also fulfill any needs-assessment or membership requirements of the registry, ARIN requires utilization justification for a transfer, RIPE NCC requires membership with active status for the recipient entity.

Block characteristics and regional internet registry workload

Blocks with legacy status are subject to different policies than newly allocated space.

Even small blocks get special treatment, in particular those that are close to the minimum transfer size.

Routing readiness and payment timing

Many parties fail to think of the routing aspect during a transfer.

Deliberate sequencing of escrow release and RIR submission is required in any transfer market transaction to avoid submitting the RIR prior to funds clearing and to avoid releasing escrow before the registry confirms that the transferred resources have been recorded. Our team works to coordinate both tracks in parallel in order to keep the timeline as tight as possible. In the case of blocks with compatible policies at registries, inter-RIR moves can be transferred faster than intra-RIR moves.

RIR approval is not the end of the road.

Why choose Prefixx for your IPv4 transfer needs

Prefixx is a registered IPv4 broker with ARIN, RIPE NCC and APNIC, LACNIC facilitated. All IPv4 transfers are processed through a structured process to ensure that all parties (source organization, recipient organization and relevant regional internet registry) are aligned from the outset.

• Tixx quality control: verify ownership, transfer eligibility, black lists and routing health before agreeing to transfer documentation. Catch any documentation surprises that others find when trying to process your RIR transfer.
• We prepare all the white-glove routing paperwork for you, such as LOA, RPKI ROA and IRR route objects so you can announce your new registered address space right away.
• Inter-RIR transfer support. We support both intra-RIR and inter-RIR transfers. That means we support transfers between organizations operating within a single RIR as well as transfers between organizations in different RIRs (e.g. between ARIN, RIPE NCC and APNIC).
• We offer escrow-secured transactions with zero buyer fees. Funds are held in escrow until the buyer receives confirmation that their funds have been transferred in full. There are no broker fees for the buyer.

If you’re looking for a clean and well-documented process for an IPv4 transfer, get in touch with the team at Prefixx.net and we’ll be happy to discuss your address space requirements.

Frequently asked questions

How do intra-rir transfer market timelines compare to inter-rir ones in duration?

An intra-RIR transfer, where both parties are in the same registry, typically completes in one to three weeks once all documentation is submitted and approved. An inter-RIR transfer, moving space between two different registries such as ARIN and RIPE NCC, adds coordination steps between both registries and commonly runs four to eight weeks or longer.

With intra RIR transfers, the source registry must approve the transfer out before the destination registry can process the transfer in, which is where most of the additional time accumulates. Clean documentation and a block that passes pre-transfer quality checks are the single biggest factors in keeping either timeline short.

What documents are needed to submit inter RIR transfers between ARIN and RIPE NCC?

For ARIN, you need a signed transfer agreement between buyer and seller, proof of the seller's right to transfer the block, and a needs-justification statement from the recipient demonstrating they meet ARIN's utilization requirements. For RIPE NCC, both parties must hold active LIR or End User accounts, and the transfer is executed through the RIPE Database with supporting contractual evidence.

In both cases, any discrepancy in registration records, such as a stale WHOIS contact or an unresolved abuse flag, will pause the process until it is resolved.

Are inter RIR transfers possible for IPv4 addresses with legacy status?

Yes. Under ARIN, legacy holders can transfer space to a recipient organization without first signing a Legacy RSA, though signing one brings the block under standard policy and simplifies future transactions.

Under RIPE NCC, legacy space is transferable provided the holder has a valid contractual relationship with the registry. The key practical point is that legacy blocks sometimes carry older, incomplete registration records, which adds a pre approval verification step and can extend the timeline by several days.

What minimum IPv4 address block sizes apply to inter-rir transfers?

ARIN's minimum transferable block is a /24 (256 addresses). RIPE NCC also enforces a /24 minimum for transfers. LACNIC requires a minimum of a /24 for transfers it facilitates. These minimums apply to the block being transferred as a unit; you cannot split a /24 into smaller pieces and transfer each fragment separately through the standard transfer process.

Do inter RIR transfers of IPv4 addresses require ARIN pre-approval before buying?

Yes, for specified transfers under ARIN's needs-based policy, the recipient must receive a Needs Assessment approval from ARIN before the transfer can be registered.

Skipping this step means the transfer request will be rejected outright, not just delayed.

How long after a transfer market deal before geolocation databases update

The major geolocation providers, including MaxMind, IP2Location, DB-IP and ipinfo.io, refresh their data on cycles ranging from a few days to several weeks after a registry change for a recipient organization receives pre approval and is published.

Without a geofeed, providers rely on WHOIS and routing data alone, which means some databases may show the old location for a month or more. Prefixx publishes a daily geofeed for clients and submits it to the major internet resources and providers as part of its white-glove service, which is the fastest reliable path to accurate geolocation after a transfer.

What are the RIR fees for an IPv4 transfer?

Each RIR charges its own administrative fees for processing a transfer, and those fees are set by the registry, not by any broker. ARIN, RIPE NCC and APNIC all publish their current fee schedules on their respective websites, and the amounts vary by block size and membership status.

These registry fees are separate from any brokerage commission and are typically the responsibility of one or both parties as agreed in the transfer contract. For the most current figures, check the fee schedule directly on the relevant RIR's site, since registry fees in the transfer market are updated periodically and any number stated here could be out of date by the time you read it.

The timing of IPv4 transfer of IP address space is mostly dependent on 3 things: the registry or registrar you are working with to complete the transfer, whether the transfer crosses a registry boundary, and how complete and accurate your documentation is on the first day. Completing all of the necessary paperwork with your current RIR can take as little as a few days to complete the transfer.

Transfers of IP address space between different RIRs, on the other hand, can add significant time to complete the transfer due to additional policy based review of the proposed transfer. Space with unresolved blocklist entries, IRR inconsistencies, or missing LOA(s) will generally stall at the first review step of the proposed transfer.

Getting that groundwork right before you submit is the single biggest lever you control. Prefixx handles exactly that: Tixx quality control flags issues before a block ever enters the transfer pipeline. Additionally, The white-glove team prepares your LOA, RPKI ROAs, and IRR route objects so nothing comes back for corrections. If you have a transfer coming up, reach out to Prefixx before you file, not after.