Guide Transfer •

Inter-RIR Transfer Process Explained

A comprehensive guide to transferring IPv4 addresses and ASNs between Regional Internet Registries, covering requirements, timelines, and step-by-step procedures for all RIRs.

Inter-RIR Transfer Process Explained

Inter-Regional Internet Registry (Inter-RIR) transfers allow organizations to transfer IPv4 addresses and Autonomous System Numbers (ASNs) between different RIR service regions. This comprehensive guide explains the entire inter-RIR transfer process, from understanding eligibility requirements to completing successful transfers across regional boundaries.

What is an Inter-RIR Transfer?

An inter-RIR transfer is the movement of Internet number resources (primarily IPv4 addresses and ASNs) from one Regional Internet Registry's service region to another. Unlike intra-RIR transfers that occur within a single RIR's region, inter-RIR transfers involve coordination between two separate registries, each with its own policies, procedures, and requirements.

Key characteristics of inter-RIR transfers:

  • Requires approval from both the source and destination RIRs
  • Must comply with reciprocal, compatible policies between RIRs
  • Involves more documentation and longer processing times than intra-RIR transfers
  • Only available between RIRs with compatible inter-RIR transfer policies

Which RIRs Support Inter-RIR Transfers?

Currently, only four of the five RIRs support inter-RIR transfers:

Participating RIRs

RIPE NCC (Europe, Middle East, Central Asia)

  • Policy: RIPE-769 - Inter-RIR Transfer of Internet Number Resources
  • Supports both IPv4 and ASN transfers
  • Requires 50% utilization plan over 5 years for incoming transfers from needs-based RIRs
  • Contact: inter-rir@ripe.net

ARIN (North America)

  • Policy: NRPM 8.4 - Inter-RIR Transfers to Specified Recipients
  • Supports IPv4 and ASN transfers
  • Requires 24-month needs justification for incoming transfers
  • 12-month hold period before resources can be transferred out
  • 36-month waitlist restriction after transferring resources out

APNIC (Asia-Pacific)

  • Policy: Inter-RIR Transfer of IPv4 Addresses and ASNs
  • Supports IPv4 and ASN transfers
  • Requires 24-month utilization plan for incoming transfers
  • 5-year hold period for resources from the 103/8 free pool

LACNIC (Latin America and Caribbean)

  • Policy: LAC-2019-1 - Inter-regional IPv4 Transfers
  • Supports IPv4 transfers (policy became operational in 2020)
  • 3-year hold period before LACNIC-allocated space can be transferred
  • 1-year re-transfer restriction
  • Minimum transfer size: /24

Non-Participating RIR

AFRINIC (Africa)

  • Currently does not have an inter-RIR transfer policy
  • No resources can be transferred to or from the AFRINIC region
  • Policy proposals (2019-IPv4-002, 2020-GEN-006) are under discussion
  • Only intra-RIR transfers within Africa are permitted

All four participating RIRs prohibit transfers to/from AFRINIC due to the lack of reciprocal policy.

Policy Compatibility and Reciprocity

Inter-RIR transfers can only occur between RIRs with reciprocal, compatible, needs-based policies. This means:

Compatible RIR pairs:

  • RIPE ↔ ARIN
  • RIPE ↔ APNIC
  • RIPE ↔ LACNIC
  • ARIN ↔ APNIC
  • ARIN ↔ LACNIC
  • APNIC ↔ LACNIC

Policy compatibility requirements:

  • Both RIRs must have inter-RIR transfer policies in place
  • Policies must include reciprocal provisions allowing bidirectional transfers
  • Both RIRs must apply needs-based assessment (though requirements may differ)
  • Transfer must comply with both source and destination RIR policies

General Inter-RIR Transfer Requirements

While specific requirements vary by RIR, all inter-RIR transfers share common prerequisites:

Source Organization Requirements

Eligibility criteria:

  • Must be the registered holder of the resources in the source RIR
  • Resources must meet minimum hold period requirements (varies by RIR)
  • Must be current with all contractual obligations to the source RIR
  • Cannot have outstanding disputes regarding the resources
  • Must not be on any RIR restriction lists

Hold periods by RIR:

  • ARIN: 12 months after receiving allocation/transfer
  • RIPE: 24 months after allocation or last transfer
  • APNIC: 5 years for resources from 103/8 pool; otherwise varies
  • LACNIC: 36 months after allocation

Documentation required:

  • Company registration documents
  • Authorization letter from legal representative
  • Proof of current resource registration
  • Officer attestation or notarized acknowledgment (ARIN)

Recipient Organization Requirements

