Your IP address could not be determined at this time.

Transfer Resources

IP addresses and Autonomous System Numbers (ASNs) issued by ARIN or its predecessors may only be transferred to another organization when:

  • An organization acquires the assets that are using IP addresses and/or ASNs in a currently operating network via a merger, acquisition, or similar transaction
  • An organization with unused IPv4 address space or an ASN releases it to a specified recipient who qualifies for it under current ARIN policy (either inside or outside the ARIN region)

Transfer requests must meet the requirements of ARIN transfer policies in order to receive approval. Before reviewing the guidelines below and submitting your request, please view ARIN's instructional video series for a briefing on the resource transfer process and what to expect.

Submitting a Transfer Request

Note: All transfer requests require an ARIN Online account linked to either an Admin or Tech Point of Contact record (POC) with the authority to request resources for a valid Organization Identifier (Org ID).

To request a Transfer:

  • Log into your ARIN Online account
  • Select Transfer Resources on the left
  • Follow the instructions on the form
  • Upon approval, pay a transfer fee and any other applicable fees
  • Submit a signed Registration Services Agreement (RSA) within 90 days

Once ARIN receives a signed RSA and all applicable fees, your resources will be transferred within two business days. If you need a status update on your transfer request or have any questions, please call ARIN Registration Services at +1.703.227.0660. For fee or RSA questions, call ARIN Financial Services at +1.703.227.9886.

Note: All resource holders are responsible for proper record maintenance with ARIN, including:

  • Org ID and POC information upkeep
  • Responsible IP address reassignment
  • Reverse DNS lookup maintenance (IN-ADDRs)
  • Payment of all annual registration renewal and maintenance fees

Transfers Due to Mergers and Acquisitions

(NRPM 8.2)

If your organization acquired assets (such as customers and equipment) from another organization via an acquisition or merger, and those assets are using IP addresses and/or ASNs that are directly registered through ARIN, you may request a transfer of those resources. ARIN will proceed with processing transfer requests even if the number resources of the combined organizations exceed what can be justified under current ARIN policy. In that event, ARIN will work with the resource holder(s) to transfer the extra number resources to other organization(s) or accept a voluntary return of the extra number resources to ARIN.

Note: If your organization has not undergone a merger, acquisition, or reorganization, and simply requires a name change, you may request one by:

  • Logging into ARIN Online
  • Selecting Your Account > Organization Identifiers on the left
  • Select the appropriate Organization Identifier (Org ID)
  • Select "request name change" on the right
  • Fill in the appropriate fields and attach official name change documents filed with your state/province
  • Submit your name change request to ARIN for review


  • The new organization must provide evidence that they have acquired the assets that use the resources to be transferred in one or more of the following forms:
    • 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

Transfers to Specified Recipients Within the ARIN Region

(NRPM 8.3)

If your organization is in need of, or currently holds unused ARIN-issued IPv4 address space or an Autonomous System Number (ASN), you may request an 8.3 Transfer.

Both the recipient and source organizations must submit 8.3 transfer requests separately. These ticketed requests will be linked to one another by ARIN staff once they have been reviewed.

Note: If your organization is participating in an 8.3 transfer, please coordinate your request with the other party prior to ARIN approval. ARIN cannot provide information on ticketed requests from other organizations. Also keep in mind that regardless of pre-approval, both the source and recipient organizations must submit an 8.3 transfer request.

Note: If you have not identified the party you wish to transfer resources to or from, you may request a transfer pre-approval

Requirements for the Source Organization (Current Registrant)

  • The source organization must be the current registered holder of the resources
  • If the current registrant no longer exists, an 8.2 transfer may be required before the 8.3 transfer 
  • Must not be involved in any dispute as to the status of the resources
  • Must provide a notarized Officer Acknowledgement Letter
  • The minimum transfer size is a /24 
  • Must not have received a transfer, allocation or assignment of IPv4 number resources from ARIN within 12 month prior to the approval of the transfer
    • This does not apply to 8.2 transfers

Requirements for the Recipient Organization

  • The recipient must demonstrate a need for up to a 24-month supply of IP addresses under current ARIN policy
  • May need to sign a Registration Services Agreement (RSA)

Next Steps:

