ARIN to RIPE Transfer Requirements

Transferring IPv4 addresses from ARIN to the RIPE NCC service region has unique characteristics compared to other inter-RIR transfers. The key difference is RIPE's more flexible 50% utilization requirement over 5 years, rather than the stricter 24-month justification. This comprehensive guide covers all requirements and steps for successful ARIN to RIPE transfers.

Transfer Overview

ARIN to RIPE transfers move IPv4 resources from North America to Europe, the Middle East, or Central Asia. These transfers are popular for European organizations expanding operations or seeking IPv4 resources in the international market.

Key characteristics:

• Typical timeline: 4-6 weeks with complete documentation
• RIPE requires 50% utilization plan over 5 years
• ARIN requires 12-month hold period
• ARIN imposes 36-month waitlist restriction on source
• Both RIRs must approve the transfer
• Minimum transfer size: /24 (256 addresses)

For general inter-RIR transfer information, see our Inter-RIR Transfer Process Explained guide.

Understanding the Key Difference: RIPE's 50% Requirement

The most significant aspect of ARIN to RIPE transfers is RIPE's unique needs assessment approach for inter-RIR transfers from needs-based RIRs.

The 50% Over 5 Years Rule

RIPE's requirement: When receiving IPv4 transfers from RIRs with needs-based policies (like ARIN), recipients must provide a plan to use at least 50% of the transferred resources within 5 years.

Why this is significant:

• Much more flexible than ARIN's 24-month requirement
• Allows for longer-term growth planning
• Easier to justify larger blocks
• Accommodates conservative growth estimates
• Reduces risk of over-justification pressure

What qualifies as "use":

• Active assignment to customers
• Infrastructure deployment
• Service provisioning
• Legitimate operational needs
• Not: Stockpiling, speculation, or hoarding

Comparison to Other Requirements

ARIN's 24-month standard:

• Requires demonstrating need for entire amount within 24 months
• More difficult to justify large blocks
• Higher scrutiny of utilization rates
• Stricter documentation requirements

RIPE's 50%/5-year approach:

• Only need to justify 50% of the block
• 5-year timeframe allows strategic planning
• More realistic for many business models
• Simpler justification preparation

Pre-Transfer Requirements

ARIN Seller (Source) Requirements

Organization status:

• Registered resource holder in ARIN database
• Current with all ARIN obligations and fees
• Valid Registration Services Agreement (RSA) with ARIN
• No outstanding disputes or issues

Hold period verification:

• Must be at least 12 months since receiving the resources from ARIN
• Includes allocations, assignments, or previous transfers
• Clock starts from most recent ARIN transaction date
• Verify exact dates in ARIN Online account

Resource verification:

• Minimum size: /24 (256 addresses)
• Must be publicly routable IPv4 space
• Cannot transfer IPv6 in inter-RIR transfers
• Cannot be special-use or reserved addresses
• Must be clean registration without liens

Officer attestation:

• Signed and notarized Officer Acknowledgement Letter required
• Officer must have legal authority to bind organization
• Acknowledges understanding of transfer terms
• Confirms 36-month waitlist restriction

Post-transfer impact:

• Source cannot apply to ARIN waitlist for 36 months after transfer
• This restriction is automatic and strictly enforced
• Consider carefully before transferring out resources

RIPE Buyer (Recipient) Requirements

Organization status:

• Must have active network element in RIPE NCC service region
• Legal entity established within RIPE region
• RIPE NCC LIR membership or sponsoring LIR arrangement
• Current with RIPE NCC obligations

Regional presence:

• Physical operational presence in RIPE region (Europe/Middle East/Central Asia)
• Active network infrastructure deployed or planned
• Business registered in RIPE service area
• Customers or services in RIPE region

LIR membership options:

• Direct LIR membership: Full RIPE NCC membership (€1,400/year + €2,000 setup)
• Sponsoring LIR: Use service provider like Via-Registry (lower cost alternative)

Needs assessment preparation:

• 5-year business and network plan
• 50% utilization justification
• Infrastructure documentation
• Growth projections

The 50% Utilization Plan: What RIPE Needs

Creating a strong 50% utilization plan is critical for ARIN to RIPE transfers.

Plan Components

1. Business overview:

