ASN + /40 IPv6 bundle • BGP-ready in 5-7 business days

ASN Registration

Own a 32-bit Autonomous System Number registered at RIPE NCC, ready for BGP announcements across any transit provider or internet exchange. The bundle includes a /40 IPv6 prefix, aut-num, as-set, RPKI ROA and a first-draft routing policy, everything a new ASN needs to start peering.

Order ASN bundle How does it work?
Total cost year one
200 €
setup + first year
100 € one-time RIPE fee + 100 €/year ongoing
  • 32-bit ASN registered at RIPE NCC
  • IPv6 /40 included
  • RIPE justification drafted for you
  • aut-num, as-set, route6 published
  • RPKI ROA signed and deployed
  • Initial routing policy drafted
When you need your own ASN

Three signals that mean it is time to stop using your provider's AS

1. Two or more upstream transits. The moment you want redundancy across carriers, you need a single ASN that announces the same prefix to all of them. Otherwise traffic gets fragmented, BGP communities become meaningless and RPKI cannot protect you.

2. Peering strategy at IXPs. Internet exchange route servers only accept announcements from members with their own ASN and a matching RPKI ROA. Peering at DSIX, DE-CIX, AMS-IX or any other IX requires your AS number, period.

3. Regulatory or contractual independence. Some customers, insurers or regulators require that you operate your own AS and keep it independently routable. Without an ASN you are a sub-tenant of your upstream; with one you are a peer on the global routing table.

Signals you do NOT need an ASN yet
  • You run a handful of servers on a single provider, their ASN announces your traffic already.
  • You do not have a plan to BGP-announce prefixes. An ASN without announcements is a paper certificate.
  • Your use case is better served by CDN/Anycast or cloud load balancers.
Unsure? Ask us for a 10-minute fit check before ordering, we would rather talk you out of a bad ASN decision than sell you one that sits idle.

Your ASN, sponsored and BGP-ready

Open a ticket with a short description of your routing plan and we will draft the RIPE justification today.

Start my ASN request Email us

Everything inside the 100 €/year bundle

One price, one sponsor, one contact. Every object a new AS needs to peer, route and survive RPKI filtering.

32-bit ASN registered at RIPE

A 4-byte AS number assigned to your organisation by RIPE NCC. Full ownership; you remain the sole admin-c and tech-c, we simply sponsor under our LIR.

Bundled IPv6 /40

The /40 prefix that would cost 12 €/year standalone is included at no extra charge. Enough for 65,536 customer /56s and ready to announce from day one.

Justification drafted by us

RIPE requires a written case showing you will multi-home or peer with a unique routing policy. We draft it for you, based on a short intake questionnaire, and submit it through our LIR account.

aut-num object published

Created with your admin-c, tech-c, abuse-c and a sensible initial routing policy (import/export from upstream and peers). Visible on the global RIPE DB the moment RIPE approves the ASN.

as-set and route filters

An as-set in the naming convention RIPE expects (AS-YOURASN) plus route6 objects authorising your announcement. Required by IXP route servers, MANRS filters and Cloudflare's validator.

RPKI ROA + validator help

We sign the ROA for your prefix, origin-validate against MANRS recommendations, and deliver router snippets for Cisco, Juniper, Arista, MikroTik, VyOS and BIRD if you want to run your own validator.

Typical timeline

5 to 7 business days from intake to first BGP session

The RIPE NCC side usually takes three to five business days; the rest is documentation and post-allocation automation on our end.

DAY 1

Intake & justification

We collect your legal entity info, intended upstreams, peering plans and target IPv6 address. Draft the RIPE justification email the same day.

DAY 2

Submission to RIPE

We submit the ASN request through our LIR Portal. Any RIPE clarification goes back via our support queue, you do not see the ticket thread.

DAY 3-5

RIPE review

RIPE Registration Services reviews the case. Typical SLA is 5 business days; often they approve within 2-3 if the justification is tight.

DAY 5-6

Objects & RPKI

aut-num, as-set, route6 created. RPKI ROA signed against your new ASN. mnt-by delivered.

DAY 7

Peer & announce

Credentials handed over. First BGP session established with your upstream, first prefix seen on a looking glass.

Pair with

A fresh ASN benefits from professional BGP setup and ongoing monitoring. Or if you already own an ASN elsewhere, move the sponsorship over.

