RIPE NCC guide

RIPE NCC IPv4 transfer guide

RIPE NCC is the regional internet registry for Europe, the Middle East and parts of Central Asia. Its transfer rules are lighter than ARIN's or APNIC's: there is no needs test for transfers inside the region, but transferred IPv4 addresses can't be transferred again for 24 months.

Checked against RIPE NCC sources November 2, 2026

In short

  • No needs test for transfers within the RIPE NCC region (ripe-807).
  • Who can receive: allocated (PA) IPv4 only a RIPE NCC member (LIR); PI IPv4 also an End User through a sponsoring LIR.
  • 24-month restriction: IPv4 can't be transferred again for 24 months after it was received, including through a merger or acquisition.
  • Cost: RIPE NCC charges nothing for transfers. Membership in 2026 is EUR 1,000 to sign up plus EUR 1,800 a year per LIR account (EUR 1,894 in 2027).
  • Inter-RIR: with ARIN and APNIC (IPv4 and AS numbers, including legacy) and LACNIC (IPv4). Not with AFRINIC.

Who can buy and sell in the RIPE NCC region

Any legitimate holder can transfer all or part of its IPv4, IPv6 or AS number resources (ripe-807, section 2). Holders are either LIRs (RIPE NCC members) or End Users that hold resources through a sponsoring LIR. What a recipient needs depends on the type of resource:

Source: RIPE NCC: Transfers in the RIPE NCC service region. Transfers can go LIR to LIR, End User to End User, or between an LIR and an End User.
ResourceRecipient must be a memberCan be sponsored24-month restriction
IPv4 allocation (PA)YesNoYes
IPv4 PINoYesYes
IPv6 allocationYesNoNo (minimum /32)
IPv6 PINoYesNo (minimum /48)
16-bit AS numberNoYesYes
32-bit AS numberNoYesNo

Only the offering LIR, or the sponsoring LIR of an offering End User, can submit a transfer request.

The 24-month restriction

RIPE NCC treats IPv4 and 16-bit AS numbers as scarce resources. Under ripe-807, section 2.2, they cannot be transferred for 24 months from the date the holder received them:

  • The clock starts whether the addresses came from the RIPE NCC, from another organization by transfer, or through a merger or acquisition.
  • Further mergers or acquisitions during those 24 months are still allowed.
  • Consolidations between LIR accounts of the same organization trigger the restriction only once, after the resources were first received (RIPE NCC).
  • A holder can also lock its own resources against transfer under RIPE's Voluntary Transfer Lock policy.

For buyers: RIPE NCC publishes every transfer, with the date, in its monthly transfer statistics (ripe-807, section 4), so you can check when a seller received a block. Compared with ARIN: ARIN has no 24-month hold; its rule is that the seller must not have received IPv4 from ARIN in the 12 months before approval (ARIN 8.2 vs 8.3 vs 8.4).

