ARIN guide

ARIN 8.2 vs 8.3 vs 8.4 transfers explained

ARIN's transfer policy, section 8 of its Number Resource Policy Manual (NRPM), has three ways to move IPv4 addresses from one organization to another. Which one applies depends on why the addresses are moving and where the other party is.

ARIN Qualified Facilitator Checked against ARIN sources October 26, 2026

In short

  • 8.2: addresses move with a business (merger, acquisition, reorganization, name change). No needs test.
  • 8.3: a transfer between two organizations inside the ARIN region, the usual way to buy or sell. The recipient must qualify under NRPM 8.5.
  • 8.4: a transfer between ARIN and another registry with a compatible policy: APNIC, LACNIC or RIPE NCC.
  • Fees: $500 per transfer request, plus a recipient fee by block size for recipients in the ARIN region (ARIN fees).

Side by side

Sources: NRPM section 8, ARIN: Transferring IP Addresses & ASNs, ARIN Fee Schedule. ASNs can also be transferred under these sections.
8.2 Mergers & acquisitions8.3 Within ARIN8.4 Inter-RIR
Used forAddresses that move with a business: merger, acquisition, reorganization or name changeSale or transfer between two organizations in the ARIN regionTransfer between an ARIN organization and one in another registry's region
Needs testNoneRecipient must meet NRPM 8.5Into ARIN: NRPM 8.5. Out of ARIN: the receiving registry's policy
Pre-approval availableNoYesYes, for recipients in the ARIN region
Who submitsThe new (surviving) organizationBoth source and recipient, each in ARIN Online; ARIN links the ticketsA point of contact of the organization in the ARIN region
Key documentsProof of the transaction, e.g. asset purchase agreement, merger filing, court order, SEC filingSource: notarized Officer Acknowledgement Letter. Recipient: 24-month need, RSAAs 8.3 on the ARIN side, plus the other registry's requirements
ARIN fee$500 (requesting organization)$500 (source) + recipient fee by sizeOut of ARIN: $500 (source). Into ARIN: recipient fee by size
Minimum sizeSmaller of the original allocation or current minimum/24/24

8.2: Mergers, acquisitions and reorganizations

Use 8.2 when the addresses go with a business: you bought the company that holds them, bought the assets (network, customers) that use them, merged, reorganized or changed your legal name. Because the addresses stay with the network that uses them, ARIN does not apply a needs test (NRPM 8.2).

  • The new organization submits the request with proof of the transaction, such as an asset purchase agreement, a finalized merger agreement, a court order or SEC filings, or proof of a name change. If several transactions connect the old and new organizations, ARIN needs documents for each one. Financial details can be redacted (ARIN quick guide).
  • The current registrant may not be in a dispute over the resources.
  • The new organization signs a Registration Services Agreement (RSA) covering the transferred resources.
  • The source cannot apply to ARIN's waitlist for 36 months, unless the recipient remains its subsidiary, parent or under common ownership.

8.2 often comes up before a sale. If the organization on ARIN's records no longer exists, for example because it was acquired years ago, ARIN requires an 8.2 transfer to the current owner first, before that owner can sell under 8.3 or 8.4.

8.3: Transfers within the ARIN region

8.3 is how IPv4 addresses are usually bought and sold in North America: a source releases addresses to a specific recipient, both in the ARIN region (NRPM 8.3).

The source (seller) must

  • Be the current registered holder, with no dispute over the addresses.
  • Provide a signed, notarized Officer Acknowledgement Letter and pay the $500 transfer request fee.
  • Not have received an IPv4 transfer, allocation or assignment from ARIN in the past 12 months (8.2 transfers excepted).
  • Know that transfers must be at least a /24 (NRPM 8.5.3), and that addresses from ARIN's reserved pools (NRPM 4.4 and 4.10) can't be transferred.
  • Accept that it cannot apply to ARIN's waitlist for 36 months afterwards.

The recipient (buyer) must

  • Qualify under NRPM 8.5: an initial /24 with no utilization history, or a 24-month plan to use at least 50% of a larger block. See ARIN pre-approval.
  • Sign an RSA covering the addresses, unless it already has one on file.
  • Pay the recipient transfer processing fee on approval.
  • Leave ARIN's waitlist if it is on it; it cannot reapply for 90 days.

ARIN reviews the source's and recipient's requests separately and completes the transfer within two business days of having the signed RSA and all fees (ARIN).

8.4: Inter-RIR transfers