BGP Services
Multi-home, RPKI, MANRS
LIR Sponsoring
Move an existing ASN to us
IPv6 Lease
Standalone subnets from 5 €/yr

ASN Registration FAQ

Everything we get asked about registering, pricing and using a new AS number.

What exactly is an ASN?
An Autonomous System Number is a globally unique 32-bit integer that identifies a routing domain on the internet. Every BGP announcement on the default-free zone carries an AS_PATH made of ASNs. Owning one means you can independently originate prefixes and run your own routing policy instead of sitting inside your provider's AS.
32-bit vs 16-bit ASN, which will I get?
RIPE has been assigning only 32-bit (4-byte) ASNs for new requests since 2011. 16-bit ASNs are fully exhausted for new assignments. 32-bit ASNs look like AS213123, AS206499, etc. Every modern BGP stack transparently handles 32-bit ASNs, including Cisco IOS 12.0(32)S13+, Juniper Junos 9.1+, Arista EOS, MikroTik 6+, BIRD, FRRouting, etc.
Do I have to become a RIPE NCC member myself?
No. We sponsor the ASN under our existing LIR membership. You keep full ownership (admin-c, tech-c, legal control) and the ASN is yours, but the annual RIPE NCC membership fee and portal work belongs to us. This is the whole point of LIR sponsorship.
What justification does RIPE need for a new ASN?
RIPE wants to see evidence that you will run a unique routing policy, which in practice means multi-homing (two or more transits) or peering at an IX. We write the justification for you based on a short questionnaire, intended upstreams, target prefixes, geographic scope, expected peering stance. Typical submissions are 10-15 lines of prose.
What does the 100 EUR application fee cover?
That is the one-time RIPE NCC resource fee for a new ASN, paid from our LIR account on your behalf. RIPE issues us one invoice per assignment; we pass it through at cost. Nothing on top, nothing hidden.
Can I bring my own IPv6 instead of taking the bundled /40?
Yes. If you already own IPv6 (for example PI space or a block from another LIR that we can sponsor), we register the ASN without the bundled /40 and apply a 12 €/year discount. Contact us for the custom quote.
Is RPKI mandatory these days?
It is not formally mandatory but it is effectively required. Without an RPKI ROA your prefix will be marked invalid by any RPKI-enforcing validator, which means Cloudflare, most tier-1 transit providers and the major IX route servers will drop the announcement. We sign ROAs for every prefix we deliver.
How do I connect the new ASN to my hardware?
We send you ready-to-paste BGP configuration snippets for the most common platforms (Cisco, Juniper, Arista, MikroTik, VyOS, Cumulus, BIRD, FRR). Typical first session is 10-15 minutes of config on your router plus matching configuration on the upstream or IX side.
Can I peer at DSIX with this ASN?
Absolutely. DSIX (AS58218) is our own internet exchange and new ASNs under our LIR are welcome on the fabric. We pre-configure filters on the route servers and can run the first BGP session on the same day the ASN is assigned.
What happens if I want to leave DreamServer later?
The ASN stays yours. Sponsorship at RIPE NCC is non-exclusive; you can transfer the sponsorship to another LIR or become your own RIPE member at any time. We remove our mnt-by, update the org attribute and hand over the resource with zero routing impact.
Can I get multiple ASNs?
Yes, but RIPE policy now requires a stronger justification for additional ASNs, typically a genuinely different routing policy, geographic region, or operational reason (for instance separating content from transit). We have experience drafting multi-ASN justifications.
Do you support 2-byte (16-bit) legacy ASN transfers?
Yes. If you own a legacy 2-byte ASN under another LIR and want to transfer the sponsorship to us, we handle the RIPE paperwork. The ASN keeps its number, we simply take over the sponsoring role. See our LIR Sponsoring page.
Can you advertise my prefix through your own network too?
Yes. If you want DreamServer AS57050 to accept your prefix as a customer cone, we can transit your announcement as an upstream. Ask us for a transit quote, it stacks cleanly on top of the ASN registration and is often how new ASNs get their first BGP session live.

Trusted By & Member Of

We are proud members of leading internet infrastructure organizations.

RIPE NCC MANRS PeeringDB RoTLD DSIX SBIX 4IXP LOCIX Euro-IX RIPE NCC MANRS PeeringDB RoTLD DSIX SBIX 4IXP LOCIX Euro-IX