RIPE to ARIN Transfer Step-by-Step

Transferring IPv4 addresses from the RIPE NCC service region to the ARIN region is one of the most common inter-RIR transfers due to strong market demand in North America. This comprehensive guide walks you through every step of the RIPE to ARIN transfer process, from initial preparation to final completion.

Transfer Overview

RIPE to ARIN transfers involve moving IPv4 address resources from Europe, the Middle East, or Central Asia to North America. The process requires coordination between both registries and compliance with both RIPE and ARIN policies.

Key characteristics:

• Typical timeline: 4-6 weeks with complete documentation
• Requires ARIN pre-approval or needs justification
• RIPE 24-month hold period must be met
• ARIN 24-month needs assessment required
• Both RIRs must approve the transfer
• Minimum transfer size: /24 (256 addresses)

For background on inter-RIR transfers and general requirements, see our Inter-RIR Transfer Process Explained guide.

Pre-Transfer Requirements

Before initiating the transfer, ensure both parties meet all eligibility requirements.

RIPE Seller (Source) Requirements

Organization status:

• Current RIPE NCC LIR member or have resources registered through sponsoring LIR
• Registered holder of the IPv4 resources in RIPE database
• Current with all RIPE NCC obligations and fees
• No disputes or liens on the resources

Hold period verification:

• Resources must have been registered for at least 24 months
• Clock starts from allocation date or last transfer date
• Verify exact dates in RIPE database
• Cannot transfer resources more frequently than every 24 months

Resource verification:

• Minimum size: /24 (256 addresses)
• Must be publicly routable IPv4 space
• Cannot be special-use or reserved addresses
• Legacy resources require additional verification

Authorization:

• Legal representative authorized to execute transfer
• Access to RIPE NCC portal
• Contact information current in RIPE database

ARIN Buyer (Recipient) Requirements

Organization status:

• Legal entity registered in ARIN region (US, Canada, Caribbean)
• Physical operational presence in ARIN service area
• ARIN Online account established
• Registration Services Agreement (RSA) signed or ready to sign

Needs assessment preparation:

• Demonstrate need for 24-month supply of IPv4 addresses
• Detailed network infrastructure documentation
• Current IP utilization data (if applicable)
• Realistic deployment timeline

Pre-approval option (highly recommended):

• Submit pre-approval request to ARIN before initiating transfer
• Valid for 24 months from approval date
• Significantly reduces transfer processing time
• Provides certainty before committing to purchase

Financial readiness:

• $500 non-refundable transfer processing fee
• Annual maintenance fees ($150-$500 based on resource size)
• Payment method established in ARIN account

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 account
• Provide accurate organization information
• Ensure legal entity name matches 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
• Ensure business is registered in ARIN region (US/Canada/Caribbean)

Step 2: Submit Pre-Approval Request

Pre-approval establishes your eligibility to receive transfers before you commit to a purchase.

Access the pre-approval form:

• Log into ARIN Online
• Navigate to "Transfer Resources" section
• Select "Submit Pre-approval Request"

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 and pay fee:

• Review all information for accuracy
• Submit pre-approval request
• Pay processing fee if required

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: 1-2 weeks for initial review

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 24 months
• 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
• Identify available resources through RIR transfer listings
• Verify seller legitimacy

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
• Define responsibilities for transfer costs

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 in ARIN reserved or special-use ranges

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
• Ensure 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
• Typically 1-3% of transaction value

Phase 4: Initiate Transfer with RIPE

Step 7: Seller Submits Transfer Request to RIPE

The RIPE seller initiates the transfer process.

Prepare documentation:

• Company registration documents (recent, official)
• Letter of authorization from company director
• Confirmation of transfer intent
• Details of recipient organization and ARIN

Submit request to RIPE:

• Email to: inter-rir@ripe.net
• Subject: Inter-RIR Transfer Request - [IP Range]
• Include all required documentation
• Specify recipient details and destination RIR (ARIN)

Email template:

To: inter-rir@ripe.net
Subject: Inter-RIR Transfer Request - [IP-RANGE]

Dear RIPE NCC,

We request to transfer the following IPv4 resources to the ARIN region:

IP Range: [specify exact range]
Source Organization: [RIPE Org-ID]
Destination Organization: [company name]
Destination RIR: ARIN

[Attach required documentation]

Sincerely,
[Authorized Representative]

Required attachments:

• Recent company registration papers
• Signed confirmation letter from authorized director
• Transfer agreement (if requested)
• Any additional RIPE-requested documents

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
• Ensure resources are eligible for transfer

