RIPE to ARIN Transfer Step-by-Step

A RIPE to ARIN transfer moves IPv4 addresses or an ASN from a holder in the RIPE NCC service region to an organization in the ARIN region. The RIPE holder files first, with the RIPE NCC's inter-RIR template sent to inter-rir@ripe.net. Once the RIPE NCC approves, it notifies ARIN, which evaluates the recipient under its own policy.

The RIPE NCC charges nothing for the transfer. ARIN bills the recipient a processing fee ($187.50 for a /24 on the 2026 fee schedule) plus its yearly Registration Services Plan fee, $275 for a /24. A first /24 needs no justification when the recipient holds no IPv4 from ARIN.

Policy references: ripe-807 section 3 (RIPE transfer policy), ripe-769 (RIPE NCC inter-RIR procedure), the RIPE NCC inter-RIR page, ARIN transfers and NRPM section 8.4.

Transfer Overview

RIPE to ARIN transfers move IPv4 addresses and ASNs, legacy resources included. IPv6 cannot move: ARIN excludes it from every transfer between registries. The RIPE NCC handles the source, ARIN the recipient, and both registries update their databases on an agreed date.

Key characteristics:

• Resources: IPv4 (minimum /24, NRPM 8.5.3) and ASNs; no IPv6
• Who files: the RIPE holder with the RIPE NCC, the ARIN recipient in ARIN Online; the RIPE holder never files at ARIN
• RIPE side: free of charge; IPv4 and 16-bit ASNs held for less than 24 months cannot move (ripe-807 section 2.2); most transfers complete within one or two business days (RIPE NCC)
• ARIN side: a first /24 without justification if the recipient holds no IPv4 from ARIN (NRPM 8.5.4); larger or additional blocks need a plan showing 50% use within 24 months (8.5.5); a signed RSA; the recipient processing fee and the yearly RSP fee
• ARIN publishes no end-to-end duration ("the time required to conclude an 8.4 transfer can vary")

For background on inter-RIR transfers and general requirements, see our How Inter-RIR Transfers Work guide. The reverse direction has its own rules: ARIN to RIPE Transfer Requirements.

Pre-Transfer Requirements

Both parties must meet the rules below before anyone files.

RIPE Seller (Source) Requirements

Who can file: a RIPE NCC member, an End User sponsored through an LIR, or a legacy holder without a contract (the RIPE NCC accepts a separate confirmation letter from legacy holders). The party must be the registered holder and must not be in a dispute over the resources.

Hold period (ripe-807 section 2.2): IPv4 and 16-bit ASNs cannot be transferred for 24 months from the date the holder received them, receipts through a merger or acquisition included; a further merger or acquisition inside the 24 months is the only carve-out. 32-bit ASNs have no hold. Resources under a Voluntary Transfer Lock cannot move before the lock's end date.

Money and screening: every annual contribution on the member's LIR accounts must be paid before a transfer (RIPE NCC Billing Procedure 2026). The RIPE NCC screens all signing parties and authorized representatives against Dutch and EU sanctions lists (ripe-863).

Resource: minimum /24, publicly routable, not special-use or reserved. Verify the registration date and holder in the RIPE Database before quoting a hold date.

Authorization:

• A director authorized to sign the transfer for the holder
• Contact information current in the RIPE Database

Eligibility rules for every RIR pair: Inter-RIR Transfer Eligibility by Region.

ARIN Buyer (Recipient) Requirements

Organization status:

• An active business entity legally formed within the ARIN service region (ARIN)
• ARIN Online account established
• Registration Services Agreement (RSA): signed for the transferred resources within 90 days of approval, unless one is already on file (NRPM 8.5.1)

Needs test: a first /24 needs no justification when the recipient holds no IPv4 allocation from ARIN (NRPM 8.5.4). A larger initial block, or any additional block, needs documentation showing at least 50% of the requested block in use within 24 months (8.5.5). An existing ARIN holder must also show 50% use of its previous blocks (8.5.6) or 80% utilization (8.5.7, up to a /16 in any six months). A recipient on the ARIN waitlist is removed from it and cannot reapply for 90 days (8.4).

