Inter-RIR Transfer Eligibility by Region

Understanding the specific eligibility requirements for each Regional Internet Registry (RIR) is critical for successful inter-RIR transfers. Each RIR has distinct policies governing who can transfer resources, when they can transfer them, and under what conditions. This guide provides a comprehensive breakdown of eligibility requirements for all four RIRs that participate in inter-RIR transfers.

Overview of Regional Differences

While all participating RIRs share the fundamental principle of needs-based resource distribution, their specific eligibility criteria vary significantly:

Key differences include:

• Hold period requirements before resources can be transferred
• Needs assessment methodology and timeframes
• Documentation and proof requirements
• Regional presence verification methods
• Post-transfer restrictions and limitations

Understanding these differences is essential for planning your transfer strategy and ensuring compliance with both source and destination RIR policies. For a complete overview of the inter-RIR transfer process, see our Inter-RIR Transfer Process Explained guide.

RIPE NCC Eligibility Requirements

The RIPE Network Coordination Centre serves Europe, the Middle East, and parts of Central Asia. RIPE's inter-RIR transfer policy (RIPE-769) is generally considered one of the most straightforward.

Eligibility as Source (Transferring Out)

Basic requirements:

• Must be a current RIPE NCC member (LIR) or have resources registered through a sponsoring LIR
• Must be the registered holder of the resources
• Resources must not be subject to any disputes or liens
• Must be current with all RIPE NCC obligations (membership fees, contact updates)

Hold period requirements:

• IPv4 allocations: 24 months after the allocation date
• IPv4 transfers: 24 months after the last transfer date
• ASN transfers: 24 months for scarce resources (16-bit ASNs); otherwise per standard policy

Resource eligibility:

• Minimum transfer size: /24 (256 IPv4 addresses)
• Must be publicly routable address space
• Special-use or reserved space cannot be transferred
• Legacy resources may require additional registration steps

Restrictions:

• Cannot transfer the same resources more frequently than every 24 months
• Must notify RIPE NCC of the transfer intent
• Source organization remains responsible until transfer is complete

Eligibility as Recipient (Receiving Resources)

Organizational requirements:

• Must have at least one active network element in the RIPE NCC service region
• Legal entity must be established within the RIPE region
• Must be a RIPE NCC member or use a sponsoring LIR
• Company registration must be current and verifiable

Needs assessment (from needs-based RIRs):

• Must demonstrate plan to use at least 50% of transferred resources within 5 years
• Provide supporting business case and network plans
• Document current infrastructure and growth projections
• Show legitimate operational need for the resources

Documentation required:

• Recent company registration papers from national authorities
• Confirmation letter signed by authorized company director
• Network infrastructure documentation
• 5-year utilization plan (for transfers from ARIN, APNIC)
• Proof of active operations in RIPE region

Regional presence verification:

• Physical office or operational facility in RIPE region
• Active network infrastructure (servers, routers, etc.)
• Local business registration
• European-based operations or customers

RIPE-Specific Policies

No needs assessment for some transfers: When receiving from RIRs without needs-based outbound requirements, RIPE may not require the 50% utilization plan. However, the basic requirement to have an active presence in the region still applies.

Legacy resources: Legacy IPv4 resources can be transferred, but must first be brought under contract with RIPE NCC. Legacy status is maintained within the RIPE region.

Post-transfer obligations:

• Maintain LIR membership or sponsoring relationship
• Keep WHOIS data current
• Comply with ongoing utilization requirements
• Respond to RIPE NCC communications

ARIN Eligibility Requirements

The American Registry for Internet Numbers serves North America (United States, Canada, and parts of the Caribbean). ARIN's inter-RIR policy (NRPM 8.4) includes some of the most stringent requirements.

Eligibility as Source (Transferring Out)

Basic requirements:

• Must be the registered holder in ARIN's database
• Must have signed a Registration Services Agreement (RSA) with ARIN
• Must be current with all ARIN fees and obligations
• Resources must be accurately registered and maintained

Hold period requirements:

• 12 months after receiving any allocation, transfer, or assignment from ARIN
• This applies to all IPv4 resources received from ARIN
• Clock starts from the date of the most recent ARIN transaction

Pre-transfer restrictions:

• Must not have received a transfer, allocation, or assignment from ARIN in the previous 12 months
• If resources were obtained through multiple transactions, the most recent date applies

Post-transfer restrictions:

• 36-month waitlist restriction: After transferring resources out, the source entity cannot apply for IPv4 address space under ARIN's waitlist (Section 4.1.8) for 36 months
• This restriction is designed to prevent resource recycling through the free pool

Officer attestation:

• Must provide signed and notarized Officer Acknowledgement Letter
• Officer must have legal authority to bind the organization
• Attestation confirms understanding of transfer terms and restrictions

Resource eligibility:

• Minimum transfer size: /24 (256 IPv4 addresses)
• Resources must be specified recipients transfers (not general waiting list)
• Must verify no outstanding disputes or claims

Eligibility as Recipient (Receiving Resources)

Organizational requirements:

• Must have operational presence in ARIN service region (US, Canada, Caribbean)
• Legal entity must be registered in the ARIN region
• Must sign ARIN Registration Services Agreement (RSA)
• Must establish ARIN Online account

Needs assessment:

• Must demonstrate need for up to a 24-month supply of IPv4 addresses
• Provide detailed utilization plans showing how addresses will be used
• Document current infrastructure and immediate needs
• Show realistic deployment timeline

Pre-approval option:

• ARIN offers pre-approval for transfer recipients
• Valid for 24 months from approval date
• Significantly speeds up transfer process
• Recommended for first-time recipients

Documentation required:

• Organizational documentation (articles of incorporation, etc.)
• Detailed network plan showing infrastructure
• Utilization justification with timeline
• Current IP address usage (if applicable)
• Signed RSA and officer attestation

Regional presence verification:

• Physical business location in ARIN region
• Operational infrastructure deployed or planned in region
• Customer base or service area within ARIN territory
• Business registration in US, Canada, or Caribbean nation

ARIN-Specific Policies

Compatibility requirement: ARIN will request certification from the source RIR confirming that the transfer request is compatible with ARIN's needs-based policies. This ensures reciprocity.

Fee structure:

• Transfer processing fee: $500 (non-refundable)
• Annual maintenance fees based on resource size
• Fee-for-service model applies

Legacy resources: Legacy resources can be transferred but must first be brought under an ARIN RSA. Legacy holders must comply with current ARIN policies for inter-RIR transfers.

APNIC Eligibility Requirements

The Asia Pacific Network Information Centre serves the Asia-Pacific region. APNIC's inter-RIR transfer policy balances accessibility with needs-based allocation principles.

Eligibility as Source (Transferring Out)

Basic requirements:

• Must be current APNIC account holder (except for certain historical resources)
• Resources must be under APNIC's management
• Authentic holder must match source organization without disputes
• Must be current with APNIC obligations

Hold period requirements:

• Standard resources: No specific hold period for most resources
• 103/8 pool resources: 5-year minimum hold period from original delegation date
• Resources from 103/8 cannot be transferred for 5 years after allocation

Account requirements:

• Active APNIC account or membership
• Current contact information
• No outstanding fees or obligations
• Proper authorization for transfer

Historical resources: In some cases, historical resource holders not currently in APNIC's database may transfer, but additional verification is required.

Eligibility as Recipient (Receiving Resources)

Organizational requirements:

• Must have operational presence in APNIC service region
• Legal entity registered within the Asia-Pacific region
• Active APNIC account or membership required
• Demonstrated business operations in region

Needs assessment:

• Must demonstrate detailed plan for use of transferred resources within 24 months
• Provide evidence of current infrastructure and needs
• Show realistic deployment schedule
• Document growth projections and customer base

Compliance verification:

• Must provide evidence of compliance with APNIC policies regarding past delegations
• If recipient has previous APNIC resources, must show proper utilization
• No history of policy violations or non-compliance

Documentation required:

• Organization registration documents
• Network infrastructure details
• 24-month utilization plan
• Evidence of regional presence
• Authorization from legal representatives

Regional presence verification:

• Physical operations in APNIC region (Asia-Pacific)
• Active network infrastructure deployment
• Business registration in APNIC member economy
• Service delivery to Asia-Pacific markets

APNIC-Specific Policies

NIR involvement: In economies with National Internet Registries (NIRs) like Japan (JPNIC), China (CNNIC), Korea (KRNIC), etc., transfers may need to go through the NIR.

Minimum size:

• /24 for IPv4 transfers (consistent with other RIRs)
• Must maintain CIDR boundary alignment

ASN transfers: APNIC will recognize inter-RIR ASN transfers only when the counterpart RIR has an inter-RIR ASN transfer policy. Currently compatible with RIPE and ARIN for ASN transfers.