Once both the source and recipient involved in the transfer (if known) meet the transfer requirements, the following steps must occur:

  • The Admin or Tech Point of Contact (POC) on the Org ID of both the source (holder of the resources) and the recipient organization must submit a transfer request via ARIN Online. Both organizations will be issued a ticket number for their respective requests.
  • ARIN will link the two tickets after the source and recipient organizations on a transfer request are identified.
  • An ARIN analyst will work on each request independently of the other. ARIN cannot report to one organization on the status of another organization's ticket, so the source and recipient organizations will need to coordinate with each other directly to monitor progress on their respective requests.
  • Upon approval of both transfer requests, an invoice for the transfer fee will be sent to the recipient organization along with a Registration Services Agreement (RSA) if applicable.
  • Upon receipt of the fee and Registration Services Agreement (RSA), ARIN will complete the transfer.

Inter-RIR Transfers

(NRPM 8.4)

8.4 transfers allow organizations within the ARIN region who hold unused IPv4 address space to request transfers to a specific qualified recipient in another Regional Internet Registry (RIR) region. 8.4 transfers also allow organizations within another RIR's region to transfer IPv4 addresses to an organization within the ARIN region. In both cases, an 8.4 transfer can only be conducted between RIRs that share reciprocal, compatible, needs-based policy. 

Note: Inter-RIR transfers involving ARIN are solely for IPv4 addresses, and may not include Autonomous System Numbers (ASNs) or IPv6 addresses.

APNIC and RIPE NCC are currently the only RIRs with ARIN-compatible inter-RIR transfer policies. Other RIRs have policy proposals under discussion that will enhance their compatibility with ARIN, but they may not be fully implemented for some time. Due to the consolidated efforts between multiple RIRs and organizations, the time required, to conclude an 8.4 transfer may vary.

Note: If you have not identified the party you wish to transfer resources to or from, you may request a transfer pre-approval

Requirements for Transfers From ARIN to another RIR:

Source Requirements:
  • The source organization must be the current registered holder of the IPv4 resources
  • If the current registrant no longer exists, an 8.2 transfer may be required before the 8.4 transfer
  • The source organization must not be involved in any dispute as to the status of the resources
  • Must provide a notarized Officer Acknowledgement Letter
  • The minimum transfer size is a /24
  • Must not have received a transfer, allocation or assignment of IPv4 number resources from ARIN within 12 month prior to the approval of the transfer
    • This does not apply to 8.2 transfers
Recipient Requirements:
  • The conditions on a recipient outside of the ARIN region will be defined by the policies of the receiving RIR
  • Upon completion, the network record will move to the other RIR and be removed from the ARIN database and a placeholder record pointing to the new RIR will be added

Requirements for Transfers From another RIR to ARIN:

Source Requirement:
  • Source organizations outside of the ARIN region must meet any requirements defined by the RIR where the source organization holds the registration
Recipient Requirements:
  • Recipients within the ARIN region will be subject to current ARIN policies
  • Recipients within the ARIN region must demonstrate the need for up to a 24-month supply of IPv4 address space
  • The minimum transfer size is a /24
  • May be required to sign a Registration Services Agreement (RSA) for the resources being received

Specified Transfer Listing Service (STLS)

The STLS is an optional service that facilitates 8.3 and 8.4 transfers of IPv4 addresses from validated source organizations that have IPv4 addresses available for transfer to recipient organizations with a demonstrated need for IPv4 addresses. Additionally, the STLS allows entities to facilitate these transfers between agreeing parties ("facilitators").

STLS participants will have full access to contact information provided for all registered source and recipient organizations. This information may be accessed through the Downloads & Services option within ARIN Online by any registered STLS participant, including facilitators.

Learn more about the STLS.

View a list of registered STLS facilitators.

ARIN provides a publicly available summary that includes potentially available IPv4 address space(tallied by available address block size) and a summary of needed IPv4 address space(tallied by needed addresses listed in /24 equivalents). The public STLS summary is updated as participation in the service changes and does not contain any organizational name or contact information.

Note: Participating organizations must agree to the STLS Terms of Service and are subject to vetting by ARIN's Registration Services Department. Requests to receive IPv4 addresses through STLS are subject to the same policy criteria as requests submitted directly to ARIN.

Frequently Asked Questions

Who may submit a transfer request?