• Company description and business model
• Current operations in RIPE region
• Services provided or planned
• Customer base and target markets

2. Current infrastructure:

• Existing network deployment
• Current IP address usage (if any)
• Infrastructure locations
• Technical capabilities

3. 5-year growth projection:

• Realistic expansion plans
• Customer acquisition estimates
• Infrastructure deployment timeline
• Geographic expansion within RIPE region

4. IP address utilization schedule:

• Year 1: [X addresses] - [specific use cases]
• Year 2: [X addresses] - [specific use cases]
• Year 3: [X addresses] - [specific use cases]
• Year 4: [X addresses] - [specific use cases]
• Year 5: [X addresses] - [specific use cases]
• Total by Year 5: >50% of transferred block

5. Technical justification:

• Why IPv4 is required (vs. IPv6 only)
• Specific technical use cases
• Customer or service requirements
• Infrastructure architecture

Example Utilization Plan

Scenario: Hosting company receiving /22 (1,024 IPs)

Year 1 (128 IPs, 12.5%):

• Initial infrastructure: 64 IPs
• First 50 customers: 64 IPs

Year 2 (256 IPs, 25% total):

• Additional 100 customers: 128 IPs
• Infrastructure expansion: 128 IPs

Year 3 (384 IPs, 37.5% total):

• 150 new customers: 128 IPs
• Service diversification: 256 IPs

Year 4 (512 IPs, 50% total):

• 200 customers: 128 IPs
• Infrastructure scaling: 384 IPs

Year 5 (640 IPs, 62.5% total):

• 250 customers: 128 IPs
• Full infrastructure: 512 IPs

Result: 62.5% utilization by Year 5 exceeds 50% requirement

Supporting Documentation

Business documentation:

• Business plan excerpts
• Customer contracts or letters of intent
• Revenue projections
• Market analysis for RIPE region

Technical documentation:

• Network topology diagrams
• Infrastructure deployment schedule
• Service architecture documentation
• Current IP utilization (if applicable)

Regional presence proof:

• Office lease or ownership documents
• Business registration certificates
• Utility bills for operational facilities
• Local banking relationships
• Customer contracts in RIPE region

Step-by-Step Transfer Process

Phase 1: Preparation and Documentation

Step 1: Establish RIPE Presence

Ensure you meet RIPE's regional presence requirement.

Required elements:

• Legal entity registered in RIPE region
• Physical office or operational facility
• Active network element (server, router, etc.)
• Business operations in region

Documentation to gather:

• Company registration from European/ME/Central Asian authority
• Office lease or property documentation
• Utility bills showing active operations
• Business licenses or permits

Step 2: Obtain RIPE LIR Status

Choose between direct membership or sponsoring LIR.

Option A: Direct RIPE LIR membership

• Apply at www.ripe.net
• Complete member application
• Pay setup fee (€2,000) and annual fee (€1,400)
• Await approval (typically 1-2 weeks)

Option B: Sponsoring LIR

• Contract with sponsoring LIR provider
• Provide required documentation
• Lower cost than direct membership
• Transfer processed through sponsor

Step 3: Prepare 50% Utilization Plan

Develop comprehensive 5-year plan as detailed above.

Plan structure:

• Executive summary
• Current state assessment
• 5-year projections
• Utilization timeline
• Supporting evidence

Review and refine:

• Ensure realistic and credible projections
• Include specific use cases and numbers
• Tie to business objectives
• Provide supporting documentation

Step 4: Identify and Secure ARIN Resources

Locate suitable IPv4 addresses registered with ARIN.

Source options:

• Direct from ARIN resource holders
• Via transfer facilitation services
• RIR transfer listings

Due diligence:

• Verify registration in ARIN WHOIS (whois.arin.net)
• Confirm seller is registered holder
• Check 12-month hold period is met
• Verify clean reputation (blacklists, spam databases)
• Confirm no disputes or liens

Negotiate agreement:

• Price and payment terms
• Transfer timeline
• Responsibility for fees
• Escrow arrangements
• Conditions for completion

Phase 2: Initiate Transfer with ARIN

Step 5: ARIN Seller Submits Transfer Request

The ARIN source initiates the transfer.

Access ARIN Online:

• Log in to ARIN Online account
• Navigate to "Transfer Resources"
• Select "Inter-RIR Transfer"