Basic eligibility:

  • Must have active presence in the destination RIR's service region
  • Must be an RIR member or use a sponsoring LIR
  • Must demonstrate legitimate need for the resources
  • Must be current with obligations to the destination RIR
  • Must comply with destination RIR's technical requirements

Needs assessment requirements:

  • ARIN: 24-month justification for IPv4 addresses
  • RIPE: 50% utilization plan over 5 years (for transfers from needs-based RIRs)
  • APNIC: 24-month utilization plan
  • LACNIC: Needs justification per LACNIC policies

Technical Requirements

Minimum transfer sizes:

  • All RIRs: /24 for IPv4 addresses (256 addresses minimum)
  • ASN transfers: Individual ASNs or blocks per RIR policy

Resource requirements:

  • Resources must be validly registered in the source RIR
  • Must not be designated as special-use or reserved space
  • Must be publicly routable address space
  • Legacy resources may have additional requirements

Step-by-Step Inter-RIR Transfer Process

The inter-RIR transfer process involves multiple stages and coordination between both RIRs. Here's the general workflow:

Phase 1: Pre-Transfer Preparation

Step 1: Verify eligibility

  • Confirm resources meet hold period requirements in source RIR
  • Verify recipient has active presence in destination RIR region
  • Check that both RIRs have compatible inter-RIR transfer policies
  • Ensure no disputes or liens on the resources

Step 2: Create or verify RIR accounts

  • Source organization: Active account in source RIR
  • Recipient organization: Active account or LIR sponsor in destination RIR
  • Ensure legal entity names match across all documentation

Step 3: Prepare needs justification (recipient)

  • ARIN recipients: Complete pre-approval request for 24-month needs assessment
  • RIPE recipients: Prepare 5-year 50% utilization plan
  • APNIC recipients: Document 24-month utilization requirements
  • LACNIC recipients: Prepare needs justification per LACNIC policy

Step 4: Gather required documentation

For source organization:

  • Company registration papers from national authorities
  • Letter of authorization from authorized signatory
  • Confirmation of resource ownership
  • Officer attestation (ARIN transfers)

For recipient organization:

  • Company registration documents
  • Network infrastructure documentation
  • Utilization plans and needs justification
  • Contact information for authorized representatives

Phase 2: Initiate Transfer Request

Step 5: Submit request to source RIR

The transfer request is always initiated by the transferring party at the source RIR.

RIPE source:

  • Send request to inter-rir@ripe.net
  • Include both party details and resource information
  • Provide confirmation letter from authorized signatory

ARIN source:

  • Submit through ARIN Online portal
  • Select "Transfer Resources" from navigation menu
  • Pay non-refundable processing fee ($500 for IPv4 transfers)
  • Admin or Tech POC must submit the request

APNIC source:

  • Submit request through MyAPNIC portal
  • Provide transfer documentation
  • Include recipient organization details

LACNIC source:

  • Submit through LACNIC member portal
  • Include both party information
  • Provide required documentation

Step 6: Source RIR review

The source RIR will review the transfer request to ensure:

  • Resources are registered to the source organization
  • Hold period requirements are met
  • Source organization is current with obligations
  • All required documentation is complete and accurate
  • Resources are eligible for transfer

Processing time: 3-10 business days for initial review

Phase 3: Destination RIR Processing

Step 7: Source RIR contacts destination RIR

Once the source RIR approves the transfer, they will formally contact the destination RIR to coordinate the transfer.

Inter-RIR coordination includes:

  • Verification of policy compatibility
  • Confirmation of resource details
  • Exchange of transfer documentation
  • Timeline coordination

Step 8: Recipient submits documentation to destination RIR

The recipient organization must now work with the destination RIR:

For ARIN recipients:

  • Complete needs assessment or pre-approval
  • Sign Registration Services Agreement (RSA)
  • Pay transfer and annual maintenance fees
  • Submit justification documentation

For RIPE recipients:

  • Submit 50% utilization plan for 5 years
  • Provide company registration documents
  • Supply confirmation letter from authorized director
  • Demonstrate active network presence in RIPE region

For APNIC recipients:

  • Submit 24-month utilization plan
  • Provide evidence of past delegation compliance
  • Supply organization documentation
  • Confirm active presence in APNIC region

For LACNIC recipients:

  • Submit needs justification
  • Provide required documentation
  • Confirm compliance with LACNIC policies

Step 9: Destination RIR needs assessment

The destination RIR evaluates whether the recipient qualifies for the resources:

Assessment criteria:

  • Legitimate presence in the destination region
  • Demonstrated need for the specific amount of resources
  • Technical capability to utilize the resources
  • Compliance with destination RIR policies
  • Current standing with the RIR

