ASN Registration Requirements by RIR: Complete Comparison Guide

Autonomous System Number (ASN) registration requirements vary significantly across the five Regional Internet Registries (RIRs). Understanding these differences is crucial for organizations planning to obtain an ASN, as requirements affect eligibility, documentation needs, processing time, and costs.

This comprehensive guide compares ASN registration requirements across RIPE NCC, ARIN, APNIC, LACNIC, and AFRINIC, helping you navigate the specific requirements for your region and prepare a successful application.

Overview of Regional Internet Registries

The five RIRs manage IP address space and ASN allocation for different geographic regions:

Your RIR is determined by your organization's geographic location and operational headquarters, not by where your network infrastructure is deployed.

RIPE NCC ASN Requirements

RIPE NCC serves Europe, the Middle East, and parts of Central Asia with a community-driven policy development process.

Eligibility Criteria

To obtain an ASN from RIPE NCC, organizations must:

Organizational Requirements:

• Be a RIPE NCC member (LIR) OR work through a sponsoring LIR
• Have a valid legal entity registration in the RIPE service region
• Maintain up-to-date contact information in the RIPE Database
• Sign the RIPE NCC Standard Service Agreement (for direct members)

Technical Requirements:

• Demonstrate multi-homing with at least two different upstream providers
• Hold a minimum IP address allocation (/24 IPv4 or /48 IPv6)
• Have a documented routing policy
• Provide upstream provider ASNs and contact information

Current Policy Status (2025)

RIPE NCC is currently reviewing policy proposal 2025-01 "ASN assignment criteria revisited", which proposes significant changes:

Proposed changes:

• LIRs and End Users may request a single ASN without justification
• Additional ASNs require demonstration of unique routing policy
• Acknowledges that ASNs are no longer scarce resources with 32-bit ASN adoption
• Aims to simplify requirements while preventing exponential ASN exhaustion

Current practice: While the proposal is under review, RIPE continues to require multi-homing justification, though enforcement has become more flexible.

Documentation Requirements

Required documentation for RIPE ASN requests:

1. Upstream Provider Information

   • Full legal names of both upstream providers
   • ASNs of upstream providers
   • Technical contact email addresses (NOC) for each provider
   • Expected BGP session establishment dates

2. IP Address Resources

   • Documentation of IPv4 /24 or IPv6 /48 allocation
   • Assignment documentation from RIPE or sponsoring LIR
   • Plans for prefix announcements

3. Routing Policy Documentation

   • Description of routing strategy
   • Multi-homing configuration details
   • Traffic engineering plans (if applicable)

4. Organizational Information

   • Legal entity documentation
   • Organization contact details
   • Technical and administrative contacts
   • Abuse contact (mandatory)

Processing Time and Fees

Processing time: 1-3 business days for straightforward applications

Fees:

• LIR membership: €1,400 per year (includes ASN)
• Through sponsoring LIR: €50-€200 annually (varies by provider)
• Note: Proposed 2025 policy may introduce €50 annual fee per ASN

Special Considerations

Sponsoring LIR option: Organizations that don't want to become direct RIPE members can work through sponsoring LIRs, significantly reducing costs and administrative burden.

Multi-homing verification: RIPE may contact your upstream providers to verify your multi-homing setup. Ensure providers are aware of your application.

IPv6-only ASN requests: RIPE accepts ASN requests based solely on IPv6 allocations (/48 minimum), supporting IPv6 deployment.

ARIN ASN Requirements

ARIN (American Registry for Internet Numbers) serves the United States, Canada, and portions of the Caribbean with streamlined modern policies.

Eligibility Criteria

ARIN has simplified ASN requirements significantly in recent years:

Organizational Requirements:

• Be a legally formed business entity, nonprofit corporation, or government entity
• Operate within the ARIN service region
• Have an ARIN Online account
• Have valid Point of Contact (POC) records
• Have a valid Organization Identifier (Org ID)

