Quick Guide To Internet Number Resource Transfers

Submitting a Transfer Request

Via ARIN Online

To request a Transfer Between Specified Recipients within the ARIN Region (NRPM 8.3), a Transfer Due to Mergers, Acquisitions, and Reorganizations (NRPM 8.2), or an outbound Inter-RIR Transfer to Specified Recipients (NRPM 8.4):

1. Log in to your ARIN Online account.
2. Select Transfer Resources from the navigation menu.
3. Follow the instructions presented to you.

ARIN will collect a $500 USD, non-refundable processing fee for each transfer request of Internet number resources. This fee will be invoiced to the source organization’s billing Point of Contact (POC), is to be paid before request evaluation begins, and does not guarantee approval.

Once the transfer is approved and ARIN receives a signed Registration Services Agreement (RSA) and any other applicable fees, and completes any required Inter-RIR coordination, your resources will be transferred.

In cases where number resources are transferred due to a company merger or acquisition (NRPM 8.2), the organization receiving the resources will be required to sign an RSA and will have the option of retaining the legacy status of the IPv4 resources if they were issued prior to 22 December 1997.

Transfer Request Requirements

Select a transfer type for more information:

• Submitting a Transfer Request
  • Via ARIN Online
• Transfer Request Requirements
  • Transfers Based on Mergers, Acquisitions, and Reorganizations
  • Transfers of Released Number Resources to Specified Recipients
  • Transfers of Number Resources to ARIN from Another RIR
  • Transfers of Number Resources from ARIN to Another RIR
  • Transfer Requirements for Specified and Inter-RIR Transfer Recipients
• Wait List Restrictions

Transfers Based on Mergers, Acquisitions, and Reorganizations

(NRPM 8.2 )

ARIN will consider requests for the transfer of number resources in the case of mergers and acquisitions upon receipt of evidence that the new entity has acquired assets that used the transferred resources from the current registrant or acquired the current registrant as a whole. Acceptable types of documentation include:

• An authenticated copy of the instrument(s) affecting the transfer of assets, such as:
  • Asset purchase agreement and bill of sale
  • Finalized merger or amalgamation agreement filed with a province/state/federal government
  • Finalized court order
  • SEC or other public filings that document the transfer of assets
• Authenticated documentation showing name change, such as:
  • Amended articles of incorporation
  • State/province/federal government verification of name change

If multiple transactions connect the old and new organizations, documentation will be required for each transaction. You are welcome to redact any financial or otherwise sensitive information. If necessary, ARIN has a standard nondisclosure agreement available.

Mergers, acquisitions, and reorganization activity resulting in the surviving entity ceasing to have a real and substantial connection with the ARIN region shall be permitted to continue holding any numbering resources issued (directly or indirectly) by ARIN prior to the merger, acquisition or reorganization activity, but shall not qualify for any additional numbering resources (directly or indirectly) from ARIN, unless and until it once again has a real and substantial connection with the ARIN region as required by the Number Resource Policy Manual.

The resources being transferred as part of a NRPM 8.2 transfer will not be subject to a needs-based assessment during the process of the NRPM 8.2 transfer.

Transfers of Released Number Resources to Specified Recipients

(NRPM 8.3)

ARIN will consider requests for the transfer if:

• ARIN has received verification that the authorized resource holder wishes to release the resources to an organization within the ARIN region, and that the intended recipient has a demonstrated need for the resources based on current ARIN policy.
• Requests for transfers under this policy must be submitted by an authorized individual from the registered organization.
• The recipient organization may receive blocks of IPv4 addresses or ASNs under a NRPM 8.3 transfer as long as they can demonstrate the need for the resource under ARIN policy as defined in NRPM 8.5.
• The recipient organization may be required to complete a resource request form in order to provide the detailed information needed to verify that they qualify for the number resources under an existing ARIN policy.
• If applicable the recipient will be removed from the ARIN Waitlist and will not be allowed to reapply under section 4.1.8. ARIN Waitlist for a period of 90 days.

In the event that the current registrant of the resources no longer exists, ARIN will require the requesting organization to complete a Merger and Acquisition Transfer (NRPM 8.2) before proceeding with the NRPM 8.3 request. This is done in accordance with policy and provides a clear audit trail showing the chain of registration.

• The source entity must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include Merger and Acquisition transfers.

• The source entity will not be allowed to apply for IPv4 address space under Section 4.1.8. ARIN Waitlist for a period of 36 months following the transfer of IPv4 address resources to another party

IP addresses from a reserved pool (including those designated in Section 4.4 and 4.10) are not eligible for transfer.

Transfers of Number Resources to ARIN from Another RIR

(NRPM 8.4)

ARIN will consider requests for the transfer if:

• The source RIR confirms the authorized resource holder wishes to release the resources to the specified recipient within the ARIN region.
• The recipient organization demonstrates need for the address space being transferred under current ARIN policy, as defined in NRPM section 8.5, by showing how the resources will be used within 24 months.

IP addresses from a reserved pool (including those designated in NRPM 4.4 and NRPM 4.10) are not eligible for transfer.

Transfers of Number Resources from ARIN to Another RIR

(NRPM 8.4)

ARIN will consider requests for the transfer if:

• The authorized registrant of the resources confirms their desire to release to an organization located within another RIR’s service region.
• ARIN has received confirmation that the specified recipient meets the requirements to receive the released resources under the recipient RIR’s inter-RIR transfer policy.

For IPv4 transfers, in the event that the current registrant for the IPv4 addresses no longer exists, ARIN will require the requesting organization to complete a Merger and Acquisition Transfer (NRPM 8.2) before proceeding with the Inter-RIR Transfer request.

For IPv4 transfers, source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. This restriction does not include Merger and Acquisition Transfers.

IP addresses from a reserved pool (including those designated in NRPM 4.4 and NRPM 4.10) are not eligible for transfer.

If applicable the recipient will be removed from the ARIN Waitlist and will not be allowed to reapply under section 4.1.8. ARIN Waitlist for a period of 90 days.

Transfer Requirements for Specified and Inter-RIR Transfer Recipients

(NRPM 8.5)

The minimum IPv4 transfer size is a /24. Recipient organizations without direct assignments/allocations qualify for an initial /24.

Recipient organizations may qualify for a larger initial IPv4 address block by providing documentation which:

• Details 50 percent of the requested IPv4 addresses will be used within 24 months.
• Demonstrates 50 percent of the sum of all previous assignments and allocations is efficiently used.

Alternatively, recipient organizations with direct assignments/allocations who demonstrate 80 percent efficient utilization of the sum of all precious assignments/allocations may qualify for a transfer equal to the total size of their current IPv4 holdings (up to a /16). For organizations operating multiple discrete networks, each may be assessed individually for the utilization threshold, and the organization must provide justification that each network is discrete. Organizations may only qualify under this policy once every six months.

Wait List Restrictions

(NRPM 8.6)

Any organization which is on the wait list and submits a request to be the source of a transfer under any provision in section 8 will be removed from the wait list.