An 8.2 transfer request may be submitted by any Point of Contact (POC) from the recipient organization. Both the recipient and source organizations must submit 8.3 transfer requests separately. 8.4 transfer requests must be submitted by a POC of the organization in the ARIN region, whether they are source or recipient. ​

What kind of documentation will you be asking for?

Not all transfers require the same documentation, but some examples include bills of sale, finalized and filed merger or amalgamation agreement certificates of merger or amalgamation, other finalized contracts, certified deeds, or finalized court orders. ARIN will work with you to determine the appropriate documentation based on your request details.

Do I have to send my entire Asset Purchase Agreement?

No, we will only ask you for four key items:

  • the page(s) that list the parties involved
  • the page(s) that list the physical assets that were acquired
  • the page(s) that list any excluded assets and
  • the signature page(s)

Can I redact any monetary listings in my merger or acquisition contracts?

Yes, ARIN is not concerned with the associated costs of the merger or acquisition.

Our contracts are confidential and we do not feel comfortable sharing the sensitive data. Is there any other way to complete the transfer?

ARIN is willing to enter into a standard Non-disclosure Agreement (NDA) with you prior to your organization's submission of sensitive or confidential data.

I need to transfer resources, but the merger/acquisition took place many years ago and I no longer have the legal documentation outlining the transaction. Is there anything that can be done?

Submit your request as normal and we will work with you to obtain as much relevant information, documentation, and evidence as possible. Often, older documents are available on the Secretary of State/State Corporation Commission sites of various states, the U.S. Securities and Exchange Commission site and other local, state, and federal government sites.

The organization name listed on the records was never our legal name. What kind of documentation will ARIN need so we can update the records?

ARIN needs to see documentation showing the original registration was in error. For example, if the organization name was listed as a fictitious name or doing business as (D/B/A) name instead of the legal name, ARIN may ask you to provide a copy of the official business name document which was filed with a local or state government that shows the D/B/A name has always been registered to the actual legal organization name. ARIN will need to confirm and vet the organization in order to effectuate such an update.

Are there any constraints when transferring address blocks using a third-party brokerage service outside of ARIN?

The negotiations and terms of a transfer of an address block between two parties is a matter for resolution between those parties. The details of such an arrangement and/or the financial terms may be negotiated between the parties directly or through a third party facilitator. However, all transfers must be made in accordance with current ARIN policies as defined in the NRPM, and only transfer requests in compliance with ARIN policy may be processed. We recommend that parties contemplating a transfer work with ARIN early on in the process to ensure that such a transfer request would be valid under ARIN policy.

We know that ARIN has a Specified Transfer Listing Service (STLS) on the website. Is the STLS "active"? Have there been any transactions to date via the STLS?

Yes, ARIN's STLS is active and several parties have registered for the program. IP address block sizes are listed on the Public STLS Summary Report page, but ARIN cannot comment on the details of any particular transactions.

Does ARIN recommend using the STLS instead of other brokerage services that are not affiliated with ARIN? If so, why? Does ARIN have any legal rights to enforce that?

ARIN does not make any recommendations or have a preference for any brokerage services, STLS or otherwise. Parties to a transfer have the option of using the STLS to facilitate a NRPM section 8.3 transfer; but they are not required to do so. ARIN provides the STLS for the benefit of the Internet community in response to the demand for transfer services. Parties are free to use the STLS to facilitate their transfers, or they may choose to work outside of STLS and make a transfer request independent of STLS. ARIN's transfer policies apply whether a company uses the STLS or not, and in either case, the transfer request must meet with ARIN policy to be processed.

How does ARIN handle bankruptcy-related transfers?

Please see this article for a legal perspective on transfers within the ARIN region related to bankruptcy court proceedings.

Does ARIN inform the community about resources that have been transferred either via 8.3 or 8.4 transfers?

Yes, a report of number resources transferred per the requirements of Section 8.4 Inter-RIR Transfers to Specified Recipients or Section 8.3 Transfers to Specified Recipients is available on the Inter-RIR and Specified Transfers of Internet Number Resources page.

Search Related Content


full site search

IPv4 Transfers Flowchart Examples: Transfer Request Documentation

Registration Services Help Desk

Interacting With ARIN

Monday through Friday
7:00 AM to 7:00 PM ET
Phone: +1.703.227.0660
Fax: +1.703.997.8844
Tips for Calling the Help Desk