Technical Requirements (either/or):

• Option 1: Provide names and ASNs of two upstream ISPs for multi-homing
• Option 2: Describe a unique routing policy that requires an ASN

Key advantage: ARIN's flexible approach accepts either multi-homing OR unique routing policy, providing more options than some other RIRs.

Documentation Requirements

ARIN has significantly reduced documentation requirements compared to historical policies:

Required information:

1. For Multi-homing Justification

   • Names of two upstream ISPs
   • ASNs of upstream providers
   • Brief description of multi-homing configuration

2. For Unique Routing Policy

   • Detailed description of unique routing requirements
   • Explanation of why existing routing methods are insufficient
   • Technical justification for ASN need

3. Network Information

   • Projected date of ASN usage (no longer requires 30-day immediate use)
   • General description of network services
   • Geographic scope of operations

Documentation NOT required:

• Copies of transit contracts or invoices
• Letters from upstream providers
• Detailed network diagrams
• Proof of IP address holdings (though you need addresses to announce)

As stated in ARIN's ASN request guide, the streamlined process eliminates bureaucratic hurdles while maintaining appropriate oversight.

Processing Time and Fees

Processing time: 3-7 business days

Fees:

• Annual ASN fee: $250 per year
• Registration Services Plan: Included with ASN fee
• No separate sign-up fee
• No membership requirement

Special Considerations

No sponsoring LIR system: Unlike RIPE, ARIN doesn't have a formal sponsoring LIR program. Organizations must interact directly with ARIN.

Registration Services Agreement (RSA): New organizations may need to sign an RSA, which is a straightforward online process.

Flexibility for unique policies: ARIN's acceptance of unique routing policies as justification (without multi-homing) makes ASN acquisition more accessible for specialized use cases like anycast CDNs.

APNIC ASN Requirements

APNIC (Asia-Pacific Network Information Centre) serves the Asia-Pacific region with policies that balance accessibility and resource conservation.

Eligibility Criteria

APNIC follows RFC 1930 guidelines for ASN eligibility:

Organizational Requirements:

• Be an APNIC member, non-member, or NIR member
• Have a valid legal entity in the APNIC service region
• Maintain current contact information in APNIC databases

Technical Requirements:

• Network is currently multihomed, OR
• Need to interconnect with other autonomous systems, OR
• Can demonstrate meeting criteria within a reasonably short time after receiving ASN

Application channels:

• Direct application to APNIC (members and non-members)
• Through National Internet Registry (NIR) in countries like Japan, China, South Korea
• Via sponsoring LIR (in some cases)

Documentation Requirements

APNIC requires comprehensive technical documentation:

Required documentation:

1. Routing Policy Specification

   • Detailed description of routing strategy
   • Traffic engineering approach
   • Peering policy overview

2. Interconnection Information

   • ASNs with which you will interconnect
   • Nature of interconnection relationships (transit, peering, etc.)
   • Expected timeline for establishing connections

3. IP Address Documentation

   • IP addresses that will be announced through the requested ASN
   • Prefix assignment documentation
   • Route announcement plans

4. Technical Justification

   • Explanation following RFC 1930 guidelines
   • Demonstration of multi-homing or interconnection need
   • Technical capability assessment

5. Organizational Documentation

   • Business registration documents
   • Contact information for administrative and technical staff
   • Organization address and legal details

Processing Time and Fees

Processing time: 5-10 business days

Fees (as of January 2025):

• Sign-up fee: AUD 500 (one-time, for new members)
• Allocation fee: AUD 500 (for ASNs beyond free allocation)
• Annual fee: First 2 ASNs free; AUD 100 per year for additional ASNs
• Plus annual membership fees based on resource holdings

Fee structure advantage: The two free ASNs per member policy, introduced in 2025, significantly reduces costs for organizations with limited resource needs.

Special Considerations

