ARIN Specified Transfers: Requirements, Fees & Timelines

ARIN specified transfers are the regulated mechanism for moving IPv4 blocks between organizations inside the ARIN region. If you’re planning to buy, sell, or merge address space, you need to understand the requirements, the fees, and — just as important — the timelines. IPv4 scarcity keeps pushing prices up, so a botched or non-compliant transfer doesn’t just put both parties at risk. It costs money.

What Are ARIN Specified Transfers and Who Qualifies?

An ARIN specified transfer is the official process by which IPv4 number resources move from one ARIN-registered organization to another. It’s not a reassignment. A transfer permanently changes the authoritative holder of the resource in ARIN’s registration database (WHOIS), along with everything that comes with it — the addresses and the responsibilities.

Who can take part?

• Organizations with ARIN-issued resources: Any holder of IPv4 blocks (typically /24 or larger) registered directly with ARIN can initiate a transfer.
• Legacy resource holders: Even organizations holding pre-ARIN space (legacy Class B or C networks) may qualify, provided the space is confirmed in ARIN’s records.
• Recipients with demonstrated need: Buyers must hold an ARIN-issued Org ID and, in some cases, show an 18-month utilization history justifying the requested block size.
• Mergers, acquisitions, and reorganizations: Transfers can also happen between related corporate entities, though these follow the M&A transfer path with its own documentation.

A practical note before you list your block for sale: verify it’s free of disputed registrations, inactive reallocations, and legacy claims. Marketplaces such as IP4 Market handle seller verification and escrow-backed transactions, which — in my experience watching these deals play out — dramatically lowers the odds of a transfer stalling halfway through.

ARIN Specified Transfers: Key Requirements and Documentation

ARIN’s review process is documentation-heavy. Incomplete submissions are the number one cause of delays. So prepare:

1. Transfer Request Form (NRPM 8.2): Submitted through ARIN Online by both the source and recipient organizations.
2. Resource confirmation: Proof that the source organization holds the block — current registration data matching the Org ID, usually.
3. Business documentation: Articles of incorporation, corporate agreements, or a signed bill of sale between the parties. For M&A transfers, acquisition agreements are required.
4. Utilization justification (recipient): If the block would exceed the recipient’s current justification capacity, ARIN may ask for supporting network plans or growth documentation.
5. No outstanding disputes: Both parties must be in good standing, with no unresolved registration disputes or delinquent fees.

One more thing people forget: the block’s reputation. Check blacklists (Spamhaus, SORBS) and clean up any abusive-use history before you submit. A dirty block complicates the ARIN review and can haunt routing after the transfer is done.

Understanding Transfer Fees and MRA Costs

ARIN charges a transfer fee based on the size of the block, and it’s assessed to the receiving organization. Under the current fee schedule:

• Blocks of /22 through /24 incur a lower-tier fee.
• Larger blocks (/21 and bigger) are charged at higher tiers.
• Multi-registry transfers (between ARIN and other RIRs) carry the same transfer fee, plus coordination with the counterpart RIR.

Then there’s the Minimum Recoupment Amount (MRA) — and this one catches sellers off guard. When a block is transferred, ARIN may assess an MRA charge tied to the addresses being relinquished, effectively recouping discounted annual fees from earlier. Sellers should build the MRA into their asking price. Buyers, for their part, should confirm in writing who bears this cost in the purchase agreement. Not doing so is how last-minute renegotiations happen.

Working with an experienced marketplace like IP4 Market helps both sides price transfers accurately and anticipate the full fee picture before contracts are signed. Worth it, usually.

How Long Does an ARIN Transfer Take? Timelines Explained

Most ARIN specified transfers wrap up somewhere between 30 and 60 days from listing to actual resource movement. But individual stages vary a lot. Knowing where time usually gets lost helps both buyers and sellers set expectations that won’t fall apart halfway through.

Here’s the typical breakdown:

1. Pre-transfer diligence and agreement (1–2 weeks): verifying the block’s status, confirming there are no SWIPed reassignments that need reclaiming, and hammering out the purchase agreement.
2. Listing and escrow setup (a few days): ARIN charges the recipient a $500 processing fee, and escrow arrangements should be squared away before submission.
3. ARIN review (10–15 business days on average): ARIN checks that the recipient meets the demonstrated need requirement, reviews documentation, and verifies the justification for the block size requested.
4. Resource movement and WHOIS updates (a few days): once approved, ARIN updates the registry records and sends a confirmation to both parties.

If you’re in a hurry, build your justification carefully before you submit anything. An incomplete demonstrated need package is the single most common reason reviews stretch past a month. Why? Because ARIN sends the application back for clarification, and the clock restarts. Simple as that.

Common Reasons Transfers Get Delayed or Rejected

Know the typical failure points and you can sidestep most of them:

• Insufficient demonstrated need: ask for a /20 when your utilization data only supports a /22 and you’ll get a reduction request or a flat rejection. Provide detailed current utilization plus a 12-month projection.
• Unresolved reassignments: customer SWIPs sitting on the block have to be reclaimed or documented before the transfer can proceed. Sellers, audit your registrations early. Don’t wait.
• RPKI or legacy considerations: blocks with ROAs still published under the seller’s origin ASNs can cause routing confusion after the transfer. Revoke stale ROAs before closing.
• Inconsistent documentation: if the legal entity name in the purchase agreement doesn’t match the ARIN organization record or the tax paperwork, the review pauses until someone sorts it out.
• NRPM compliance issues: transfers between organizations under common control, or attempts to move resources outside the eligible categories under section 8.3, get rejected outright.

Conclusion: Navigating ARIN Transfers with Confidence

ARIN specified transfers are a mature, well-defined process. Success comes down to preparation: understanding eligibility under the NRPM, budgeting for processing and brokerage fees, making sure the demonstrated need documentation holds up, and cleaning registry records before you submit. Buyers get scarce address space with clean provenance behind it; sellers unlock value from holdings they weren’t using anyway. Everyone operates inside a regulated framework that protects both sides.

There’s a catch, though. The process layers legal, technical, and regulatory concerns all at once, which is why most successful transactions happen with experienced partners rather than solo attempts. IP4 Market provides a trusted platform for IPv4 transactions, with verified sellers, escrow-backed payment protection, and competitive pricing, guiding buyers and sellers through every stage of the ARIN specified transfer process from initial listing to final registry update. Whether you’re acquiring your first block or divesting surplus space, the right preparation and the right partner turn what looks like a complex registry procedure into something straightforward and predictable.