Complete transfer form:

• Specify IPv4 address range
• Provide recipient organization details
• Indicate destination RIR (RIPE NCC)
• Enter contact information for both parties

Upload required documents:

• Officer Acknowledgement Letter (signed and notarized)
• Transfer agreement (if requested)
• Authorization documentation
• Any additional ARIN-requested items

Pay processing fee:

• $500 non-refundable transfer fee
• Pay via credit card or electronic payment

Step 6: ARIN Review Process

ARIN evaluates the transfer request.

ARIN verification:

• Confirm source is registered holder
• Verify 12-month hold period is met
• Check RSA status
• Validate officer attestation
• Review documentation completeness

Timeline: 5-10 business days for ARIN initial review

Possible outcomes:

• Approved: ARIN approves and contacts RIPE
• Request for information: Provide additional details
• Corrections needed: Fix documentation issues
• Denied: Address deficiencies and resubmit

Phase 3: RIPE Processing

Step 7: ARIN Contacts RIPE NCC

Once ARIN approves, they coordinate with RIPE.

Inter-RIR coordination:

• ARIN notifies RIPE of pending transfer
• Provides transfer details and documentation
• Requests RIPE's review and approval
• Coordinates timing for execution

Step 8: Recipient Submits Documentation to RIPE

RIPE will request documentation from the recipient.

RIPE contact: RIPE will typically email the recipient organization directly or work through the LIR/sponsoring LIR.

Submit to RIPE (via LIR portal or email):

• If using sponsoring LIR: Work through your sponsor
• If direct LIR: Submit via RIPE NCC portal

Required documents:

1. Company registration papers:

• Recent (within 6 months) official document
• From national registration authority
• Showing legal entity in RIPE region
• Must match exact legal name in RIPE database

2. Confirmation letter:

• Signed by company director
• On company letterhead
• Confirms request to receive transfer
• Includes specific IP address range
• Authorizes transfer from ARIN

Example confirmation letter:

[Company Letterhead]
[Date]

RIPE NCC
Attn: Registration Services

Subject: Confirmation of Inter-RIR Transfer Request

Dear RIPE NCC,

[Company Name], registered as [RIPE Org-ID], hereby confirms our
request to receive the following IPv4 resources via inter-RIR
transfer from the ARIN region:

IPv4 Range: [specify exact range]
Source Organization: [ARIN organization name]
Source RIR: ARIN

We confirm that we have an active network element in the RIPE NCC
service region and will utilize these resources for our operations
in Europe.

Authorized Signature:
[Name]
[Title]
[Date]

Sincerely,

Via-Registry.com
support@via-registry.com

3. 50% utilization plan:

• 5-year business and network plan
• Detailed utilization timeline
• Supporting business case
• Infrastructure documentation

4. Regional presence documentation:

• Proof of active operations in RIPE region
• Office documentation
• Network infrastructure evidence
• Business registration

Step 9: RIPE Needs Assessment

RIPE evaluates the 50% utilization plan.

RIPE review criteria:

• Legitimate presence in RIPE region verified
• 50% utilization plan is realistic and credible
• Business case supports requested amount
• Documentation is complete and accurate
• Organization meets RIPE policies

Assessment process:

• Review submitted utilization plan
• Evaluate business case plausibility
• Verify regional presence
• Check LIR status and compliance
• May request additional information or clarification

Timeline: 1-2 weeks for RIPE assessment

Possible requests from RIPE:

• More detailed utilization breakdown
• Additional proof of regional presence
• Clarification on business model
• Updated company documents
• Infrastructure evidence

Step 10: RIPE Approval

Once satisfied, RIPE approves the transfer.

RIPE confirmation:

• Approves recipient to receive resources
• Confirms to ARIN readiness to complete transfer
• Coordinates transfer execution timing
• Prepares database updates

Phase 4: Transfer Execution

Step 11: Coordinate Transfer Timing

Both RIRs coordinate to execute simultaneously.

Coordination includes:

• Specific date/time for transfer
• Database update synchronization
• WHOIS timing
• Routing database coordination
• Communication plan

Typical execution window:

• Within 1-2 business days of final approvals
• Both RIRs update simultaneously
• Minimize routing disruption

Step 12: RIRs Execute Transfer