National Internet Registries (NIRs): Several APNIC region countries have NIRs that handle local resource allocation:

• JPNIC (Japan)
• CNNIC (China)
• KISA (South Korea)
• TWNIC (Taiwan)
• VNNIC (Vietnam)

Organizations in NIR countries typically apply through their NIR rather than directly to APNIC.

Resource-based fee structure: APNIC's fees scale with the amount of resources held, which can become expensive for organizations with large resource holdings.

LACNIC ASN Requirements

LACNIC (Latin America and Caribbean Network Information Centre) serves Latin America and Caribbean regions with policies supporting regional Internet growth.

Eligibility Criteria

LACNIC's ASN requirements are defined in their Policy Manual:

Organizational Requirements:

• Be a LACNIC member
• Have legal entity registration in LACNIC service region
• Maintain current contact information

Technical Requirements:

• Require interconnection with other independent autonomous systems at time of application, OR
• Plan to establish such interconnection within six months

Key flexibility: LACNIC's six-month planning window allows organizations to apply before fully implementing their multi-homing setup.

Documentation Requirements

Required documentation:

1. Interconnection Details

   • ASNs with which the organization will interconnect
   • Nature of relationships (transit providers, peers, etc.)
   • Timeline for establishing connections (if not yet active)

2. Routing Policy

   • Detailed routing policy description
   • Traffic engineering requirements
   • Route filtering approach

3. IP Address Information

   • IP addresses to be announced through the requested ASN
   • Prefix assignment documentation
   • Route announcement strategy

4. Technical Justification

   • Demonstration of need for globally unique ASN
   • Explanation of routing requirements
   • Technical capability assessment

5. Organizational Documentation

   • Business registration certificate
   • Legal representative information
   • Administrative and technical contacts

Processing Time and Fees

Processing time: 5-15 business days

Fees:

• Included in LACNIC membership fees
• Membership categories vary by resource holdings and organization type
• No separate ASN registration fee
• Annual renewal required

Special Considerations

Six-month planning window: LACNIC's policy allowing ASN requests for planned interconnections within six months is more flexible than some RIRs that require immediate multi-homing.

No explicit multi-homing requirement: LACNIC policies don't specifically mandate multi-homing if unique routing policy justification is sufficient.

Transfer restrictions: LACNIC policies prohibit non-authorized sale or transfer of ASNs but allow transfers resulting from mergers, acquisitions, business reorganization, or relocation.

AFRINIC ASN Requirements

AFRINIC (African Network Information Centre) serves the African continent with policies designed to support Internet infrastructure development in Africa.

Eligibility Criteria

AFRINIC's requirements are detailed in their Consolidated Policy Manual:

Organizational Requirements:

• Be an AFRINIC resource member
• Have legal entity registration in African region
• Maintain current contact information in AFRINIC database

Technical Requirements (must meet one):

• Interconnect (including peering) with more than one AS, OR
• Show a unique routing policy, OR
• Demonstrate technical need for globally unique ASN

Future planning: Organizations may qualify if they demonstrate meeting criteria within six months of receiving the ASN.

Documentation Requirements

Required documentation:

1. Technical Justification

   • Description of interconnection needs
   • Unique routing policy explanation (if applicable)
   • Multi-homing configuration details

2. Network Infrastructure

   • Network topology overview
   • Geographic scope
   • Services provided

3. Routing Information

   • Peering relationships (existing or planned)
   • ASNs of interconnection partners
   • Routing policy documentation

4. IP Address Resources

   • Current IP address holdings
   • Plans for prefix announcements
   • Assignment documentation

5. Organizational Documentation

   • Business registration certificate
   • Contact information
   • Legal representative details

Processing Time and Fees

Processing time: 7-14 business days

Fees:

• Included in AFRINIC resource member fees
• No separate annual ASN maintenance fees
• Membership categories vary by organization type
• Annual membership renewal required