8.4 moves addresses between ARIN and another regional internet registry. ARIN allows it only with registries whose policies are reciprocal and compatible with its needs-based policy (NRPM 8.4). ARIN's transfer page lists APNIC, LACNIC and RIPE NCC as approved and AFRINIC as not approved. IPv6 addresses cannot be part of an inter-RIR transfer with ARIN.

Sources: NRPM 8.4, ARIN quick guide. ARIN notes that the time to complete an 8.4 transfer can vary.
DirectionWhat applies
Into ARIN (e.g. RIPE NCC → ARIN)The ARIN recipient meets NRPM 8.5 (24-month need, minimum /24), signs an RSA and pays the recipient fee. The source registry confirms its holder wants to release the addresses.
Out of ARIN (e.g. ARIN → RIPE NCC or APNIC)The receiving registry's policy governs the recipient, and ARIN needs confirmation that the recipient meets it. The ARIN source follows the same 12-month rule as 8.3, unless one party owns or controls the other, or both are under common ownership or control.

IPv4 Depot handles ARIN transfers with RIPE NCC and APNIC; in our deals, 8.4 transfers most often go out of ARIN to those two regions. For the other side of the transfer, see our RIPE NCC and APNIC guides.

Which one applies to you?

  • You're buying, and the seller is also in the ARIN region (the US, Canada and parts of the Caribbean): 8.3. Start with pre-approval.
  • You're buying, and the seller is in another registry's region, such as RIPE NCC (Europe, Middle East) or APNIC (Asia-Pacific): 8.4 into ARIN.
  • You're selling to a buyer outside the ARIN region: 8.4 out of ARIN.
  • You acquired the company or network that uses the addresses, or changed your legal name: 8.2. Also do this first if the holder on ARIN's records no longer exists and you want to sell.

ARIN transfer types FAQ

What is the difference between an ARIN 8.2, 8.3 and 8.4 transfer?

An 8.2 transfer moves addresses as part of a merger, acquisition or reorganization and has no needs test. An 8.3 transfer moves addresses between two organizations inside the ARIN region, usually a sale, and the recipient must qualify under NRPM 8.5. An 8.4 transfer moves addresses between ARIN and another regional internet registry that has a compatible needs-based policy.

Which ARIN transfer type do I need to buy IPv4 addresses?

If the buyer and seller are both in the ARIN region, it is an 8.3 transfer. If the addresses come from, or go to, an organization in another registry's region (such as RIPE NCC or APNIC), it is an 8.4 inter-RIR transfer. 8.2 applies only when addresses move with a business through a merger, acquisition or reorganization.

Does an 8.2 merger transfer need ARIN pre-approval?

No. ARIN offers pre-approval for 8.3 and 8.4 transfers. Resources transferred under 8.2 are not subject to a needs-based assessment, but the new entity must document the transaction and sign a Registration Services Agreement covering the resources.

Can I sell IPv4 addresses I received from ARIN recently?

Not straight away. For an 8.3 or 8.4 transfer, the source must not have received an IPv4 transfer, allocation or assignment from ARIN in the 12 months before approval. 8.2 transfers don't count toward that rule, and for 8.4 it doesn't apply when one party owns or controls the other, or both are under common ownership or control. ARIN has no 24-month hold on reselling; that rule belongs to RIPE NCC, which restricts IPv4 addresses from being transferred again for 24 months after they are received.

Which registries can ARIN transfer IPv4 addresses with?

ARIN lists APNIC, LACNIC and RIPE NCC as approved for 8.4 inter-RIR transfers, because their policies are reciprocal and compatible. AFRINIC is not approved. IPv6 addresses cannot be transferred between ARIN and another registry.

How long does an ARIN transfer take to complete?

In IPv4 Depot's experience, when both parties move promptly, ARIN transfers typically complete in about 7 to 10 business days. The time depends mostly on both parties' paperwork; ARIN says that once it has a signed Registration Services Agreement and all fees, it completes the transfer within two business days. For 8.4 inter-RIR transfers, ARIN says the time to complete can vary, since the other registry has its own process.

Sources

Registry facts on this page come from ARIN's own documents, checked on October 26, 2026. ARIN's policies and fees change; where this page and ARIN differ, ARIN is right.

Related ARIN guides

ARIN IPv4 transfer guideThe whole process, step by stepARIN pre-approvalWhat to submit and how long it takesARIN transfer feesTransfer fees and the annual registration plan

Not sure which transfer type fits your deal?

IPv4 Depot is an ARIN Qualified Facilitator. Tell us who holds the addresses today and where they're going, and we'll map out the transfer.

Talk to IPv4 Depot 1.800.856.5960