Pre-approval (optional):

• Worth filing when you need more than a /24 or already hold IPv4 from ARIN
• Submitted in ARIN Online before you buy
• Valid for two years (ARIN)
• Gives you the approved size before you commit to a purchase

Fees (ARIN 2026 fee schedule): Recipient Transfer Processing Fee, paid on approval, $187.50 for a /24, $375 up to a /22, $750 up to a /20. Registration Services Plan fee per year, $275 for a /24 (3X-Small), $550 up to a /22, $1,100 up to a /20. Org ID creation costs $50 if the organization is new to ARIN. Source: ARIN fee schedule. ARIN's $500 transfer request fee is billed to sources in the ARIN region only, so it does not apply here.

Step-by-Step Transfer Process

Phase 1: ARIN Pre-Approval (Recommended)

Step 1: Establish ARIN Account

Create and verify your ARIN Online account:

Account creation:

• Visit www.arin.net and create an account
• Provide accurate organization information
• Check that the legal entity name matches the company registration exactly
• Complete email verification

Organization setup:

• Enter complete organization details
• Add authorized Points of Contact (POC)
• Designate Admin and Tech POCs
• Verify all contact information

Verification:

• ARIN may request organization verification documents
• Provide articles of incorporation or equivalent
• The business must be an active entity legally formed within the ARIN service region

Step 2: Submit Pre-Approval Request