Timeline: 5-10 business days for RIPE review

Possible RIPE requests:

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

RIPE approval: Once satisfied, RIPE approves the transfer on their end and contacts ARIN to coordinate.

Phase 5: ARIN Processing

Step 9: Submit Transfer Request in ARIN Online

Both source and recipient must submit requests in ARIN Online.

Seller actions in ARIN Online: Even though resources are in RIPE, the seller (or their representative) must submit confirmation in ARIN Online:

• Log into ARIN Online
• Navigate to "Transfer Resources"
• Select "Inter-RIR Transfer"
• Provide resource details and recipient information

Buyer actions in ARIN Online:

Access transfer section:

• Log into ARIN Online
• Select "Transfer Resources" from navigation
• Choose "Inter-RIR Transfer - Recipient"

Enter transfer details:

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

Upload documentation:

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

Pay processing fee:

• $500 non-refundable transfer processing fee
• Pay via credit card or electronic payment
• Receipt generated automatically

Step 10: ARIN Needs Assessment

ARIN evaluates the recipient's justification.

If pre-approved:

• ARIN verifies pre-approval is valid and current
• Confirms transfer amount is within approved limits
• Minimal additional review required
• Significantly faster processing

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: 1-2 weeks with pre-approval; 2-4 weeks without

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
• Ensure authorized signatory executes agreement
• Agreement binds organization to ARIN policies

Officer attestation:

• Provide notarized Officer Acknowledgement Letter
• Officer must have legal authority to bind organization
• Confirms understanding of terms and restrictions

Step 13: Pay ARIN Fees

Complete payment for ongoing maintenance.

Fee structure:

• Annual maintenance based on resource size
• /24 to /20: $150/year
• /19 to /16: $250/year
• /15 to /12: $500/year
• Larger blocks: Higher tiers

Payment:

• Set up payment method in ARIN Online
• Pay first year upon transfer completion
• 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
• Issues transfer confirmation

ARIN actions:

• Registers resources to recipient organization
• Updates ARIN WHOIS database
• Creates routing database entries
• Issues registration certificates

Coordination:

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

Timeline: Transfer execution typically occurs within 1-2 business days of final approvals

Phase 7: Post-Transfer Actions

Step 15: Update Routing Information

Critical step to maintain connectivity and routing.

Before transfer execution:

• Notify upstream providers of pending change
• Prepare BGP configuration updates
• Update Route Origin Authorization (ROA) records
• Plan routing cutover timeline

After transfer completion:

• Update BGP announcements with ARIN registration info
• Modify ROA records in RPKI system
• Verify routing propagation globally
• Monitor for routing issues

ROA update process:

• Delete existing ROAs in RIPE system
• Create new ROAs in ARIN system
• Use ARIN's hosted RPKI or delegated RPKI
• Verify ROA validation

BGP considerations:

• BGP announcements can continue unchanged (same ASN)
• Update WHOIS references to ARIN
• Coordinate with peers and upstreams
• Monitor routing tables for propagation

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
• Registration certificate received from ARIN
• ARIN account shows resources
• Routing information updated
• ROA records validated

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

Ensure continued compliance with ARIN requirements.

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
• Ensure efficient utilization

Transfer restrictions:

• Cannot transfer resources out of ARIN for 12 months
• Subject to ARIN policies on subsequent transfers

Timeline and Milestones

Typical RIPE to ARIN transfer timeline with complete documentation:

Week 1-2: Pre-Approval (if used)

• Submit ARIN pre-approval request
• ARIN review and approval

Week 1: Resource Identification and Agreement

• Identify resources
• Due diligence
• Negotiate and execute purchase agreement

Week 2: RIPE Initiation

• Seller submits request to RIPE
• RIPE reviews documentation
• RIPE approves on their end

Week 3-4: ARIN Processing

• Submit requests in ARIN Online
• ARIN needs assessment (faster if pre-approved)
• ARIN-RIPE coordination
• Final approvals

Week 4-5: Transfer Execution

• Sign ARIN RSA
• Pay ARIN fees
• RIRs execute transfer
• Databases updated

Week 5-6: Post-Transfer

• Update routing information
• Verify completion
• Release escrow
• Finalize documentation

Total typical timeline: 4-6 weeks

Factors that extend timeline:

• No pre-approval: Add 1-2 weeks
• Incomplete documentation: Add 1-3 weeks
• Complex justification: Add 1-2 weeks
• First-time transfer: Add 1-2 weeks
• Holiday periods: Variable delays

Common Issues and Solutions

Issue 1: Pre-Approval Denied

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

