ASN Registration: Establish Your Network Identity
Register your Autonomous System Number (ASN) through RIPE NCC.
Complete technical support for ASN registration, BGP configuration, and routing policy setup.
Part of our Registry Services
TL;DR Summary
Register your Autonomous System Number with RIPE NCC sponsorship and support.
What is an Autonomous System Number?
An ASN (Autonomous System Number) is a globally unique identifier assigned to an autonomous system (AS) - a collection of IP networks under a single administrative domain with a defined routing policy.
ASNs are used in BGP (Border Gateway Protocol) to exchange routing information between different networks on the internet. Your ASN identifies your network when peering with other networks, ISPs, or internet exchanges.
When you announce IP prefixes via BGP, your ASN serves as the origin identifier. This enables other networks to make routing decisions and establish peering relationships with your autonomous system.
Why You Need an ASN
ASN registration is required for specific network operations and business needs:
BGP Routing Control
Implement independent routing policies and control how traffic enters and exits your network.
Multi-Homing
Connect to multiple upstream ISPs simultaneously for redundancy and traffic optimization.
Internet Exchange Peering
Peer directly with other networks at IXPs (Internet Exchange Points) to reduce latency and transit costs.
Network Identity
Establish your organization as an independent network operator with a recognized presence in global routing tables.
ASN Types: 16-bit vs 32-bit
ASNs come in two formats with different numbering ranges and availability.
| Feature | 16-bit ASN | 32-bit ASN |
|---|---|---|
| Number Range | AS1 - AS65535 | AS4200000000 - AS4294967294 |
| Format | 2-byte (original) | 4-byte (extended) |
| Availability | Limited (mostly allocated) | Widely available |
| Allocation Cost | Standard RIPE fees | Standard RIPE fees |
| Best For | Established operators (if available) | New network deployments |
Note: Both formats function identically in modern BGP implementations. 32-bit ASNs are recommended for new allocations due to better availability.
ASN Registration Process
Step-by-step path from application to active BGP peering
LIR Verification
Confirm LIR membership status or arrange RIPE NCC sponsorship through Virtuasys.
Justification Documentation
Prepare technical justification demonstrating need for independent routing (multi-homing, IXP peering, etc.).
RIPE NCC Submission
Submit ASN request to RIPE NCC with complete documentation and routing policy details.
Review & Approval
RIPE NCC reviews justification and validates technical requirements (1-2 weeks typical).
ASN Assignment
Receive ASN allocation and create AS object in RIPE database with routing policy.
BGP Configuration
Configure BGP sessions, establish peering relationships, and announce your IP prefixes.
Technical Requirements
Prerequisites for successful ASN registration
LIR Membership
Active RIPE NCC LIR membership or approved sponsorship arrangement.
Virtuasys offers LIR sponsorship services if you're not a direct member.
Routing Justification
Valid technical need for independent routing (multi-homing to multiple ISPs, IXP peering, or specific routing policies).
Single-homed networks typically don't require an ASN.
IP Address Resources
Assigned IPv4 or IPv6 address space to announce via BGP.
ASN without IP addresses has limited utility - consider IPv4/IPv6 allocation.
BGP-Capable Equipment
Router or BGP-capable device to establish peering sessions and announce routes.
Must support your chosen ASN format (16-bit or 32-bit).
RIPE NCC Requirements
RIPE NCC enforces specific policies for ASN allocation in the European service region:
Multi-Homing Requirement
Demonstrate multi-homed connectivity or intent to peer at internet exchanges. Single-homed networks should use provider ASN.
Documented Routing Policy
Define and document your intended routing policy in the RIPE database (aut-num object).
Technical Contacts
Assign qualified technical contacts with BGP knowledge to manage your ASN.
Accurate Registration Data
Maintain current and accurate contact information and routing policy in RIPE database.
ASN Registration Use Cases
Common scenarios requiring autonomous system registration
Internet Service Provider
ISPs require ASNs to establish peering relationships with multiple upstream providers and internet exchanges.
Requirements:
Multi-homed connectivity, BGP-capable infrastructure, IP address allocations for customer assignments.
Example:
Regional ISP with connections to Tier 1 providers and local IXP presence.
Hosting & Cloud Provider
Large-scale hosting operations use ASNs for optimal routing and redundancy across multiple datacenters.
Requirements:
Multiple datacenter locations, diverse ISP connectivity, substantial IP address space (/22 or larger).
Example:
Managed hosting provider with facilities in multiple countries and IXP peering.
Global Enterprise Network
Multinational organizations with distributed operations benefit from ASN-controlled routing policies.
Requirements:
Multiple site locations, direct internet connectivity at each site, need for traffic engineering.
Example:
Financial services company with datacenters in multiple regions requiring precise routing control.
Content Delivery Network
CDNs use ASNs with BGP anycast to route users to nearest edge location for optimal performance.
Requirements:
Distributed point-of-presence infrastructure, anycast addressing, extensive IXP peering.
Example:
Video streaming platform with edge caches at 20+ locations worldwide.
ASN vs IP Addresses: Understanding the Relationship
ASNs and IP addresses serve different but complementary purposes in network operations:
Autonomous System Number
Purpose:
Identifies your network in BGP routing system
Function:
Used for establishing peering relationships and route exchange
Requirement:
Required for multi-homing and independent routing
Quantity:
One ASN per autonomous system (though organizations may have multiple ASes)
IP Address Space
Purpose:
Addresses assigned to devices and services on your network
Function:
Actual endpoints for network communication
Requirement:
Required for any network connectivity
Quantity:
Blocks of addresses based on your network size (/24, /22, /20, etc.)
Relationship: Your ASN announces IP address prefixes via BGP. When you peer with another network, you advertise which IP blocks are reachable through your AS. Both resources are typically required for independent network operations.
You can have IP addresses without an ASN (common for single-homed networks), but an ASN without IP addresses has limited utility.
ASN Setup & Configuration Support
Virtuasys provides complete technical support for ASN deployment:
RIPE Database Objects
Create and configure aut-num, route, and route6 objects with correct routing policy syntax.
ROA Configuration
Set up Route Origin Authorization (ROA) for RPKI validation to prevent prefix hijacking.
BGP Configuration
Assist with BGP session setup, prefix filtering, and routing policy implementation.
Peering Coordination
Help establish peering relationships with ISPs and internet exchange points.
Reverse DNS Delegation
Configure reverse DNS zones for your announced IP prefixes.
24/7 Monitoring
Ongoing monitoring of BGP announcements and routing table visibility.
Frequently Asked Questions
Common questions about ASN registration and network identity
Request ASN Registration
Contact us to discuss your routing requirements and begin the ASN allocation process.
Our team handles all RIPE NCC coordination and provides complete technical support.
Or view IPv4 allocation options