Processing time: 1-3 weeks depending on RIR and completeness of documentation

Phase 4: Final Approval and Transfer

Step 10: Bilateral RIR approval

Both RIRs must approve the transfer before it can proceed:

Source RIR confirms:

  • Willingness to de-register resources
  • No outstanding issues with source organization
  • Resources are clear for transfer

Destination RIR confirms:

  • Recipient meets all eligibility requirements
  • Needs assessment is approved
  • All fees are paid
  • Documentation is complete

Step 11: RIRs coordinate the transfer

The two RIRs work together to execute the transfer:

  • Source RIR prepares to de-register resources
  • Destination RIR prepares to register resources
  • Both RIRs coordinate timing to minimize routing disruption
  • Transfer is executed simultaneously in both systems

Step 12: Resources are transferred

Source RIR actions:

  • De-registers resources from source organization
  • Updates WHOIS database
  • Marks resources as transferred out
  • Issues transfer confirmation

Destination RIR actions:

  • Registers resources to recipient organization
  • Updates WHOIS and routing databases
  • Issues new registration certificates
  • Confirms transfer completion

Phase 5: Post-Transfer Actions

Step 13: Update routing information

The recipient must update routing announcements:

  • Update BGP announcements with new RIR information
  • Coordinate with upstream providers
  • Update Route Origin Authorization (ROA) records
  • Monitor routing propagation

Step 14: Verify transfer completion

Confirm the following:

  • Resources appear in destination RIR's WHOIS database
  • WHOIS records show correct organization details
  • Resources are de-registered from source RIR
  • All routing information is updated
  • Registration certificates are received

Step 15: Maintain compliance

Ongoing obligations:

  • Pay annual fees to destination RIR
  • Keep registration information current
  • Comply with resource utilization commitments
  • Maintain active presence in destination region
  • Respond to RIR communications promptly

Transfer Timelines by RIR Combination

Inter-RIR transfer timelines vary significantly based on which RIRs are involved:

Fast Processing Combinations (4-6 weeks)

RIPE ↔ ARIN:

  • Typical completion: 4-6 weeks
  • Well-established procedures
  • Efficient coordination between RIRs
  • Pre-approval available at ARIN

RIPE ↔ APNIC:

  • Typical completion: 4-6 weeks
  • Streamlined documentation requirements
  • Regular inter-RIR coordination
  • Efficient processing on both sides

ARIN ↔ APNIC:

  • Typical completion: 4-6 weeks
  • Compatible needs-based assessments
  • Established transfer procedures
  • Regular communication channels

Moderate Processing (6-10 weeks)

Involving LACNIC (sender or recipient):

  • Typical completion: 8-10 weeks
  • More detailed justification requirements
  • Additional documentation review
  • Time zone coordination challenges

Factors Affecting Timeline

Faster transfers:

  • Complete documentation submitted upfront
  • Pre-approval obtained (where available)
  • Simple organizational structures
  • Prompt response to RIR questions
  • Experienced transfer brokers or consultants involved

Slower transfers:

  • Incomplete or incorrect documentation
  • Complex organizational structures
  • First-time transfers for the organizations
  • Need for additional justification
  • Language or translation requirements
  • Holiday periods in either region

Costs and Fees

Inter-RIR transfer costs include fees from both RIRs plus any broker or consultant fees:

ARIN Fees

Transfer processing:

  • IPv4 transfer processing fee: $500 (non-refundable)
  • ASN transfer processing fee: $500 (non-refundable)

Ongoing fees:

  • Annual maintenance fee: $150-$500 (based on resource size)
  • Registration Services Agreement (RSA) required

Post-transfer restrictions:

  • 36-month waitlist restriction if transferring out resources

RIPE NCC Fees

Membership requirements:

  • LIR membership: €1,400 per year (standard)
  • One-time setup fee: €2,000 (new members)
  • Or use sponsoring LIR services

Transfer fees:

  • No separate transfer processing fee
  • Included in membership benefits

APNIC Fees

Membership or account:

  • Associate membership or account required
  • Fees vary by membership type and country
  • Transfer processing included in membership

LACNIC Fees

Membership requirements:

  • Active LACNIC membership required
  • Annual fees vary by resource holdings
  • Additional documentation may require certified translations

Additional Costs

Optional but common:

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

Special Considerations

Legacy Resources

IPv4 legacy space (allocated before RIR system):

  • May have different transfer requirements
  • Some RIRs require registration or service agreements first
  • Legacy status may be lost upon transfer to certain RIRs (e.g., LACNIC)
  • Additional documentation often required

