Find answers to common questions about AS Number registration, IP resources, and network services.
As a RIPE NCC member (LIR), we are required to collect the €50 annual ASN maintenance fee mandated by RIPE's new policy. This fee goes directly to RIPE NCC for maintaining the global ASN registry. We pass this cost through transparently with no markup.
Note: Business days follow RIPE NCC schedule (Monday-Friday, 09:00-17:00 CET/CEST, excluding Dutch public holidays). Our support is available Monday-Friday, 09:00-18:00 CET for any questions.
Delays beyond 2 days are rare and typically due to incomplete documentation or verification requirements.
16-bit AS numbers range from 1 to 65,534, while 32-bit AS numbers range from 131,072 to 4,294,967,294. Both function identically in modern networks.
RIPE NCC no longer assigns 16-bit ASNs; they change hands only through transfers between existing holders.
No. RIPE NCC assigns AS numbers from a single 32-bit pool and no longer honors requests for 16-bit numbers; the only way to obtain a 16-bit ASN today is a transfer from an existing holder.
In practice this changes nothing for your network: 16-bit and 32-bit ASNs work identically in modern BGP (RFC 6793).
To register an ASN you need:
A peer is any network you exchange routes with: upstream transit providers, hosting providers with BGP support and Internet Exchange route-servers all count, so most customers already qualify through providers they pay. If you lack in-region infrastructure or a second peer, a Virtua.Cloud VM with BGP provides both.
Active network equipment refers to devices that actively participate in routing and managing network traffic. This includes:
The equipment operates within the RIPE NCC service region, and it does not all have to be live when you apply: signed contracts or orders showing the planned deployment are accepted as supporting documentation. The requirement exists so ASNs go to organizations with genuine networking needs, not speculation or resale.
Multihoming means your AS exchanges routes with at least two other networks. Those peers do not have to be two paid transit contracts: a hosting provider with BGP support, an Internet Exchange route-server or an upstream ISP each count as one peer.
RIPE NCC requires multihoming (or a unique routing policy) to justify an independent ASN, which is why our form asks for two peers.
Required documentation depends on your entity type:
Important: All information provided must be accurate and verifiable. Submitting false or forged documents will result in immediate rejection of your application, possible account suspension, and may be reported to the relevant authorities. Your registration details will be publicly visible in the RIPE WHOIS database. Unlike domain registration, ASN registration does not allow anonymous or proxy registration - your real organization or personal details will be published in the global routing registry.
Yes, we lease IPv4 blocks (from /24) to customers holding an ASN through us. IPv4 is lease-only: we do not offer PI IPv4 sponsorship.
Demand is high and our inventory is currently exhausted, so new requests join a waitlist and are served in order when space frees up.
If you need address space today, IPv6 blocks (from /48) are available immediately and are included as an option during ASN registration.
Important: Transfers work both ways. If you ever decide to change providers in the future, you can transfer your ASN to another sponsor. You maintain ownership of your ASN regardless of who sponsors it.
If you need to become a RIPE LIR yourself in the future, we can assist with that process as well.
You still keep full control of your ASN. Day-to-day changes are made in your Via-Registry portal: route and AS-SET objects, contact and abuse details, routing policies. We push every change to the RIPE database for you, usually within minutes.
Prefer to work in the RIPE database directly? Provide your own mntner handle when you order and we will place the admin-c, tech-c, abuse-c and route objects under your maintainer. You can then edit them yourself with a free RIPE NCC Access account. Only a few fields on the ORG object, such as the legal name, remain editable by RIPE NCC alone.
We handle all of these for you automatically, ensuring your routes are properly authorized and secured from day one.
Yes. Your ASN is completely portable: use it with any hosting provider, data center or ISP that supports BGP, and we provide LOAs for any provider you choose. You are never locked in.
If you host with our partner Virtua.Cloud, BGP sessions are included with your VM at no extra charge and their invoices are accepted directly as supporting documentation for your registration.
Important: Once an ASN is returned to RIPE, you cannot get the same number back. If you might need it again in the future, consider transferring it instead of cancelling.
Your network equipment must be physically located in one of these regions to qualify for ASN registration through RIPE NCC. If your equipment is in the Americas, Asia-Pacific, or Africa, you'll need to work with the respective regional registry (ARIN, APNIC, or AFRINIC).
The main difference is the documentation required: businesses need company registration documents, while individuals need valid government ID. All other requirements (multihoming, active equipment, etc.) remain the same.
We offer IPv6 blocks in four sizes:
Current pricing per size is shown during registration; you can start small and add a larger block later.
Once payment is received, your ASN is instantly renewed for another year. No paperwork or re-verification required - just a simple payment process.
Instead of dealing with RIPE's technical syntax and authentication methods, you use our simple web interface. We translate your requests into proper RIPE database updates automatically.
Each ASN requires its own justification and must meet RIPE requirements independently. We offer:
Contact us if you need 5 or more ASNs - we can discuss enterprise arrangements.
Whether you use AWS, Google Cloud, OVH, Hetzner, or any other provider - your IPs work everywhere. Simply provide us with your provider details and we'll handle the authorization documentation.
The work behind our services starts as soon as your order arrives: reviewing your documents, preparing the application and handling the exchanges with RIPE NCC. That time cannot be recovered once it has been spent, which is why fees cannot be returned.
This applies to:
RIPE NCC, the regional Internet registry for Europe, the Middle East and Central Asia, charges €50 per year for every ASN assigned through a sponsoring LIR. That charge is set by the RIPE NCC Charging Scheme 2026 (RIPE-848) and is billed to us, as your sponsoring LIR.
We pass it through at cost: the €50 on your invoice is exactly what RIPE NCC charges us for your ASN. RIPE NCC members review the charging scheme every year, so the amount follows the scheme in force.
RIPE NCC only works with its member LIRs, so every sponsored ASN needs an LIR doing real work behind it. Your service fee pays for that work:
An ASN looks like just a number, but both the registry and the sponsorship behind it carry yearly costs.
If privacy is a priority, we recommend registering the ASN under a company name.
Yes. Your organization can be legally established anywhere in the world: what RIPE NCC requires is that the network using the ASN is operated within their service region (Europe, the Middle East and Central Asia), and your supporting documentation must show that.
The simplest way to get an in-region network is a VM with BGP at a provider like Virtua.Cloud; any in-region hosting or transit provider works too.
Usually yes. The two required peers do not have to be two transit contracts: your hosting provider (with BGP support) counts, an Internet Exchange route-server counts, and a second uplink that is still in planning can be documented with a letter or contract.
If you truly have a single network connection, deploying one VM with BGP at Virtua.Cloud adds the missing peers in one step.
Yes. RIPE NCC wants to see a real project: a network with active equipment, IP space to announce and two BGP peers. It does not all have to be live on day one; signed contracts or orders showing the network is planned are accepted as supporting documentation.
If you would rather have something running immediately, a single VM with the BGP option at Virtua.Cloud provides the equipment and peers in minutes, and its invoice is accepted directly. Either way, once your documentation is ready, complete your registration normally.
During registration, once the sponsorship agreement exists, putting it under a different person or company requires re-issuing and re-signing it; per our Terms of Service this carries a €25 re-signing fee, arranged through support@via-registry.com.
After a registration is completed, moving the ASN to a different legal entity is a separate procedure billed at the administration fee. If you already know which entity should hold the ASN, start the registration under that entity.
30 days. The countdown starts when your payment is confirmed, and a warning email goes out after 25 days if the registration is still incomplete.
Registrations not completed within 30 days are closed automatically and, per our Terms of Service, fees are not refunded, though you can start a new registration afterwards. Most customers finish in well under a week.
Our support team is here to help you with any questions about AS Number registration, IP resources, or network services.
Questions? Ask the AI assistant It answers most questions instantly. Contact form