LACNIC Eligibility Requirements

The Latin American and Caribbean Internet Addresses Registry serves Latin America and the Caribbean. LACNIC's inter-RIR transfer policy (LAC-2019-1) became operational in 2020 and includes some unique requirements.

Eligibility as Source (Transferring Out)

Basic requirements:

• Must be current LACNIC member in good standing
• Resources must be registered under the source organization
• Must be current with all contractual obligations to LACNIC
• No outstanding disputes regarding the resources

Hold period requirements:

• 3-year hold period for LACNIC-allocated resources before they can be transferred
• This is one of the longest hold periods among participating RIRs
• Clock starts from original allocation date

Re-transfer restrictions:

• 1-year re-transfer bar: After receiving resources via transfer, cannot transfer them out for 1 year
• Applies to both intra-RIR and inter-RIR transfers
• Designed to prevent rapid speculation

Member obligations:

• Must maintain active LACNIC membership
• Current with all membership fees
• Proper resource registration and maintenance
• Updated contact information

Eligibility as Recipient (Receiving Resources)

Organizational requirements:

• Must have operational presence in LACNIC service region
• Legal entity registered in Latin America or Caribbean
• Active LACNIC membership required
• Demonstrated business operations in region

Needs assessment:

• Must demonstrate legitimate need for the resources
• Provide detailed justification per LACNIC policies
• Historically required strict justification including NAT deployment evidence
• Utilization plans and network documentation

Documentation required:

• Company registration from Latin American or Caribbean nation
• Network infrastructure documentation
• Needs justification with detailed technical plans
• Proof of LACNIC membership
• Authorization from legal representatives
• Documents may require certified translation to Spanish or Portuguese

Regional presence verification:

• Physical business presence in LACNIC region
• Active network operations in Latin America or Caribbean
• Business registration in LACNIC member country
• Service delivery or infrastructure deployment in region

LACNIC-Specific Policies

Legacy resources: When legacy IPv4 prefixes are transferred into the LACNIC region, they lose their legacy status and become subject to standard LACNIC policies and fees.

Minimum transfer size:

• /24 for IPv4 addresses (consistent with other RIRs)

Policy compatibility: LACNIC can transfer with RIPE, ARIN, and APNIC. No transfers with AFRINIC due to lack of reciprocal policy.

Language requirements:

• Official languages are Spanish and Portuguese
• English documents may require certified translation
• Communication with LACNIC may be in Spanish/Portuguese

AFRINIC Status

The African Network Information Centre serves the African continent but does NOT currently participate in inter-RIR transfers.

Current Situation

No inter-RIR policy:

• AFRINIC does not have an inter-RIR transfer policy in effect
• No resources can be transferred to or from the AFRINIC region
• Only intra-RIR transfers within Africa are permitted

Policy proposals under consideration:

• 2019-IPv4-002: IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)
• 2020-GEN-006: AFRINIC Number Resources Transfer Policy
• 2019-V4-001: IPv4 Inter-RIR Legacy Resource Transfers

Impact on global transfers: All four participating RIRs (RIPE, ARIN, APNIC, LACNIC) prohibit transfers to/from AFRINIC due to the lack of reciprocal policy.

Intra-RIR only: Organizations in Africa can transfer resources within the AFRINIC region per Section 5.7 of the Consolidated Policy Manual, but cannot participate in the global inter-RIR transfer market.

Comparative Eligibility Matrix

Hold Periods

RIR	Standard Hold Period	Special Cases
RIPE	24 months	After allocation or last transfer
ARIN	12 months	After any ARIN transaction
APNIC	Variable	5 years for 103/8 pool
LACNIC	36 months	After LACNIC allocation

Needs Assessment Timeframes

RIR	Justification Period	Notes
RIPE	5 years (50% usage)	Only for transfers from needs-based RIRs
ARIN	24 months	Full needs demonstration
APNIC	24 months	Detailed utilization plan
LACNIC	Variable	Per LACNIC needs policy

Minimum Transfer Sizes

All participating RIRs use the same minimum:

• IPv4: /24 (256 addresses)
• ASN: Individual ASNs (where permitted)

Post-Transfer Restrictions

RIR	Re-transfer Restriction	Additional Restrictions
RIPE	24 months	Cannot transfer same resources
ARIN	12 months to transfer out	36-month waitlist ban
APNIC	Variable	Depends on resource type
LACNIC	12 months	1-year re-transfer bar