ASN Transfers

Inter-RIR ASN transfers:

  • Only allowed between RIRs with ASN transfer policies
  • Must demonstrate continued need for the ASN
  • Routing policies must be maintained
  • 16-bit ASNs may have special restrictions (RIPE requires 2-year hold period)

IPv6 Transfers

Current status:

  • ARIN does not permit inter-RIR transfers of IPv6 addresses
  • Most RIRs focus inter-RIR transfers on IPv4 only
  • IPv6 is still readily available through direct allocations
  • Policies may evolve as IPv6 adoption increases

Partial Transfers

Splitting address blocks:

  • Minimum size /24 must be maintained
  • Source RIR must approve the split
  • CIDR boundary alignment required
  • May require additional technical justification

Best Practices for Successful Inter-RIR Transfers

1. Plan Early and Allow Sufficient Time

Start the process 3-6 months before you need the resources:

  • Account for potential documentation issues
  • Allow time for needs assessment preparation
  • Consider RIR processing backlogs
  • Plan for unexpected delays

2. Understand Both RIRs' Policies Thoroughly

Research requirements:

  • Read official policy documentation from both RIRs
  • Understand needs assessment criteria
  • Know hold period and restriction requirements
  • Familiarize yourself with fee structures

Official policy sources:

  • RIPE: www.ripe.net/publications/docs/ripe-769
  • ARIN: www.arin.net/resources/registry/transfers
  • APNIC: www.apnic.net/manage-ip/manage-resources/transfer-resources
  • LACNIC: www.lacnic.net/en/web/lacnic/inter-regional-transfers

3. Prepare Complete Documentation Upfront

Checklist:

  • Company registration papers (recent, official)
  • Letters of authorization (properly signed and notarized if required)
  • Network diagrams and infrastructure documentation
  • Utilization plans with detailed justification
  • Contact information for all authorized representatives
  • Any additional RIR-specific requirements

4. Consider Pre-Approval

ARIN recipients:

  • Submit pre-approval request before initiating transfer
  • Valid for 24 months
  • Reduces transfer processing time
  • Provides certainty before committing to purchase

5. Use Experienced Professionals When Needed

Consider using:

  • Transfer brokers: Navigate the process, coordinate with RIRs
  • LIR consultants: Provide sponsorship and expertise
  • Legal advisors: Review agreements and ensure compliance
  • Technical consultants: Assist with routing updates

6. Maintain Clear Communication

Communication tips:

  • Respond promptly to RIR requests
  • Keep all stakeholders informed
  • Use official RIR contact channels
  • Document all communications
  • Clarify requirements if uncertain

7. Verify Post-Transfer Compliance

After transfer completion:

  • Confirm WHOIS accuracy
  • Update all routing information
  • Verify registration certificates
  • Set up annual fee payments
  • Maintain utilization commitments

Common Challenges and Solutions

Challenge 1: Incomplete or Incorrect Documentation

Problem: Transfer delayed due to missing or improperly formatted documents

Solution:

  • Use RIR-provided checklists and templates
  • Have documents reviewed by professionals
  • Ensure company names match exactly across all documents
  • Get proper authorization levels for signatures
  • Allow extra time for notarization if required

Challenge 2: Needs Justification Rejection

Problem: Destination RIR rejects needs assessment

Solution:

  • Provide detailed, realistic utilization plans
  • Include network diagrams and infrastructure details
  • Reference specific use cases and customer requirements
  • Consider requesting smaller resource amounts
  • Seek guidance from the RIR before resubmitting

Challenge 3: Hold Period Not Met

Problem: Resources don't meet minimum hold period at source RIR

Solution:

  • Verify hold periods before initiating transfer
  • Wait until hold period requirements are satisfied
  • Check for exceptions to hold period rules
  • Consider alternative resource sources

Challenge 4: Policy Incompatibility

Problem: Source and destination RIRs have incompatible requirements

Solution:

  • Verify policy compatibility before starting
  • Understand both RIRs' specific requirements
  • Work with transfer brokers familiar with both regions
  • Ensure needs assessment meets both RIRs' standards

Challenge 5: Routing Coordination

Problem: Routing disruption during or after transfer

Solution:

  • Plan routing updates in advance
  • Coordinate with upstream providers
  • Update ROA records before de-registration
  • Monitor BGP propagation during transfer
  • Have rollback plan ready if issues occur

Using Via-Registry for Inter-RIR Transfers

Inter-RIR transfers involve complex coordination between multiple registries, each with distinct policies and requirements. Via-Registry simplifies this process by providing:

Complete transfer management:

  • Coordination with both source and destination RIRs
  • Documentation preparation and submission
  • Needs assessment support and justification development
  • Timeline management and status tracking

Expert guidance:

  • Policy interpretation for all RIR combinations
  • Compliance verification for both regions
  • Technical support for routing transitions
  • Post-transfer maintenance assistance

Sponsoring LIR services:

  • RIPE NCC sponsorship for organizations without LIR membership
  • Reduced costs compared to direct membership
  • Ongoing account management and support

Get started with our Inter-RIR Transfer Service to streamline your transfer and ensure compliance with all RIR requirements.

Frequently Asked Questions

Can any IPv4 addresses be transferred between RIRs?

Not all IPv4 addresses are eligible for inter-RIR transfer. Resources must meet hold period requirements, must not be special-use addresses, and must be properly registered in the source RIR. Legacy resources may have additional restrictions. Additionally, AFRINIC does not participate in inter-RIR transfers, so no resources can be transferred to or from the African region.

How long does an inter-RIR transfer typically take?

Transfer timelines vary by RIR combination. RIPE-ARIN, RIPE-APNIC, and ARIN-APNIC transfers typically complete in 4-6 weeks with complete documentation. Transfers involving LACNIC generally take 8-10 weeks or longer due to additional requirements and processing procedures. Incomplete documentation or needs assessment issues can extend timelines significantly.

Do I need to be an LIR member to receive transferred resources?

Requirements vary by RIR. For RIPE transfers, you need either direct LIR membership or a sponsoring LIR. ARIN allows resource holders without full membership through Registration Services Agreements (RSA). APNIC requires membership or associate membership. LACNIC requires active membership. Using a sponsoring LIR like Via-Registry can eliminate the need for direct membership.

Can I transfer IPv6 addresses between RIRs?

Currently, inter-RIR IPv6 transfers are limited. ARIN explicitly does not permit inter-RIR transfers of IPv6 addresses. Most inter-RIR transfer activity focuses on IPv4 resources due to exhaustion and market demand. IPv6 is still readily available through direct allocations from all RIRs at minimal cost.

What happens if my transfer request is rejected?

If either RIR rejects the transfer, you'll receive an explanation of the rejection reasons. Common issues include insufficient needs justification, incomplete documentation, or policy non-compliance. Most rejections can be resolved by addressing the specific concerns and resubmitting. Via-Registry can help prepare stronger applications and navigate the resubmission process.

Are there restrictions on re-transferring resources?

Yes, all participating RIRs impose hold periods and transfer restrictions. ARIN requires 12 months after receiving a transfer before you can transfer resources out. RIPE requires 24 months. LACNIC imposes 1-year re-transfer restrictions. These policies prevent resource stockpiling and speculative transfers.

How much does an inter-RIR transfer cost?

Costs include RIR fees, possible membership fees, and optional broker/consultant fees. ARIN charges $500 processing fee plus annual maintenance. RIPE requires LIR membership (€1,400/year) or sponsoring LIR. APNIC and LACNIC have membership-based fee structures. Transfer brokers typically charge 3-10% of transaction value. Total costs can range from $2,000 to $20,000+ depending on resource size and services needed.

Summary

Inter-RIR transfers enable the movement of IPv4 addresses and ASNs across regional boundaries, supporting the global Internet resource market. Key points to remember:

Policy framework:

  • Only RIPE, ARIN, APNIC, and LACNIC support inter-RIR transfers
  • Transfers require reciprocal, compatible policies between RIRs
  • AFRINIC does not participate in inter-RIR transfers

Requirements:

  • Source organizations must meet hold period requirements (12-36 months)
  • Recipients must demonstrate legitimate need and regional presence
  • Minimum transfer size is /24 for IPv4 addresses
  • Both RIRs must approve the transfer

Process:

  • Initiated by source organization at source RIR
  • Requires coordination between both RIRs
  • Involves needs assessment at destination RIR
  • Typical timeline: 4-10 weeks depending on RIRs involved

Success factors:

  • Complete, accurate documentation
  • Thorough understanding of both RIRs' policies
  • Adequate needs justification
  • Professional guidance for complex transfers
  • Sufficient time allowance for processing

Next Steps

Ready to initiate an inter-RIR transfer? Via-Registry provides comprehensive support throughout the entire process:

Learn more about specific transfers:

Get expert assistance:

This guide is based on current RIR policies as of 2025. Policies may be updated periodically. For the most current information, consult official RIR documentation. For assistance with your inter-RIR transfer, contact our team or explore our Inter-RIR Transfer Service.

Back to Resources