Fee advantage: AFRINIC's policy of not charging separate ASN maintenance fees makes ongoing costs lower than some other RIRs.

Special Considerations

Resource philosophy: AFRINIC emphasizes that ASNs are public resources distributed based on demonstrated need. Organizations are "custodians" rather than "owners" of ASNs.

Transfer restrictions: ASNs generally cannot be sold or transferred except in cases of legitimate business combinations, reorganizations, or mergers.

Development focus: AFRINIC policies support Internet infrastructure development in Africa, sometimes showing flexibility for organizations contributing to regional Internet growth.

Comparative Analysis of Requirements

Multi-homing Requirements

Winner for flexibility: ARIN and AFRINIC offer the most flexibility by accepting unique routing policies without mandatory multi-homing.

Documentation Burden

Most streamlined: ARIN requires the least documentation, with no contracts, invoices, or detailed network diagrams needed.

Most detailed: APNIC and LACNIC require comprehensive technical documentation including detailed routing policies and interconnection plans.

Middle ground: RIPE, while requiring multi-homing verification, has relatively straightforward documentation requirements.

Processing Time

Fastest: RIPE NCC (1-3 business days)

Moderate: ARIN (3-7 days), APNIC (5-10 days)

Slower: LACNIC (5-15 days), AFRINIC (7-14 days)

Processing times vary based on application completeness and whether the RIR requests additional information.

Cost Comparison

Most cost-effective: AFRINIC (no separate ASN fees) and ARIN (flat $250/year)

Most expensive: RIPE LIR membership (€1,400/year), though sponsoring LIR option significantly reduces costs

For detailed cost analysis, see our Cost Breakdown: ASN Registration Fees.

Common Requirements Across All RIRs

Despite differences, certain requirements are universal:

Universal Technical Requirements

1. Legitimate routing need: All RIRs require demonstration of genuine need for independent routing
2. IP address resources: You need IP addresses to announce (though specific minimums vary)
3. Technical capability: Organizations must show capacity to manage BGP routing
4. RFC 1930 compliance: All RIRs reference RFC 1930 guidelines for AS definition

Universal Organizational Requirements

1. Legal entity: Must be a registered business, organization, or government entity
2. Geographic eligibility: Organization must operate in the RIR's service region
3. Contact information: Current, accurate contact details required
4. Ongoing maintenance: Annual fees or membership renewals necessary

Universal Policy Principles

1. Public resource philosophy: ASNs are not owned but assigned based on need
2. Transfer restrictions: ASNs generally cannot be sold (except business combinations)
3. Revocation possibility: RIRs can revoke ASNs for policy violations or non-payment
4. Unique routing policy: All RIRs recognize need for unique routing as valid justification

Choosing the Right Approach

When to Apply Directly to Your RIR

Consider direct RIR membership if:

• You need multiple ASNs or large IP allocations
• You want full control over your resources
• You have administrative capacity to manage RIR relationships
• Your organization plans significant network growth
• You need to request resources frequently

When to Use a Sponsoring LIR

Consider sponsoring LIR if:

• You only need one ASN and small IP allocation
• You want to minimize administrative burden
• Cost reduction is important
• You don't have RIR expertise in-house
• You need faster, simpler process

Via-Registry.com offers sponsoring LIR services for RIPE region, handling all administrative tasks while you retain full usage rights to your ASN.

Preparing for Application Success

General Preparation Steps

Regardless of which RIR you're working with:

1. Verify geographic eligibility - Confirm your organization is in the correct RIR region
2. Assess technical readiness - Ensure you have necessary technical infrastructure
3. Secure upstream agreements - Establish relationships with ISPs before applying
4. Document your network - Prepare routing policy and technical documentation
5. Gather organizational documents - Compile business registration and contact information
6. Plan IP addressing - Obtain necessary IP allocations before or concurrent with ASN request
7. Budget appropriately - Account for both initial and ongoing costs

