How to get an ASN
You get a public ASN from a RIR (e.g. RIPE NCC) through an LIR. Learn the requirements, application steps, costs, and when you actually need your own ASN.
Last updated:
You obtain a public ASN (Autonomous System Number) from a Regional Internet Registry (RIR). In Europe and the Middle East that is the RIPE NCC. You apply through a Local Internet Registry (LIR). An ASN is a globally unique identifier for your network in BGP routing. To qualify, you must show that you will run multihoming or operate your own routing policy distinct from that of your providers.
When you need your own ASN
Your own ASN makes sense when you connect to the internet through at least two operators (multihoming) or run an independent routing policy, for example announcing your own IPv4/IPv6 prefixes to multiple peers and transits. If you buy a single transit and do not run BGP, you do not need an ASN. The RIPE NCC now assigns mostly 32-bit ASNs, which BGP carries as defined in RFC 6793. The 16-bit pool (0 to 65535) is nearly exhausted, so new assignments are usually from the 4-byte range.
- Multihoming, connecting to two or more operators at the same time
- An independent routing policy different from your upstream providers
- Peering at internet exchange points (IXPs), such as THINX or TPIX
- Announcing your own address space (PI or PA) over BGP
- Private ranges (64512 to 65534 and 4200000000 to 4294967294, RFC 6996) for internal use only, not the public internet
Requirements and the role of the LIR
The RIR does not assign ASNs directly to end users. It does so through an LIR, an organization with a membership agreement with the RIPE NCC. You can become an LIR yourself or have an existing LIR handle the request as a sponsor. The application must document your routing plan: who you will peer with or take transit from, and why your provider's ASN is not enough. You also create an aut-num object in the RIPE Database, and eventually link it to route/route6 objects in the IRR.
Steps and costs
The process is repeatable. You choose an LIR (or become one), assemble your multihoming justification, submit the ASN request, and after assignment configure BGP sessions and register IRR objects plus ROAs for RPKI. Costs depend on the model. RIPE NCC LIR membership is an annual fee (EUR 1,800 in 2025 and 2026) plus a one-off sign-up fee and EUR 50 for the ASN assignment itself. Under sponsorship by an existing LIR you skip the membership fee and pay only their handling rate for the ASN.
- Choose a model: your own LIR or sponsorship by an existing LIR
- Prepare the justification (two peers/transits or an independent policy)
- Submit the ASN request and create the aut-num object in the RIPE Database
- Configure BGP sessions with upstreams and at IXPs once the number is assigned
- Register route/route6 in the IRR and create ROAs for RPKI validation
Your ASN and AS202520 SkyPass services
Once you hold your own ASN, AS202520 SkyPass connects it to the internet. We provide IP transit and BGP peering at PoPs in Warsaw and Wrocław, plus remote access to Polish IXPs: THINX, TPIX, WRIX and 1-IX. We help you set up BGP sessions, IRR objects and ROAs for RPKI correctly, so your prefixes are announced safely and visible globally. For a freshly assigned number, this is the fastest path to multihoming and full control over your routing policy.
Frequently asked questions
Can I get an ASN without becoming an LIR?
Yes. An existing LIR can submit the request on your behalf as a sponsor. You then pay that LIR's handling rate, without the annual RIPE NCC membership fee.
What is the difference between a 16-bit and a 32-bit ASN?
A 16-bit ASN sits in the 0 to 65535 range and is effectively exhausted. New assignments are 32-bit numbers, carried in BGP as defined in RFC 6793. Modern implementations support them fully.
Do I need my own IP addresses to get an ASN?
Not always. You can announce PA space received from an LIR. To justify the ASN, however, you must demonstrate multihoming or an independent routing policy.
How long does it take to get an ASN from the RIPE NCC?
Once a complete, well-justified request is submitted, assignment usually happens within a few business days. Preparing the multihoming documentation takes the most time.