ASN Registration: RIPE ASN, BGP and RPKI Included
ASN registration through RIPE NCC on AS35661, delivered in 2-5 working days. BGP and RPKI setup included.
Get a quote
Answer within one business day.
Quick summary
RIPE ASN registration through Virtuasys as your RIPE NCC LIR (AS35661). Full setup included: RIPE objects, BGP configuration and RPKI/ROA, delivered in 2-5 working days.
- Delivery
- 2-5 working days
- Formats
- 16-bit and 32-bit
- Setup included
- BGP, RPKI, rDNS
- Eligibility
- Multi-homing or IXP peering
ASN specifications and delivery
| Number range | 16-bit: AS1-AS65535 (mostly allocated). 32-bit: AS4200000000-AS4294967294 (widely available) |
| Format | 16-bit is 2-byte (original format), 32-bit is 4-byte (extended format); both run identically in modern BGP |
| Recommended format | 32-bit for new registrations, on availability grounds; both formats supported by all current router platforms |
| Delivery | 2-5 working days from complete application to RIPE NCC activation |
| Routing justification | Multi-homing to multiple ISPs or peering at an internet exchange; single-homed networks use their provider's ASN instead |
| Equipment requirement | BGP-capable router or device able to establish peering sessions and announce routes |
| Setup included | RIPE database objects (aut-num, route, route6), ROA/RPKI configuration, BGP session setup, peering coordination, reverse DNS delegation |
| Support | 24/7 monitoring of BGP announcements and routing table visibility |
Who registers an ASN
- ISPs and hosting providers
- Multi-homed connectivity to Tier 1 providers and IXPs, or multi-datacenter routing with substantial IP space (/22 or larger).
- Multi-site enterprise
- Direct internet connectivity at each site with independent routing policy and traffic engineering control.
- CDN and anycast operators
- BGP anycast across distributed points of presence, routing users to the nearest edge location.
What the registration covers
Virtuasys handles the full path from application to active BGP peering: LIR verification or sponsorship arrangement, technical justification, RIPE NCC submission, and ASN assignment. Once assigned, we configure RIPE database objects, ROA for RPKI validation, BGP sessions and reverse DNS delegation, and monitor your announcements afterward.
- Delivery
- 2-5 working days
- RIPE NCC member since
- 2008
- Monitoring
- 24/7
ASN registration FAQ
2-5 working days from application submission to RIPE NCC approval and ASN activation, depending on application completeness and the RIPE NCC processing queue.
ASN allocation requires direct RIPE NCC LIR membership or an approved sponsorship arrangement; Virtuasys offers LIR sponsorship for organizations that don't want direct membership. RIPE NCC policy also requires multi-homing or IXP-peering justification; single-homed networks should use their provider's ASN instead.
RIPE NCC charges its own allocation fees regardless of provider, and the total also depends on whether you hold direct LIR membership or use sponsorship. Ask through the form and you get a firm quote based on your actual setup.
RPKI validates BGP route announcements; ROA (Route Origin Authorization) objects specify which ASN may announce your prefixes. Not mandatory, but strongly recommended: major networks filter BGP announcements without valid ROAs. Included in setup.
Request ASN Registration
Tell us your routing requirements. We handle the RIPE NCC submission and full BGP/RPKI setup.