Transfers in the RIPE NCC Service Region
Who Can Transfer Resources?
All resource holders in the RIPE NCC region can transfer resources in accordance with RIPE policies. Resource holders are either LIRs (Local Internet Registries) or End Users.
Transfer requests can only be submitted by the offering LIR or the sponsoring LIR of the offering End User.
The following transfer scenarios are possible:
- From LIR to LIR which are different organisations or between two LIRs belonging to the same member.
- From End User to End User with the same sponsoring LIR or with a different sponsoring LIR.
- From LIR to End User and vice versa.
Which Types of Resources Can Be Transferred?
To see which types of resources can be transferred, please refer to the table below.
| IPv4 Allocation | IPv4 PI | IPv6 Allocation | IPv6 PI | 16-bit ASN | 32-bit ASN | |
|---|---|---|---|---|---|---|
RIPE NCC membership required |
yes |
no |
yes |
no |
no |
no |
Can be sponsored |
no |
yes |
no |
yes |
yes |
yes |
Transfer restriction |
yes |
yes |
no |
no |
yes |
no |
Minimum transfer size |
- |
- |
/32 |
/48 |
- |
- |
Transfer Restrictions
IPv4 addresses and 16-bit AS Numbers are by policy restricted from being transferred for 24 months after they have been received either from the RIPE NCC, via a transfer from another organisation or following a change in business structure (e.g. merger/acquisition).
Exception: For transfers between multiple LIR accounts belonging to the same organisation, also referred to as consolidations, the 24 months restriction will only apply once after the resources were received from the RIPE NCC or from another organisation.
Documents Required to Transfer Resources
The following documents are required for a resource transfer in the RIPE NCC service region:
- For each of the parties involved in the transfer:
- Legal persons: Recent registration document from the relevant national authorities.
- Natural persons: A digital copy of the passport or another valid ID document. The validity of the document will be verified by a third party called iDenfy.
- A Transfer Agreement signed by both parties. This agreement must be signed by representatives that are legally authorised to sign/act on behalf of the organisation.
- Documentation that proves that signees are authorised to sign on behalf of their organisation (this is usually visible on the company registration document).
If the receiving party is an End User, we will also require:
- The End User Assignment Agreement signed by the receiving End User and the sponsoring LIR.
Consolidation (transfers between LIRs held by the same member):
- Please note that a transfer agreement is not required for transfers between LIRs held by the same member, but we may ask you to provide a recent copy of your company's registration documents/certificate. The request can be submitted as a standard transfer via the LIR portal.
Request Evaluation
Once all supporting documentation has been received, we will evaluate your request according to the applicable RIPE policies and RIPE NCC procedures. We will also check against the EU sanctions list – if either party is found to be under sanctions, the transfer request will not be approved.
How to Submit a Transfer Request
The offering party needs to request the transfer via their LIR Portal (under ‘Resources’ -> ‘Request Transfer’) or by clicking the button below.
You will need to fill in the required information and select the resources you wish to transfer. For IPv4 resources, you can also transfer partial blocks of a prefix.
All resource transfers are free of charge.
Relevant Policies
Resource transfers in our service region are regulated by the following RIPE policies:
RIPE Resource Transfer Policies
Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region