RIPE IPv4 Transfer Guide: PA, PI, Sponsoring LIR, Escrow
A RIPE IPv4 transfer moves the registration of an address block from one holder to another in the RIPE Database. This guide covers PA and PI resources, the sponsoring LIR, documents and the order of steps in the RIPE NCC service region.
Last policy review: 2026-10. Checked against RIPE-807, RIPE Resource Transfer Policies (published 30 Oct 2023), RIPE-826, IPv4 Address Allocation and Assignment Policies (20 Jun 2024) and the RIPE NCC transfer pages. Re-check the sources before you act.
Key takeaways
- Policy vs procedure - policy (RIPE-807) says what is allowed. The RIPE NCC transfer pages say how a request is filed.
- Not every block is equal - IPv4 allocations (PA) may only go to RIPE NCC members. IPv4 PI follows other rules, and a PI holder that is not a member needs a sponsoring LIR.
- Holding restriction - RIPE-807, section 2.2.1, restricts transfer of IPv4 for 24 months from the date the holder received it.
- Escrow is private - a private arrangement, not a RIPE NCC service.
What a transfer changes
After approval the RIPE NCC updates the registry: the new holder appears in the RIPE Database and in RIPE NCC records. The transfer does not change the history of the block, its blacklist status or its geolocation. See the blacklist check guide.
Resource categories: PA, PI and legacy
| Resource | Membership needed | Sponsoring LIR | Restriction |
|---|---|---|---|
| IPv4 allocation (PA) | Yes | No | 24-month rule applies |
| IPv4 PI | No | Yes, if holder is not a member | 24-month rule applies |
| Legacy | See legacy page | See legacy page | RIPE-807: no specific intra-region rules |
PI space is assigned to an End User for a specific purpose and under RIPE-826 it is tied to the original criteria. Do not assume a PI block can be freely sold: each request is reviewed against policy. Legacy resources have their own RIPE NCC page.
Eligibility and policy checks
- Parties - the offering LIR, or the sponsoring LIR of an offering End User, files the request. For allocations the recipient must be a RIPE NCC member (RIPE-807).
- 24-month rule - read the current RIPE-807 text on the date you plan the deal.
- Sanctions - both parties are checked against the EU sanctions list.
- Lock - a holder may have set a Voluntary Transfer Lock (RIPE-806). Ask the seller.
Role of an LIR and a sponsoring LIR
An LIR is a RIPE NCC member. It holds allocations and may sponsor End Users with PI resources. A sponsoring LIR supports the End User's request and signs the End User Assignment Agreement with it.
Documents and corporate authority
- Registration documents - a recent company register extract for each legal person.
- Transfer agreement - signed by authorised representatives of both parties. The RIPE NCC publishes a template.
- Proof of authority - the signatory must be shown to be entitled to sign.
- End User agreement - if the recipient is an End User, with its sponsoring LIR.
Step-by-step RIPE process
- Check the block: category, receipt date, WHOIS history, locks.
- Sign the transfer agreement.
- The offering party opens the LIR Portal and files a transfer request, then supplies the documents.
- The RIPE NCC evaluates the request against policy and procedure. It states no fixed processing time.
- After approval the registry is updated. RIPE NCC transfers are free of charge according to its transfer page.
- Update objects and routing, then settle payment.
Where escrow fits
Escrow holds the payment until the registry change is confirmed. The RIPE NCC does not provide, run or endorse escrow. Escrow sits around the approval, never inside it.
WHOIS, route objects, RPKI and geolocation
After the transfer, check the inetnum and org objects, maintainers, route objects and ROAs. Replace the seller ROAs with new ones. Geolocation databases update on their own schedule. If a database still shows the previous country, see how to fix IPv4 geolocation after a transfer.
Common reasons for delay
Outdated registration documents, unclear signing authority, a block inside the 24-month window or under a lock, and name mismatches.
Special cases
Legacy blocks, PI with an old or missing sponsor, mergers, and inter-RIR moves need individual review. See inter-RIR transfers. The ARIN case step by step: ARIN to RIPE inter-RIR transfer guide.
Next step
Check whether your RIPE block is transferable. Write to ipv4@dcxv.com or use dcxv.com/ipv4. For deal context read how to sell an IPv4 block, block pricing, broker vs marketplace vs direct sale, the buy and sell guide and the 2027 charging scheme. Prices are on /ipv4/pricing. Related pages: /ipv4/sell, /ipv4/buy.
