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.
- 32-bit ASN registered at RIPE NCC
- IPv6
/40included - RIPE justification drafted for you
aut-num,as-set,route6published- RPKI ROA signed and deployed
- Initial routing policy drafted
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.
- 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.
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.
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.
The RIPE ASN Management Panel, Click Through Every Tab
Once your ASN is live, this self-service panel is yours. Every tab below actually switches, exactly like the real thing. Click AS-SET, Details & Contacts, IRR Policy, BGP Config or any other tab to see what you manage from your account.
Route Objects (IRR)
Register the prefixes you announce in the RIPE routing registry. Upstreams and IX route servers use these to validate your BGP announcements.
Active Route Objects
| Prefix | Type | Origin | Status | |
|---|---|---|---|---|
| 212.81.56.0/24 | route | AS57050 | active | Delete |
| 2a10:fa80:12::/48 | route6 | AS57050 | active | Delete |
AS-SET Management
An AS-SET groups your ASN with your downstream customers. Upstreams build prefix filters from it. It is always created under your own ASN.
Details & Contacts
Live in RIPEThe fields currently on your aut-num. Edit and Save to change them. admin-c and tech-c must point to a person or role that already exists.
Abuse contact (abuse-c)
Your Contacts
| Handle | Created | |
|---|---|---|
| JD1503-RIPE | 2026-06-14 10:22 | Use Edit Delete |
BGP Visibility & Announced Prefixes
Live data from RIPE RIS route collectors. Check whether your ASN is seen in the global routing table.
Check BGP VisibilityRouting Policy
Live in RIPEThe policy currently published for AS57050. Edit the RPSL statements, one per line, and Save to update it in the RIPE DB.
Generate policy lines from peers
Build RPSL import/export from a peer list, then insert it straight into the boxes above.
BGP Configuration Generator
Ready-to-paste BGP configuration for your router platform, built from your peer list.
# BIRD 2.x BGP Configuration for AS57050
protocol bgp upstream_dreamserver {
local as 57050;
neighbor 212.81.56.1 as 174; # Replace IP
ipv4 {
import all;
export filter export_own;
};
}! FRRouting BGP Configuration for AS57050 router bgp 57050 bgp router-id 212.81.56.10 neighbor 212.81.56.1 remote-as 174 neighbor 212.81.56.1 description DreamServer-upstream ! address-family ipv4 unicast network 212.81.56.0/24 exit-address-family exit
# MikroTik RouterOS v7 BGP for AS57050
/routing bgp template
add name=default as=57050 router-id=212.81.56.10
/routing bgp connection
add name=upstream remote.as=174 \
remote.address=212.81.56.1 \
local.role=customer templates=default!! Cisco IOS-XR BGP for AS57050 router bgp 57050 bgp router-id 212.81.56.10 neighbor 212.81.56.1 remote-as 174 address-family ipv4 unicast route-policy ACCEPT-ALL in route-policy EXPORT-OWN out ! !
RIPE WHOIS Lookup
Look up your own RIPE DB objects. Queries are restricted to your ASN and related objects.
aut-num: AS57050 as-name: EXAMPLE-NET org: ORG-EX12-RIPE import: from AS174 accept ANY export: to AS174 announce AS-SELF admin-c: JD1503-RIPE tech-c: JD1503-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: DreamServer mnt-by: EXAMPLE-MNT source: RIPE
Read-only preview. All names, handles and numbers shown are fictional. Your real panel is populated live from the RIPE Database.
What you manage from the panel
The moment your ASN is delivered, every object it needs is editable from your DreamServer account. No RIPE Portal logins, no email tickets to change a contact or a route object.
Route Objects (IRR)
Create or delete route and route6 objects for every prefix you announce, so upstreams and IX route servers accept your BGP advertisements. Origin AS is filled in for you.
AS-SET
Build and maintain your customer cone (AS57050:AS-CUSTOMERS) so providers can filter your downstreams. It is always namespaced under your own ASN, so you cannot touch anyone else's.
Details & Contacts
Edit descr, admin-c and tech-c on your aut-num, see the abuse-c, and create or manage RIPE person contacts, with existence checks so a handle never fails silently.
BGP Status
Live visibility from RIPE RIS route collectors: how many peers see your ASN over IPv4 and IPv6, which prefixes are announced, and when it was first and last seen.
IRR Policy
Read and edit the import/export/mp-import/mp-export policy published on your aut-num, or generate the RPSL from a simple peer list and drop it straight into the boxes.
BGP Config
Copy-paste BGP configuration for BIRD, FRRouting, MikroTik RouterOS and Cisco IOS-XR, generated from your peer list so your first session takes minutes.
WHOIS
Look up your ASN and its related objects straight from the RIPE Database, without leaving the panel or learning the whois command line.
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.
ASN Registration FAQ
Everything we get asked about registering, pricing and using a new AS number.
What exactly is an ASN?
32-bit vs 16-bit ASN, which will I get?
Do I have to become a RIPE NCC member myself?
What justification does RIPE need for a new ASN?
What does the 100 EUR application fee cover?
Can I bring my own IPv6 instead of taking the bundled /40?
/40 and apply a 12 €/year discount. Contact us for the custom quote.Is RPKI mandatory these days?
How do I connect the new ASN to my hardware?
Can I peer at DSIX with this ASN?
What happens if I want to leave DreamServer later?
mnt-by, update the org attribute and hand over the resource with zero routing impact.
