You are here: Home > Manage IPs and ASNs > Resource Transfers and Mergers > Transfers > IPv4 > Assigned PI Space

Transfer of IPv4 Assigned PI Space

End Users and LIRs can transfer Provider Independent (PI) IPv4 address space, which is space that was originally assigned by the RIPE NCC.

Who Can Receive a Transfer of IPv4 PI Space

In order to be eligible to receive a transfer of IPv4 PI space from another organisation, the receiving party must:

  • Be a member of the RIPE NCC or have a signed End User Assignment Agreement with a sponsoring LIR (a member of the RIPE NCC)
  • Have the transfer approved by the RIPE NCC according to the requirements outlined in the existing RIPE Transfer Policy 

IPv4 address space can also be transferred as part of a merger or acquisition.

Who Can Transfer IPv4 PI Space

Any legitimate holder of IPv4 PI space can transfer this space to another End User or member in the RIPE NCC service region, provided:

  • The address space is covered by an End User Assignment Agreement with a sponsoring LIR or the recipient is a member of the RIPE NCC
  • The address space is registered in the RIPE NCC service region
  • The address space has not been received as part of a transfer within the last 24 months

Note: assignments that were provided to Internet Exchange Points (IXPs) for peering LANs cannot be transferred due to the special requirements for IXP assignments (section 6.1 of "IPv4 Address Assignment and Allocation Policies for the RIPE NCC Service Region").

To Get Started With the Transfer

To get started with a transfer of IPv4 PI space, the LIR holding the address space or the sponsoring LIR of either the transferring or receiving End User can contact the RIPE NCC using the registry update function in the LIR Portal.

The request should include:
  • The resources being transferred
  • The Transfer Agreement signed by both parties. This agreement must be signed by company directors that are legally authorised to sign/act on behalf of the organisation.
  • The End User Assignment Agreement signed by the receiving End User and a member of the RIPE NCC 
  • The company name and contact details of both End Users
  • Recent company registration papers for both End Users
  • The following resource object information for the receiving End User: 
    • org: 
    • admin-c: 
    • tech-c: 
    • mnt-by: 
  • Whether the transfer is to be permanent or temporary (in the case of a temporary transfer, specify until which date the resources are to be transferred)

Further Detail on Transfers

For further detail, refer to the RIPE NCC Procedural Document, "Transfer of Internet Number Resource Records and Change of Members Official Legal Name".