Solutions:

• 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
• Work with consultant to improve justification
• 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
• Check if any hold period exceptions apply

Issue 3: Documentation Rejected

Problem: RIPE or ARIN rejects submitted documentation.

Solutions:

• Ensure company registration is recent (within 3-6 months)
• Verify company name matches exactly across all documents
• Get proper authorization level signatures (director/officer)
• Obtain notarization where required (ARIN)
• 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
• Reference industry standards
• 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
• Have rollback plan ready
• Use looking glass services to verify propagation
• Contact RIRs if WHOIS issues occur

Cost Breakdown

Complete cost analysis for RIPE to ARIN transfer:

ARIN Fees

One-time costs:

• Transfer processing fee: $500
• Legal review (optional): $1,000-$5,000
• Consultant/broker (optional): $2,000-$10,000 or 3-10% of value

Annual ongoing costs:

• Maintenance fee: $150-$500/year (based on size)
• RIPE membership (if maintaining): €1,400/year (can cancel if no remaining resources)

Transaction Costs

IPv4 purchase price:

• Market rate per IP: $30-$55 (varies by market conditions)
• /24 (256 IPs): $7,680-$14,080
• /22 (1,024 IPs): $30,720-$56,320
• /20 (4,096 IPs): $122,880-$225,280

Additional costs:

• Escrow service: 1-3% of transaction value
• Wire transfer fees: $25-$50
• Translation services (if needed): $200-$500
• Notarization (ARIN docs): $10-$25 per document

Total first-year cost example (/24 purchase):

• IPv4 purchase: $10,000 (est.)
• ARIN processing: $500
• ARIN annual fee: $150
• Escrow: $200 (2%)
• Misc fees: $100
• Total: ~$10,950

Best Practices for Successful Transfers

1. Obtain ARIN Pre-Approval First

Benefits of pre-approval:

• Certainty before committing to purchase
• Faster transfer processing
• Reduced risk of denial
• Valid for 24 months
• Can be used for multiple transfers

2. Verify Resource Reputation

Before purchasing:

• Check blacklists (Spamhaus, SpamCop, etc.)
• Review BGP history
• Check for previous abuse reports
• Verify clean reputation
• Consider reputation checking services

3. Use Escrow for Security

Escrow protects both parties:

• Buyer protected until transfer completes
• Seller ensured of payment
• Neutral third party manages funds
• Professional escrow services available
• Minimal cost for significant protection

4. Plan Routing Updates Early

Routing coordination:

• Notify providers weeks in advance
• Prepare configuration changes
• Update ROA records proactively
• Schedule change window
• Have rollback plan ready
• Monitor post-transfer

5. Maintain Complete Documentation

Document everything:

• All RIR communications
• Transfer agreements
• Payment records
• WHOIS records at each stage
• Routing configuration changes
• Timeline and milestone tracking

6. Work with Experienced Professionals

Consider professional help for:

• First-time transfers
• Large transfers (>=/16)
• Complex justifications
• Tight timelines
• Multiple-party transactions
• Legacy resources

Via-Registry RIPE to ARIN Transfer Support

Via-Registry specializes in RIPE to ARIN transfers and can streamline the entire process:

Pre-transfer services:

• Eligibility verification
• ARIN pre-approval assistance
• Resource sourcing and due diligence
• Justification preparation

Transfer management:

• Complete coordination with RIPE and ARIN
• Documentation preparation and submission
• Timeline management
• Status tracking and updates

Technical support:

• Routing transition planning
• ROA update assistance
• BGP coordination
• Post-transfer verification

Ongoing support:

• ARIN compliance maintenance
• Annual fee management
• WHOIS updates
• Resource management

Get started with our Inter-RIR Transfer Service for expert guidance through your RIPE to ARIN transfer.

Summary

RIPE to ARIN transfers follow a well-established process:

Key steps:

1. Obtain ARIN pre-approval (recommended)
2. Identify and verify RIPE resources
3. Execute purchase agreement
4. Seller initiates with RIPE
5. Submit requests in ARIN Online
6. ARIN needs assessment
7. RIRs coordinate and execute transfer
8. Update routing information
9. Verify completion

Critical requirements:

• RIPE: 24-month hold period
• ARIN: 24-month needs justification
• Minimum: /24 (256 addresses)
• Timeline: 4-6 weeks typical
• Cost: $500 ARIN fee + $150+ annual

Success factors:

• Pre-approval before purchasing
• Complete documentation
• Strong needs justification
• Professional routing coordination
• Adequate timeline allowance