A transfer within the RIPE NCC region, step by step

  1. The buyer sets up. To receive PA space, the buyer opens an LIR account (membership). For PI space, it can sign an End User Assignment Agreement with a sponsoring LIR instead.
  2. Both sides agree terms and sign RIPE NCC's Transfer Agreement, through representatives legally authorized to act for each organization.
  3. The offering LIR submits the request in the LIR Portal (Resources, then Request Transfer) and selects the resources. Part of an IPv4 prefix can be transferred.
  4. Documents. For each party: a recent company registration document from the national authority (or, for a person, a passport or ID checked by RIPE NCC's provider iDenfy), proof the signatories are authorized, and the End User Assignment Agreement if the recipient is an End User.
  5. RIPE NCC evaluates the request against RIPE policy once the documents are complete, and checks both parties against the EU sanctions list. A sanctioned party means no approval.
  6. Registration is updated in the RIPE Database. The new holder then creates its route and domain objects and its ROAs.

The offering LIR must have paid its annual fee for the year before it can transfer resources (RIPE NCC). RIPE NCC doesn't publish a processing time for transfers.

Inter-RIR transfers: RIPE NCC with ARIN and APNIC

Both registries must approve an inter-RIR transfer, and the resources stay under the sending registry's policies until it is complete (RIPE NCC).

Sources: RIPE NCC: Inter-RIR transfers, ripe-807, section 3, ARIN NRPM 8.4.
DirectionWhat applies
Into RIPE NCC (e.g. ARIN → RIPE NCC)The request starts with the seller's registry, which then contacts RIPE NCC. The network using the addresses must have at least one active element in the RIPE NCC region. The recipient needs a contract with RIPE NCC (or a sponsoring LIR for PI; not needed to keep LEGACY status). From a needs-based registry such as ARIN, the recipient gives a plan to use at least 50% within five years.
Out of RIPE NCC (e.g. RIPE NCC → ARIN or APNIC)The holder (or its sponsoring LIR, or a legacy holder directly) emails RIPE NCC's inter-RIR template to inter-rir@ripe.net with a confirmation letter signed by an authorized director. The 24-month restriction still applies (ripe-807, section 3.1). The recipient must meet the receiving registry's policy; for ARIN, that is NRPM 8.5.

Plan for the routing handover

  • Route and domain objects are not carried over; the receiving party creates them.
  • When addresses leave RIPE NCC, reverse DNS delegation is removed immediately, so the recipient should request it from its new registry straight away.
  • RPKI: the old certificate and ROAs are withdrawn. Until new ROAs exist, announcements show as "RPKI Unknown", not "Invalid".

IPv4 Depot handles transfers between ARIN and RIPE NCC; in our deals, they most often go out of ARIN to RIPE NCC. See ARIN 8.4 inter-RIR transfers for the ARIN side.

What it costs

Sources: RIPE NCC transfers ("all resource transfers are free of charge"), ripe-848, Charging Scheme 2026, ripe-867, Charging Scheme 2027.
20262027
Transfer feeNoneNone
LIR sign-up fee (one-time)EUR 1,000EUR 1,000
Annual fee per LIR accountEUR 1,800EUR 1,894
Per independent resource (e.g. PI assignment)EUR 75EUR 75
Per AS numberEUR 50First ASN included; EUR 50 per additional ASN

Brokers in the RIPE NCC region

RIPE NCC used to publish a list of Recognised IPv4 Transfer Brokers. Its Executive Board decided to end it in October 2023, and in January 2024 RIPE NCC confirmed the list had been removed from its website (RIPE NCC). So no broker can currently claim a RIPE NCC listing. To check a broker, look at the lists ARIN and APNIC still keep: IPv4 Depot is an ARIN Qualified Facilitator and an APNIC registered broker.

RIPE NCC transfer FAQ

Does RIPE NCC require needs justification for IPv4 transfers?

Not for transfers within the RIPE NCC service region. The RIPE Resource Transfer Policies (ripe-807) set out who can receive addresses and when they can be transferred, but there is no needs test. The exception is an inter-RIR transfer into the RIPE NCC region from a registry that requires needs-based policies, such as ARIN: then the recipient must give RIPE NCC a plan to use at least 50% of the addresses within five years.

What is RIPE NCC's 24-month transfer restriction?

IPv4 addresses and 16-bit AS numbers cannot be transferred for 24 months after the holder received them, whether from the RIPE NCC, through a transfer from another organization or through a merger or acquisition. Further mergers or acquisitions within those 24 months are still allowed. For consolidations between LIR accounts of the same organization, the restriction applies only once. ARIN's comparable rule is 12 months and applies to the seller's own recent receipts from ARIN.

Do I need to be a RIPE NCC member to buy IPv4 addresses?

To receive allocated (PA) IPv4 space, yes: allocations can only be transferred to a RIPE NCC member (an LIR). Provider Independent (PI) IPv4 space can also go to an End User that has a contract with a sponsoring LIR. In 2026, RIPE NCC membership costs a one-time EUR 1,000 sign-up fee per LIR account plus EUR 1,800 a year; the annual fee rises to EUR 1,894 in 2027.

How much does RIPE NCC charge for an IPv4 transfer?

Nothing: RIPE NCC states that all resource transfers are free of charge. The costs are membership (or a sponsoring LIR's fees for PI space), and an LIR must have paid its annual fee for the year before it can transfer resources. Broker fees and escrow fees are separate.

Can I transfer IPv4 addresses from RIPE NCC to ARIN or APNIC?

Yes. RIPE NCC transfers IPv4 and AS numbers, including legacy resources, with ARIN and APNIC, and IPv4 with LACNIC. AFRINIC has no inter-RIR transfer policy, so no transfers are possible with that region. Both registries must approve, and the recipient must meet the receiving registry's policy; for ARIN that means qualifying under NRPM 8.5.

How long does a RIPE NCC transfer take?

RIPE NCC does not publish a processing time. Evaluation starts once all documents are in, and RIPE NCC checks both parties against the EU sanctions list. Inter-RIR transfers take longer than transfers within the region because both registries must approve and then update their records on an agreed date.

Buying or selling in the RIPE NCC region?

Tell us the block size, where the network is and which registry the addresses are in now. We'll map out the transfer, including any move between RIPE NCC and ARIN.