RIPE NCC Transfer Process 2025: Step-by-Step Guide

The RIPE NCC Transfer process lets organisations in the RIPE service region buy, sell, and lease IPv4 address blocks legally and securely. IPv4 exhaustion is permanent now — that’s just reality. So if you run a network, manage IT for a company, or operate an ISP and need more address space, you’ll have to understand how the RIPE NCC Transfer framework works in 2025. This guide walks through the whole procedure, from pre-transfer checks to final registration updates, and covers the documentation both parties need to prepare. Skip that part, and you’ll pay for it in delays.

Understanding the RIPE NCC Transfer Policy in 2025

The RIPE Transfer Policy (RIPE-682 and its successors) governs how IPv4 allocations and assignments move between LIRs, and directly between end-user organisations. What strikes me most about the 2025 version is how deliberately hands-off it stays: technology-neutral, market-driven. No price regulation. No transfer fee from the RIPE NCC beyond standard registration costs. And no limit on how often you can transfer space you’ve received.

A few things every participant should know before starting:

• Eligible parties: Only organisations within the RIPE service region can take part. Transfers happen between LIRs, or from an LIR/end-user to an end-user sponsored by an LIR.
• Minimum prefix size: A /24 is the floor. Anything smaller can’t be registered as a standalone transfer.
• 56-bit organisation requirement: Since the 2021 policy updates, anyone receiving a /22 or smaller must either hold an independent PI assignment or be a new LIR — the point being that the receiving organisation has its own 56-bit resource holder identity.
• Registry integrity: The RIPE NCC reviews each transfer for legitimacy, but it won’t check your commercial terms, your pricing, or whether the contract between the parties actually holds up.

In practice, the RIPE NCC is a registrar of last review, not a deal facilitator. The gap in between — vetting sellers, verifying ownership documents, negotiating competitive pricing — is where marketplaces like IP4 Market operate, before a transaction ever reaches registry review.

RIPE NCC Transfer Process: Step-by-Step Walkthrough

The transfer usually follows six steps, in order:

1. Agreement and due diligence: Buyer and seller settle on the prefix, price, and terms. The buyer should confirm the seller’s legal right to transfer by checking the RIPE Database records for that specific prefix.
2. Contract signing: A written transfer agreement spells out payment conditions, liability for blacklisting history, and who handles cut-over.
3. RIPE NCC transfer ticket: The receiving LIR submits the transfer request through the LIR Portal, referencing the applicable transfer policy and attaching the signed agreement.
4. Registry review: The RIPE NCC checks eligibility, prefix size, and documentation. In 2025, expect a response anywhere from a few business days to two weeks.
5. Registration update: Once approved, the RIPE Database gets amended so the inetnum object reflects the new holder or sponsoring LIR.
6. Post-transfer actions: Update routing (BGP announcements, RPKI ROAs), DNS, WHOIS abuse contacts — and let your upstream providers know who the new authoritative holder is.

Documentation and Eligibility Requirements for Buyers and Sellers

Both sides have paperwork to hand over to the RIPE NCC:

• Seller: Proof of ownership (allocation or assignment record), the signed transfer agreement, and corporate authorisation confirming the signatory actually has authority to sign.
• Buyer: Evidence of LIR status, or an independent PI resource (for /22 or smaller transfers), plus identification of the legal entity receiving the space.
• Both parties: Company registration documents and, where applicable, board resolutions approving the transaction.

Working with an experienced intermediary cuts the friction considerably. IP4 Market, for instance, verifies seller ownership documents up front and coordinates the registry submission — which shortens review cycles and lowers the risk of rejection over incomplete paperwork. Honestly, documentation is the single biggest factor in whether a RIPE NCC Transfer goes smoothly or drags on for weeks.

Common Reasons Transfers Get Rejected (and How to Avoid Them)

The RIPE NCC Routing Registry review team turns down a meaningful share of transfer requests. Most of the time, the cause was avoidable. These are the usual suspects:

• Inconsistent ORG-HANDLE data. The legal name of the receiving organisation in the RIPE Database has to match its official registration documents exactly. A trading name instead of the legal entity, a missing “Ltd” or “B.V.”, an outdated company registration number — any of these will get the request bounced back.
• Unjustified size of the request. Since 2017, the RIPE NCC checks whether the requesting organisation’s infrastructure actually justifies the address space it wants to acquire. If the request looks disproportionate to documented network plans, expect extra questions: growth projections, infrastructure descriptions, the works.
• Incomplete end-user assignment history. Selling a PA (Provider Aggregatable) allocation means proving that every current end-user assignment was properly deregistered or transferred. Leftover legacy assignments are one of the top causes of delay. And delays here aren’t days — they can drag on for weeks.
• Signature and authority problems. The transfer agreement must be signed by someone authorised to represent the company. A missing power of attorney, or a signature from a contact nobody has on file, is an easy rejection to prevent with a bit of preparation.
• Unpaid registry fees or outstanding disputes. Any unresolved billing issue with the RIPE NCC — on either side — freezes the whole process until it’s cleared.

So before you submit anything, run a full internal audit. Confirm the ORG-HANDLE is current, check the resource object status, reconcile every assignment in the database. A marketplace that does pre-transaction due diligence, such as IP4 Market, screens for these problems before the transfer ever reaches the RIPE NCC — which cuts the back-and-forth with the registry to a minimum.

How Long Does a RIPE Transfer Take? Timelines and Costs

Under normal conditions, the registry review for a RIPE NCC transfer takes roughly two to four weeks from submission to approval — assuming the paperwork is complete from the start. In practice, the timeline usually breaks down like this:

1. Due diligence and negotiation: one to three weeks, depending on how responsive the seller is and how the escrow arrangements look.
2. Contract signing and registry submission: a few business days.
3. RIPE NCC review: two to four weeks. Occasionally longer, if the registry asks for clarifications.
4. Database updates and routing configuration: several days after approval.

All told, plan for four to eight weeks end to end. On the cost side, the RIPE NCC charges an administrative transfer fee (currently a few hundred euros, billed to the receiving LIR). But that’s the small part. The dominant cost is the per-address market price, which has historically hovered between roughly €25 and €50 per IPv4 address depending on block size and demand. Escrow services typically charge a percentage-based fee, and professional intermediaries work on commissions or flat transaction fees. Budget for a legal review of the transfer agreement too — especially with blocks above a /22.

Final Thoughts: Completing Your Transfer Securely with a Trusted Marketplace

The RIPE NCC transfer process in 2025 is mature, well-documented, and entirely manageable if you approach it methodically. Success rests on three pillars: clean documentation, realistic justification of your needs, and a counterparty you can actually trust. Given what IPv4 blocks are worth these days, cutting corners on verification or escrow exposes buyers and sellers alike to fraud risk that dwarfs any savings.

Working with an established marketplace removes most of that uncertainty. IP4 Market provides verified sellers, escrow-backed transactions, and hands-on coordination of the RIPE submission — so network engineers and IT managers can focus on integration instead of paperwork. Whether you’re buying your first /22 or liquidating a large portfolio, a trusted platform remains the most reliable way to close the deal securely, on schedule, and at a fair market price.