RIR-Specific Preparation

For RIPE:

• Decide between LIR membership and sponsoring LIR
• Coordinate with upstream providers for verification
• Prepare detailed multi-homing justification
• Ensure IP allocation meets /24 or /48 minimum

For ARIN:

• Create ARIN Online account
• Establish Org ID and POC records
• Prepare either multi-homing or unique routing policy justification
• Review simplified documentation requirements

For APNIC:

• Determine if you should apply through NIR (if applicable)
• Prepare comprehensive routing policy documentation
• Document interconnection plans thoroughly
• Budget for initial setup fees

For LACNIC:

• Establish LACNIC membership
• Prepare six-month interconnection timeline (if not yet implemented)
• Document routing policy comprehensively
• Gather complete organizational documentation

For AFRINIC:

• Become AFRINIC resource member
• Prepare technical justification emphasizing network development
• Document interconnection needs clearly
• Emphasize contribution to African Internet infrastructure

Using Via-Registry Services

Navigating different RIR requirements can be complex. Via-Registry.com simplifies ASN registration across all RIRs:

Our services include:

• Expert guidance on RIR-specific requirements
• Application preparation and submission
• Documentation development
• Upstream provider coordination
• Sponsoring LIR services (RIPE region)
• Ongoing registry management

Benefits:

• Higher approval rates with properly prepared applications
• Faster processing through complete documentation
• Cost optimization for your specific situation
• Ongoing support for registry compliance

Learn more about our ASN Registration Service or read our Complete Guide to ASN Registration.

Frequently Asked Questions

Can I choose which RIR to apply to?

No. Your RIR is determined by your organization's geographic location and operational headquarters. You cannot choose a different RIR simply because their requirements are more favorable.

What if my organization operates in multiple RIR regions?

Apply to the RIR where your headquarters and primary operations are located. Your ASN will work globally regardless of which RIR assigned it.

Which RIR has the easiest ASN requirements?

ARIN generally has the most streamlined process with minimal documentation requirements and flexible justification options. However, "easiest" depends on your specific situation.

Do all RIRs accept IPv6-only ASN requests?

Yes, all five RIRs accept ASN requests based on IPv6 allocations, though specific minimum allocation sizes vary by RIR.

Can I transfer my ASN to a different RIR if I relocate?

Inter-RIR ASN transfers are complex and subject to specific policies. Most RIRs allow transfers for legitimate business relocations, but the process is more complicated than intra-RIR transfers.

How often do RIR policies change?

RIR policies evolve through community-driven processes. Major policy changes typically occur every 1-3 years, with smaller updates more frequently. Always check current policies before applying.

Summary

ASN registration requirements vary significantly across the five RIRs:

• RIPE NCC: Requires multi-homing, flexible enforcement, policy changes proposed
• ARIN: Most streamlined process, accepts either multi-homing or unique routing policy
• APNIC: Comprehensive documentation required, two free ASNs per member (2025)
• LACNIC: Six-month planning window, flexible interconnection requirements
• AFRINIC: Multiple justification paths, no separate ASN maintenance fees

Key considerations:

• Your RIR is determined by geographic location
• All RIRs require legitimate routing need demonstration
• Documentation requirements range from minimal (ARIN) to comprehensive (APNIC/LACNIC)
• Costs vary significantly, from flat fees to membership-based models
• Processing times range from 1-3 days (RIPE) to 7-14 days (AFRINIC)

Understanding your RIR's specific requirements is essential for preparing a successful ASN application.

Next Steps

Now that you understand RIR-specific requirements:

• Start planning: Review our Complete Guide to ASN Registration
• Understand costs: Read our Cost Breakdown: ASN Registration Fees
• Prepare justification: Learn How to Prepare Your ASN Justification
• Explore use cases: See ASN Use Cases and Real-World Examples
• Learn fundamentals: Read What is an ASN? How BGP Routing Works