Both registries complete the transfer.

ARIN actions:

• De-registers resources from source organization
• Updates ARIN WHOIS database
• Marks resources as transferred to RIPE region
• Issues transfer confirmation
• Applies 36-month waitlist restriction to source

RIPE actions:

• Registers resources to recipient organization
• Updates RIPE WHOIS database
• Creates routing database entries
• Issues registration certificates
• Confirms transfer completion

Step 13: Verify Transfer Completion

Confirm the transfer is complete in both systems.

WHOIS verification:

# Check RIPE WHOIS
whois -h whois.ripe.net [IP-RANGE]

# Verify removed from ARIN
whois -h whois.arin.net [IP-RANGE]

Confirmation checklist:

• Resources appear in RIPE WHOIS with correct organization
• Resources removed from ARIN WHOIS
• Registration certificate received from RIPE
• RIPE LIR portal shows resources
• All details accurate (organization, contacts, etc.)

Phase 5: Post-Transfer Actions

Step 14: Update Routing Information

Critical for maintaining connectivity.

Before transfer:

• Notify upstream providers
• Prepare BGP configuration updates
• Plan ROA updates
• Coordinate timing

After transfer:

• Update BGP announcements (if needed)
• Modify Route Origin Authorization (ROA) records
• Delete ROAs from ARIN hosted RPKI
• Create ROAs in RIPE NCC hosted RPKI system
• Verify RPKI validation
• Monitor routing globally

RPKI transition: RIPE offers hosted RPKI service or delegated RPKI. Create ROAs for your transferred resources to maintain route security.

Step 15: Complete Payment and Administration

Finalize financial and administrative items.

Escrow release (if used):

• Confirm transfer completion
• Buyer authorizes escrow release
• Funds transferred to seller

RIPE ongoing obligations:

• Maintain LIR membership or sponsoring relationship
• Keep WHOIS data current
• Pay annual fees
• Comply with utilization commitments

ARIN final items:

• Verify source organization records updated
• Confirm 36-month restriction applied
• Close out transfer in ARIN Online

Step 16: Maintain Compliance

Ensure ongoing adherence to commitments.

RIPE requirements:

• Deploy resources according to 5-year plan
• Maintain documentation of usage
• Respond to potential RIPE audits
• Keep utilization records

Documentation to maintain:

• Proof of ongoing deployment
• Customer assignments
• Infrastructure usage
• Growth tracking vs. projections

Timeline and Milestones

Typical ARIN to RIPE transfer timeline:

Week 1: Preparation

• Establish RIPE LIR status
• Prepare 50% utilization plan
• Identify resources
• Execute purchase agreement

Week 2: ARIN Initiation

• Seller submits request to ARIN
• Upload documentation
• Pay ARIN processing fee
• ARIN reviews and approves

Week 3: RIPE Processing

• ARIN contacts RIPE
• Submit documentation to RIPE
• RIPE reviews utilization plan
• RIPE conducts needs assessment

Week 4: Approval and Coordination

• RIPE approves transfer
• Both RIRs coordinate execution
• Finalize timing
• Prepare for database updates

Week 5: Execution

• RIRs execute transfer
• Databases updated
• Verify completion
• Update routing

Week 6: Post-Transfer

• Release escrow
• Update ROAs
• Final verification
• Compliance documentation

Total typical timeline: 4-6 weeks

Common Issues and Solutions

Issue 1: Insufficient 50% Utilization Justification

Problem: RIPE questions whether 50% usage by Year 5 is realistic.

Solutions:

• Provide more detailed breakdown by year
• Include specific customer estimates
• Reference comparable growth in industry
• Add supporting business documentation
• Scale back requested amount if needed
• Show track record of existing utilization
• Include customer letters of intent
• Demonstrate infrastructure capacity

Issue 2: Regional Presence Verification Challenges

Problem: RIPE questions legitimacy of presence in RIPE region.

Solutions:

• Provide multiple forms of presence proof
• Submit utility bills for operational facilities
• Include photos of physical infrastructure
• Show active customer base in region
• Provide business registration certificates
• Document local banking relationships
• Include office lease agreements
• Show employees in region

Issue 3: ARIN Hold Period Not Met

Problem: Resources haven't been with source for 12 months.

Solutions:

• Verify exact date from ARIN Online
• Wait until 12-month period completes
• Consider alternative resource sources
• Check if any exceptions apply

Issue 4: Documentation Issues

Problem: RIPE rejects submitted documentation.

Solutions:

• Ensure company registration is recent (within 6 months)
• Verify exact legal name matches across all documents
• Get proper authorization level (director/officer)
• Use official company letterhead
• Ensure signatures are original
• Provide certified translations if needed
• Double-check all details for accuracy

Issue 5: LIR Membership Delays

Problem: RIPE LIR application taking longer than expected.

Solutions:

• Apply for LIR membership early (before finding resources)
• Use sponsoring LIR for faster processing
• Ensure all LIR application documents are complete
• Respond quickly to RIPE requests
• Consider professional LIR setup assistance

Cost Analysis

Complete cost breakdown for ARIN to RIPE transfer:

One-Time Costs

ARIN fees:

• Transfer processing fee: $500
• Final annual maintenance (prorated): Variable

RIPE fees (if becoming new LIR):

• Setup fee: €2,000 (one-time)
• Or sponsoring LIR fee: €500-€1,500 (varies by provider)

IPv4 purchase:

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

Optional services:

• Transfer broker: 3-10% of transaction value
• Legal review: $1,000-$5,000
• Consultant services: $2,000-$10,000
• Escrow: 1-3% of transaction value

Annual Ongoing Costs

RIPE NCC:

• LIR membership: €1,400/year
• Or sponsoring LIR: €400-€800/year

Total first-year example (purchasing /24):

• IPv4 purchase: $10,000
• ARIN processing: $500
• RIPE setup: €2,000 ($2,200)
• RIPE annual: €1,400 ($1,540)
• Escrow/misc: $300
• Total: ~$14,540

Annual ongoing (subsequent years):

• RIPE membership: €1,400 ($1,540/year)
• Or sponsoring: €400-€800 ($440-$880/year)

Best Practices

1. Prepare Comprehensive 50% Plan

Make it credible:

• Use realistic, conservative estimates
• Provide specific use cases
• Include detailed year-by-year breakdown
• Support with business documentation
• Show track record if possible

2. Document Regional Presence Thoroughly

Multiple forms of proof:

• Physical office documentation
• Active infrastructure evidence
• Business registration
• Customer contracts
• Local relationships
• Employee presence

3. Consider Sponsoring LIR

Benefits:

• Lower cost than direct membership
• Faster processing
• Expert guidance
• Ongoing support
• No setup complexity

4. Plan Routing Transition

Routing coordination:

• Notify providers early
• Update ROAs proactively
• Test routing before transfer
• Monitor post-transfer
• Have rollback plan

5. Maintain Utilization Documentation

Ongoing compliance:

• Track actual deployment vs. plan
• Document customer assignments
• Maintain infrastructure records
• Be prepared for potential audits
• Update RIPE if plans change significantly

Via-Registry ARIN to RIPE Transfer Services

Via-Registry specializes in ARIN to RIPE transfers and offers comprehensive support:

Pre-transfer services:

• Eligibility verification
• 50% utilization plan development
• Resource sourcing and due diligence
• Documentation preparation

Sponsoring LIR:

• Alternative to direct RIPE membership
• Lower cost and faster processing
• Complete transfer coordination
• Ongoing resource management

Transfer management:

• Coordination with both ARIN and RIPE
• Documentation submission and tracking
• Timeline management
• Status updates throughout

Post-transfer support:

• Routing transition assistance
• ROA update coordination
• Compliance maintenance
• Ongoing RIPE relationship management

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

Summary

ARIN to RIPE transfers feature unique requirements:

Key differentiator:

• RIPE's 50% utilization over 5 years (vs. ARIN's 24-month)
• More flexible and easier to justify
• Allows strategic long-term planning

Critical requirements:

• ARIN: 12-month hold period, 36-month waitlist restriction
• RIPE: Active regional presence, 50% utilization plan
• Both: Minimum /24, complete documentation
• Timeline: 4-6 weeks typical

Success factors:

• Strong 50% utilization plan with supporting evidence
• Thorough regional presence documentation
• RIPE LIR membership (direct or sponsored)
• Professional transfer coordination
• Proper routing transition planning