Pre-approval establishes your eligibility to receive transfers before you commit to a purchase. Submit a transfer pre-approval request in ARIN Online (the menu labels change; follow ARIN's pre-approval guide).

Required information:

• Estimated resource size needed
• Detailed network infrastructure description
• Current IP address utilization (if applicable)
• 24-month deployment plan

Network plan details to include:

• Infrastructure type (hosting, ISP, enterprise network, etc.)
• Geographic deployment area
• Number of customers or services
• Growth projections with supporting data
• Current resource utilization rates
• Technical rationale for IPv4 requirement

Supporting documentation:

• Network topology diagrams
• Infrastructure deployment schedule
• Customer contracts or letters of intent
• Current IP usage reports
• Business plan excerpts showing growth

Submit:

• Review all information for accuracy
• Submit pre-approval request

Step 3: ARIN Pre-Approval Review

ARIN evaluates your needs justification.

Review process:

• ARIN staff review submitted justification
• May request additional information or clarification
• Evaluate 24-month needs against NRPM policies
• Verify regional presence and operational legitimacy

Timeline: ARIN says it answers pre-approval requests within two business days and each follow-up question within two days; a request with no reply for 90 days is closed (ARIN).

Possible outcomes:

• Approved: Receive approval for specific resource amount
• Conditional approval: Approved for different amount than requested
• Request for additional information: Provide more details
• Denied: Insufficient justification (can resubmit with stronger case)

Approval validity:

• Pre-approval valid for two years
• Can be used for multiple transfers up to approved amount
• Must be used before expiration

Phase 2: Identify and Secure Resources

Step 4: Find IPv4 Resources

Locate suitable RIPE-registered IPv4 addresses.

Direct purchase:

• Contact IPv4 holders directly
• Verify seller legitimacy

Neither registry lists blocks for sale any more. ARIN retired its Specified Transfer Listing Service on 1 June 2023 and publishes a list of Qualified Facilitators instead. The RIPE NCC removed its Recognised IPv4 Transfer Brokers List on 31 December 2023 and decommissioned its IPv4 Transfer Listing Service in early 2024 (RIPE NCC).

Due diligence:

• Verify resources are registered in RIPE database (whois.ripe.net)
• Confirm seller is registered holder
• Check hold period has been met (24 months)
• Verify resources are not blacklisted or have reputation issues
• Confirm no disputes or liens exist

Negotiate terms:

• Agree on price and payment terms
• Determine transfer timeline
• Establish escrow arrangements if used
• Agree who pays ARIN's recipient fees (the RIPE NCC charges nothing)

Step 5: Verify Resource Eligibility

Confirm the IPv4 resources meet all requirements.

RIPE database verification:

whois -h whois.ripe.net [IP-RANGE]

Check for:

• Current registration holder matches seller
• Allocation or last transfer date (must be 24+ months ago)
• Resource status (allocated, assigned)
• No special designations or restrictions

ARIN compatibility check:

• Resources are within transferrable ranges
• Minimum /24 size maintained
• CIDR boundary alignment
• Not IPv6: ARIN accepts no IPv6 in transfers between registries

Phase 3: Execute Transfer Agreement

Step 6: Prepare Transfer Agreement

Create legal agreement between buyer and seller.

Agreement should include:

• Buyer and seller legal entity details
• Specific IPv4 address range(s)
• Purchase price and payment terms
• Transfer timeline and milestones
• Responsibility for RIR fees
• Representations and warranties
• Conditions precedent (RIR approvals)
• Escrow arrangements (if used)

Legal review:

• Have agreement reviewed by legal counsel
• Check compliance with applicable laws
• Verify signatures have proper authority
• Include dispute resolution provisions

Escrow setup (optional but recommended):

• Use specialized IPv4 escrow service
• Deposit funds before initiating transfer
• Release upon transfer completion
• Fee negotiated with the escrow agent

Phase 4: Initiate Transfer with RIPE

Step 7: Seller Submits Transfer Request to RIPE

The RIPE seller initiates the transfer process. The RIPE NCC's procedure (ripe-769, inter-RIR page):

• Complete the RIPE NCC's inter-RIR template and e-mail it to inter-rir@ripe.net
• Legal persons: a recent registration document from the national authorities. Natural persons: a passport or other valid ID, verified through iDenfy
• A confirmation letter of the transfer request, signed by a company director authorized to act for the holder
• Legacy holders without a contract with the RIPE NCC or a sponsoring LIR: the RIPE NCC's separate confirmation letter instead
• The RIPE NCC starts evaluating as soon as the documents arrive

Use the RIPE NCC's own template: it is the only one the RIPE NCC accepts.

Step 8: RIPE Review and Approval

RIPE NCC evaluates the transfer request.

RIPE verification process:

• Confirm source organization is registered holder
• Verify 24-month hold period is met
• Check organization is current with obligations
• Validate documentation completeness
• Check resources are eligible for transfer

Timeline: the RIPE NCC says most transfers complete within one or two business days once the documents are in order (RIPE NCC transfers); the ARIN evaluation that follows is separate.

Possible RIPE requests:

• Additional documentation
• Clarification on organization details
• Updated company registration papers
• Confirmation of no disputes

RIPE approval: Once approved, the RIPE NCC notifies ARIN, which starts its own evaluation and contacts the recipient.

Phase 5: ARIN Processing

Step 9: Submit Transfer Request in ARIN Online

Only the recipient files in ARIN Online: ARIN requires 8.4 requests from a POC of the organization in the ARIN region. The RIPE holder's side stays with the RIPE NCC.

Buyer actions in ARIN Online:

Access transfer section:

• Log into ARIN Online
• Select "Transfer Resources" from navigation
• Open an 8.4 transfer request as the recipient

Enter transfer details:

• Specify IPv4 address range(s)
• Provide source organization details
• Confirm pre-approval number (if obtained)

Upload documentation:

• Transfer agreement (if required)
• Needs justification (if not pre-approved)
• Supporting network documentation
• Authorization letters

Fees: the $187.50 recipient processing fee for a /24 (2026 schedule) is due on approval, before ARIN registers the block; the yearly RSP fee follows.

Step 10: ARIN Needs Assessment

A first /24 for an organization with no IPv4 from ARIN passes without documentation (NRPM 8.5.4); the assessment below applies to larger or additional blocks.

If pre-approved:

• ARIN verifies pre-approval is valid and current
• Confirms transfer amount is within approved limits

If not pre-approved:

• ARIN conducts full needs assessment
• Reviews submitted justification documentation
• May request additional information
• Evaluates 24-month needs per NRPM policies

Assessment criteria:

• Realistic deployment timeline
• Adequate infrastructure support
• Appropriate resource size for demonstrated need
• Compliance with ARIN policies
• Operational presence in ARIN region

Timeline: ARIN publishes no figure for the assessment itself.

Step 11: ARIN Requests Certification from RIPE

ARIN contacts RIPE to confirm policy compatibility.

ARIN verification with RIPE:

• Confirms transfer is compatible with needs-based policies
• Verifies RIPE has approved the transfer
• Coordinates transfer execution timing
• Exchanges technical details

Both RIRs coordinate:

• Timing of database updates
• WHOIS synchronization
• Routing database coordination
• Transfer execution date

Phase 6: Transfer Execution

Step 12: Sign ARIN Registration Services Agreement

If not already signed, complete ARIN RSA.

RSA requirements:

• Review Registration Services Agreement terms
• Sign electronically through ARIN Online
• An authorized signatory signs for the organization
• Agreement binds organization to ARIN policies
• Due within 90 days of approval; not needed when a current RSA is on file (NRPM 8.5.1)

Step 13: Pay ARIN Fees

Complete payment for ongoing maintenance.

Fee structure:

ARIN bills one Registration Services Plan fee per organization, set by its largest holding across IPv4, IPv6 and ASNs (2026 fee schedule): /24 or smaller $275 (3X-Small, $288.75 from 2027); more than a /24 up to a /22 $550; up to a /20 $1,100; up to a /18 $2,205; up to a /16 $4,410. Fees are in USD, non-refundable and not prorated.

Payment:

• Set up payment method in ARIN Online
• Pay the RSP fee when ARIN invoices it
• Establish automatic renewal (optional)

Step 14: RIRs Execute Transfer

Both registries coordinate to complete the transfer.

RIPE actions:

• De-registers resources from source organization
• Updates RIPE WHOIS database
• Marks resources as transferred to ARIN region
• Deletes the related RIPE Database objects, domain objects included, and removes the reverse delegation on the transfer date
• Issues transfer confirmation

ARIN actions:

• Registers the block (or ASN) to the recipient's Org ID in ARIN Whois
• If the recipient already has an ARIN RPKI certificate, extends it to the new resources automatically

Coordination:

• Both RIRs synchronize timing
• Minimize WHOIS gaps or overlaps
• Coordinate routing database updates
• Execute transfer simultaneously

Timeline: ARIN says the resources move within two business days once it holds the signed RSA and the fees; both registries update on the date they agree.

Phase 7: Post-Transfer Actions

Step 15: Update Routing Information

Seller, before the transfer date (ARIN's source checklist and the RIPE NCC procedure):

• Edit or delete the ROAs covering the block in the RIPE NCC RPKI dashboard; check maxLength on the ROAs that remain
• Remove the route objects and domain objects for the block in the RIPE Database; the RIPE IRR only holds route objects for RIPE-region prefixes, so they cannot stay
• Agree a reverse DNS plan with the recipient: the RIPE NCC removes the reverse delegation on the transfer date
• Tell the upstreams the origin will change (a buyer normally announces from its own ASN)

Recipient, from the transfer date:

• Create ROAs in ARIN's hosted RPKI (an existing ARIN certificate extends to the block automatically)
• Create route objects in ARIN's IRR from ARIN Online, see Route Objects Explained
• Request reverse DNS delegation at ARIN at once
• Check prefix and origin with the RPKI checker before announcing

Create the ROA before you announce. While a ROA for the old origin still covers the block, an announcement from the new ASN is RPKI-invalid and validating networks drop it; once no ROA covers the block the route is only 'not found', accepted but unprotected.

Step 16: Verify Transfer Completion

Confirm all aspects of transfer are complete.

WHOIS verification:

# Check ARIN WHOIS
whois -h whois.arin.net [IP-RANGE]

# Verify removed from RIPE
whois -h whois.ripe.net [IP-RANGE]

Confirmation checklist:

• Resources appear in ARIN WHOIS with correct org details
• Resources removed from RIPE WHOIS database
• Block listed under your Org ID in ARIN Online
• ARIN account shows resources
• Routing information updated
• ROA records validated
• Reverse DNS delegated at ARIN

Step 17: Release Escrow (if used)

If using escrow services, complete the release.

Escrow release conditions:

• Transfer confirmed complete in both RIRs
• WHOIS updated correctly
• Recipient has control of resources
• All parties satisfied with completion

Release process:

• Buyer confirms receipt of resources
• Escrow agent verifies transfer completion
• Funds released to seller
• Final documentation distributed

Step 18: Maintain Ongoing Compliance

Keep meeting ARIN's requirements after the transfer.

Annual obligations:

• Pay ARIN maintenance fees on time
• Keep WHOIS data current and accurate
• Respond to ARIN communications promptly
• Update POC information when changes occur

Utilization requirements:

• Deploy resources according to justification
• Maintain documentation of usage
• Be prepared for potential ARIN audits

Transfer restrictions:

• For 12 months after receiving IPv4 through ARIN (transfer or allocation), you cannot be the source of another 8.3 or 8.4 transfer, unless both parties are under common ownership or control (NRPM 8.4)
• If transferring resources out, the source becomes ineligible for the ARIN IPv4 waitlist for 36 months

Timeline and Milestones

A RIPE to ARIN transfer runs in this order:

1. ARIN pre-approval, if you need more than a first /24
2. Resource identification, due diligence and purchase agreement
3. Seller's request to the RIPE NCC and its review
4. Recipient's request in ARIN Online and ARIN's evaluation
5. RSA signature, ARIN fees and execution by both registries
6. Routing, RPKI and reverse DNS clean-up, escrow release

Only three durations are published. The RIPE NCC completes most transfers within one or two business days once the documents are complete. ARIN answers pre-approval requests within two business days and moves the resources within two business days once it holds the signed RSA and the fees; for the 8.4 evaluation itself it says the time "can vary". Everything else in this section is sequence, not duration: see Inter-RIR Transfer Timeline and Approval Process for what the whole chain looks like in practice.

RIPE to ARIN transfers in numbers

The RIPE NCC publishes every transfer (ripe-807 section 4). Its transfer file lists 70 IPv4 transfers from the RIPE NCC to ARIN in 2025 (1,113,856 addresses) and 26 in 2026 up to 25 September (1,274,368 addresses), plus 10 ASN transfers in 2025 and 8 in 2026. The main flow runs the other way: 374 IPv4 transfers from ARIN into the RIPE region in 2025 (10,134,528 addresses). Source: RIPE NCC inter-RIR transfer statistics, file of 25 September 2026; ARIN statistics and the NRO publish the other side.

Common Issues and Solutions

Issue 1: Pre-Approval Denied

Problem: ARIN denies pre-approval due to insufficient justification.

Solutions:

• Check whether you needed pre-approval at all: a first /24 for an organization without ARIN IPv4 needs no justification (NRPM 8.5.4)
• Request specific feedback on deficiencies
• Strengthen network documentation with diagrams
• Provide more detailed utilization plans
• Include customer contracts or letters of intent
• Reduce requested resource amount
• Show higher utilization of existing resources
• Resubmit with enhanced documentation

Issue 2: RIPE Hold Period Not Met

Problem: Resources haven't been registered in RIPE for 24 months.

Solutions:

• Verify exact allocation/transfer date from RIPE database
• Wait until 24-month period is complete
• Consider alternative resource sources
• The only carve-out is a further merger or acquisition inside the 24 months (ripe-807 section 2.2)

Issue 3: Documentation Rejected

Problem: RIPE or ARIN rejects submitted documentation.

Solutions:

• Send a recent registration document (the RIPE NCC's word; it asks for a new one when the copy is old)
• Verify company name matches exactly across all documents
• Get proper authorization level signatures (director/officer)
• Use official company letterhead
• Translate documents if needed
• Resubmit with corrected documentation

Issue 4: Needs Assessment Challenges

Problem: ARIN questions the 24-month needs justification.

Solutions:

• Provide more detailed infrastructure plans
• Include specific use cases and customer data
• Show realistic growth projections
• Document current utilization rates
• Consider requesting smaller amount
• Engage ARIN's Registration Services for guidance

Issue 5: Routing Transition Problems

Problem: Routing issues during or after transfer.

Solutions:

• Coordinate with upstream providers before transfer
• Update ROA records proactively
• Maintain BGP announcements during transition
• Monitor routing tables globally
• Request reverse DNS at ARIN on the transfer date: the RIPE delegation is gone that day
• Use looking glass services to verify propagation
• Contact RIRs if WHOIS issues occur

More refusal causes across RIR pairs: Common Inter-RIR Transfer Rejections.

How much does a RIPE to ARIN transfer cost?

Registry fees (ARIN 2026 fee schedule; the RIPE NCC charges nothing):

• Recipient Transfer Processing Fee, on approval: $187.50 for a /24, $375 up to a /22, $750 up to a /20, $1,500 up to a /18, $3,000 up to a /16
• Registration Services Plan fee, yearly: $275 for a /24 (3X-Small, $288.75 from 2027), $550 up to a /22, $1,100 up to a /20, $2,205 up to a /18, $4,410 up to a /16
• Org ID creation, once: $50 if the recipient is new to ARIN
• ARIN's $500 transfer request fee: sources in the ARIN region only, not this direction
• RIPE NCC membership, if the seller keeps its LIR account: €1,800 per year under the Charging Scheme 2026 (ripe-848), €1,894 from 2027 (ripe-867); a closure request filed before 31 December avoids the next year's fee

Purchase price: broker IPv4.Global reports monthly averages of about $23.50 per address for /22 to /24 blocks and about $17.00 for /20 to /21 blocks in August 2026 (prices at agreement date, online and private sales mixed). A /24 therefore costs about $6,000. Whether buying beats leasing for your case: IPv4 Leasing vs Purchasing (2026): Cost Analysis and Break-Even.

Deal costs without a public rate: legal review, broker commission, escrow and translation are negotiated per deal; no registry sets them.

First-year example, one /24, recipient new to ARIN (August 2026 prices, 2026 fees):

• Block: about $6,000
• ARIN recipient processing fee: $187.50
• ARIN Registration Services Plan, 2026: $275
• ARIN Org ID creation: $50
• RIPE NCC: €0
• Registry fees on top of the price: $512.50 ($462.50 for an organization that already has an Org ID)

Best Practices for Successful Transfers

1. Obtain ARIN Pre-Approval First

Pre-approval is worth filing when you need more than a /24; Step 2 covers it.

2. Verify Resource Reputation

Check the block against blacklists such as Spamhaus and SpamCop before you pay. Review its BGP history and any previous abuse reports, or use a reputation checking service to do it.

3. Use Escrow for Security

Escrow protects both parties. A neutral agent holds the buyer's money until the transfer completes, and the seller knows the funds are there before filing.

4. Plan Routing Updates Early

Routing clean-up on both sides starts before the transfer date; Step 15 lists it.

5. Maintain Complete Documentation

Keep every registry e-mail, the signed agreement, payment records and a Whois capture at each stage. Log routing changes and the date each milestone was reached.

6. Work with Experienced Professionals

Outside help is worth considering for first transfers, blocks of a /16 or larger, complex justifications and tight deadlines. Deals with several parties and legacy resources belong on the same list.

Via-Registry RIPE to ARIN Transfer Support

We check eligibility on both sides, prepare the RIPE NCC and ARIN paperwork and coordinate the two registries until the block shows under the recipient's Org ID. Transfers are quoted per case: tell us about your inter-RIR transfer.

Summary

The RIPE holder files first, with the RIPE NCC's template and its documents, and the RIPE NCC usually clears its side in one or two business days at no charge. ARIN then vets the recipient: a first /24 passes without justification, anything larger needs 50% use within 24 months, and the recipient pays $187.50 on approval plus $275 a year for a /24 on the 2026 schedule. The step most often forgotten is the clean-up: ROAs and route objects deleted on the RIPE side before the date, ROAs, IRR entries and reverse DNS created at ARIN on the date.