Common Eligibility Issues and Solutions

Issue 1: Insufficient Hold Period

Problem: Attempting to transfer resources before the required hold period has elapsed.

Solution:

• Verify exact allocation/transfer date from RIR records
• Calculate hold period from the correct starting date
• Wait until hold period requirement is met
• Check for any hold period exceptions in RIR policies

Issue 2: Inadequate Regional Presence

Problem: Cannot demonstrate sufficient operational presence in destination RIR region.

Solution:

• Establish physical office or operational facility in region
• Deploy actual network infrastructure (not just plans)
• Obtain local business registration
• Develop customer base or service area in region
• Document all regional presence elements clearly

Issue 3: Weak Needs Justification

Problem: Destination RIR rejects needs assessment as insufficient.

Solution:

• Provide detailed, realistic utilization plans
• Include network diagrams and infrastructure documentation
• Reference specific use cases and customer requirements
• Show current utilization of existing resources if applicable
• Consider requesting smaller resource amounts
• Work with consultants experienced in needs assessments

Issue 4: Documentation Problems

Problem: Required documents are missing, incomplete, or improperly formatted.

Solution:

• Use official RIR templates and checklists
• Ensure company names match exactly across all documents
• Obtain proper authorization levels for signatures
• Get notarization where required (ARIN transfers)
• Translate documents if needed (LACNIC)
• Have documents professionally reviewed before submission

Issue 5: Legacy Resource Complications

Problem: Legacy resources have different or additional requirements.

Solution:

• Bring legacy resources under contract with current RIR first
• Understand that legacy status may be lost in some regions
• Complete additional verification steps required for legacy space
• Budget extra time for legacy resource processing

Best Practices for Ensuring Eligibility

1. Verify Eligibility Before Committing

Pre-transfer checklist:

• Confirm resources meet hold period requirements
• Verify you can demonstrate adequate regional presence
• Assess your ability to provide needs justification
• Check that both RIRs have compatible policies
• Ensure all organizational documentation is current

2. Maintain Current RIR Relationships

Ongoing compliance:

• Keep all RIR memberships active and current
• Pay fees on time
• Maintain accurate WHOIS records
• Update contact information promptly
• Respond to RIR communications

3. Document Regional Presence Thoroughly

Proof of presence:

• Physical office lease or ownership documents
• Utility bills showing operational facility
• Business registration certificates
• Network infrastructure deployment evidence
• Customer contracts or service agreements
• Local banking and financial records

4. Prepare Strong Needs Justification

Effective justification includes:

• Detailed network diagrams
• Infrastructure deployment timeline
• Specific use cases and customer requirements
• Realistic growth projections
• Current resource utilization data
• Technical rationale for requested amount

5. Work with Experienced Professionals

When to seek help:

• First-time inter-RIR transfers
• Complex organizational structures
• Challenging needs assessment
• Legacy resource transfers
• Tight timelines
• Multi-party transactions

Via-Registry Eligibility Support

Navigating the different eligibility requirements across RIRs can be complex. Via-Registry provides comprehensive support to ensure your organization meets all requirements:

Eligibility assessment:

• Pre-transfer eligibility verification
• Hold period calculation and confirmation
• Regional presence evaluation
• Needs assessment preparation

Documentation assistance:

• Complete documentation checklist development
• Template provision and formatting guidance
• Document review and verification
• Translation coordination (LACNIC transfers)

Sponsoring LIR services:

• RIPE NCC membership alternative
• Reduced cost compared to direct membership
• Ongoing compliance support
• Transfer coordination and management

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

Summary

Inter-RIR transfer eligibility varies significantly across regions:

Key requirements:

• Hold periods: 12-36 months depending on RIR
• Needs assessment: 24 months (ARIN, APNIC) or 5-year 50% plan (RIPE)
• Regional presence: Physical operations in destination region required
• Minimum size: /24 for all IPv4 transfers
• Documentation: Company registration, authorization, utilization plans

Critical differences:

• ARIN has strictest post-transfer restrictions (36-month waitlist ban)
• LACNIC has longest hold period (36 months)
• RIPE has most flexible needs assessment (50% over 5 years)
• APNIC has special restrictions on 103/8 pool resources
• AFRINIC does not participate in inter-RIR transfers

Success factors:

• Verify eligibility before committing to transfer
• Maintain current RIR relationships
• Document regional presence thoroughly
• Prepare comprehensive needs justification
• Seek professional assistance when needed