ENTRDEESFRPTIT
All Guides
RIPE NCC Guide

RIPE NCC IPv4 Transfer Guide

RIPE NCC manages the most active IPv4 transfer market in the world. Learn the complete process for transferring IPv4 addresses within or into the RIPE region.

Key Facts

Essential numbers you should know before starting a RIPE NCC transfer.

1–2 Weeks
Typical Timeline
For intra-RIPE transfers
/24 Minimum
Transfer Size
256 IP addresses
$7,000–$9,000
Per /24 Block
Q1 2026 market price
No Needs Test
Transfer Policy
Since RIPE-689 (2014)

Transfer Process

A step-by-step overview of how IPv4 transfers are completed through RIPE NCC.

1

Verify RIPE Org IDs

Both buyer and seller need active RIPE Org IDs or LIR accounts before the transfer can begin.

2

Due Diligence

Blacklist check, BGP history review, and ownership verification through the RIPE database.

3

Purchase Agreement

Legally binding contract between buyer and seller with an escrow arrangement for payment security.

4

Submit Transfer Request

Buyer and seller both submit the transfer request via the RIPE NCC portal.

5

RIPE NCC Review

RIPE verifies authorization and checks policy compliance before approving the transfer.

6

Transfer Completion

Resources are moved to the buyer's account and ROA/RPKI records are updated accordingly.

Required Documents

Make sure you have the following documentation ready before initiating a transfer.

  • Valid RIPE Org ID or LIR account for both parties
  • Company registration documents (recent, within 3 months)
  • Government-issued ID of authorized signatories
  • Signed IPv4 transfer agreement
  • Bank details for escrow payment

RIPE Transfer Types

RIPE NCC supports two types of IPv4 transfers, each with different requirements and timelines.

Intra-RIPE Transfer

  • Between two RIPE NCC members or LIRs
  • Faster processing (1–2 weeks)
  • Simpler documentation requirements
  • Governed by RIPE-689 policy

Inter-RIR Transfer

  • Between RIPE and another RIR (e.g., ARIN)
  • Longer processing (3–6 weeks)
  • Requires both RIRs' approval
  • Additional documentation needed

Frequently Asked Questions

Common questions about RIPE NCC IPv4 transfers.

Do I need to be a RIPE NCC member?
You need a RIPE Org ID, which can be obtained through a sponsoring LIR (Local Internet Registry) if you're not a direct member.
How long does a RIPE transfer take?
Intra-RIPE transfers typically take 1–2 weeks. Inter-RIR transfers involving RIPE can take 3–6 weeks.
Is there a needs test for RIPE transfers?
No. Since RIPE-689 (adopted in 2014), RIPE NCC does not require a needs justification for IPv4 transfers.
Can I transfer legacy RIPE resources?
Yes, legacy resources can be transferred. Additional verification of the holder's authority may be required.
Does ipv4.center handle the RIPE transfer?
Yes. ipv4.center manages the entire transfer process including documentation, RIPE portal submissions, and post-transfer ROA/RPKI configuration.

Ready for a RIPE Transfer?

Browse available RIPE IPv4 blocks and let us handle the entire transfer process from start to finish.

Browse RIPE ListingsMore Guides