LIR Sponsoring
Your current LIR is closing, charging too much or not answering tickets? Move the sponsorship of your existing IPv4 and IPv6 prefixes or ASN to DreamServer's RIPE NCC LIR in a single coordinated change. Your announcements stay on the routing table, your RPKI ROAs stay signed, only the mnt-by, org and sponsoring attributes change in the database.
- No RIPE transfer fee on our side
- RPKI continuity preserved
- Annual RIPE audit handled
- Cancel anytime, move back out
- Full ownership retained
Four reasons your current LIR has become a liability
The LIR is closing. RIPE NCC membership is a recurring cost; smaller LIRs that have run out of customers sometimes wind down operations. If your sponsor closes without arranging a hand-over, your resources can end up in limbo.
Pricing has drifted. Annual sponsorship fees of 200-400 € per resource are common. If you are paying far above market rate for administrative work your current LIR has automated, it is time to re-shop.
Operational neglect. Delayed RPKI ROA updates, ignored abuse-c rotations, late audit responses or no support during routing emergencies, any of these signal that your LIR is not investing in the infrastructure your resources depend on.
Strategic concentration. You already run services on DreamServer infrastructure or peer with us at DSIX, and consolidating LIR administration simplifies your vendor footprint and support loop.
- ASN number and every IPv4 or IPv6 prefix stay identical
- Your BGP announcements never pause
- Admin-c, tech-c and legal ownership stay with you
- RPKI ROAs remain published without interruption
- Existing peering relationships stay in place
mnt-by, org and sponsoring attributes at RIPE change. Your routers and peers never notice.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.
The IPv4 and IPv6 RIPE Management Panel, Click Through Every Tab
The moment your IPv4 or IPv6 prefix moves under our sponsorship, this self-service panel becomes yours. Every tab below actually switches, exactly like the real thing. Click ROA / RPKI, Reverse DNS, inetnum / inet6num, WHOIS or any other tab to see the interface you manage for every sponsored prefix, IPv4 or IPv6.
| Prefix | Origin AS | Status | Created | Actions |
|---|---|---|---|---|
| 2a10:fa80:aaaa::/40 | AS213123 | Active | 2026-04-08 10:42 | ViewDelete |
| 2a10:fa80:aaaa:1000::/44 | AS213123 | Active | 2026-04-12 15:08 | ViewDelete |
| 185.72.40.0/24 | AS213123 | Active | 2026-04-09 09:15 | ViewDelete |
| Prefix | Max Length | ASN | Status | Created | Actions |
|---|---|---|---|---|---|
| 2a10:fa80:aaaa::/40 | /48 | AS213123 | Active | 2026-04-08 10:44 | Delete |
| 2a10:fa80:aaaa:1000::/44 | /48 | AS213123 | Active | 2026-04-12 15:10 | Delete |
| 2a10:fa80:aaaa::/40 | /40 | AS65001 | Active | 2026-04-14 09:21 | Delete |
| 185.72.40.0/24 | /24 | AS213123 | Active | 2026-04-09 09:17 | Delete |
| Zone | Nameservers | Status | Actions |
|---|---|---|---|
| a.a.a.a.0.4.b.6.b.0.a.2.ip6.arpa | ns1.example.comns2.example.com | Active | EditDelete |
| 40.72.185.in-addr.arpa | ns1.example.comns2.example.com | Active | EditDelete |
IPv6 inet6num (2a10:fa80:aaaa::/40)
| inet6num | 2a10:fa80:aaaa::/40 |
| netname | EXAMPLE-NET |
| descr | Example Ltd. IPv6 allocation |
| country | RO |
| org | ORG-EXML1-RIPE |
| admin-c | JD1234-RIPE |
| tech-c | JD1234-RIPE |
| status | ALLOCATED-BY-LIR |
| mnt-by | MNT-EXAMPLE |
| source | RIPE |
IPv4 inetnum (185.72.40.0/24)
| inetnum | 185.72.40.0 - 185.72.40.255 |
| netname | EXAMPLE-NET |
| descr | Example Ltd. IPv4 PA assignment |
| country | RO |
| org | ORG-EXML1-RIPE |
| admin-c | JD1234-RIPE |
| tech-c | JD1234-RIPE |
| status | ASSIGNED PA |
| mnt-by | MNT-EXAMPLE |
| source | RIPE |
Update Fields
| Type | Key | Handle | Status | Actions |
|---|---|---|---|---|
| inet6num | 2a10:fa80:aaaa::/40 | EXAMPLE-NET | Active | ViewRIPE → |
| inetnum | 185.72.40.0/24 | EXAMPLE-NET | Active | ViewRIPE → |
| organisation | ORG-EXML1-RIPE | Example Ltd. | Active | ViewRIPE → |
| mntner | MNT-EXAMPLE | MNT-EXAMPLE | Active | ViewRIPE → |
| role | JD1234-RIPE | J. Doe | Active | ViewRIPE → |
| route6 | 2a10:fa80:aaaa::/40 | AS213123 | Active | ViewRIPE → |
| route6 | 2a10:fa80:aaaa:1000::/44 | AS213123 | Active | ViewRIPE → |
| route | 185.72.40.0/24 | AS213123 | Active | ViewRIPE → |
| Subnet | Label | Description | Status | Actions |
|---|---|---|---|---|
| 2a10:fa80:aaaa:0::/48 | Web Servers | Public-facing web cluster | Used | EditDelete |
| 2a10:fa80:aaaa:1::/48 | SMTP / IMAP / MX | Used | EditDelete | |
| 2a10:fa80:aaaa:100::/56 | Staging | Reserved for staging env | Reserved | EditDelete |
# First 5 of 256 subnets 2a10:fa80:aaaa:0000::/48 → first: 2a10:fa80:aaaa:: last: 2a10:fa80:aaaa:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0001::/48 → first: 2a10:fa80:aaaa:1:: last: 2a10:fa80:aaaa:1:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0002::/48 → first: 2a10:fa80:aaaa:2:: last: 2a10:fa80:aaaa:2:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0003::/48 → first: 2a10:fa80:aaaa:3:: last: 2a10:fa80:aaaa:3:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0004::/48 → first: 2a10:fa80:aaaa:4:: last: 2a10:fa80:aaaa:4:ffff:ffff:ffff:ffff:ffff ... 251 more
# BIRD 2.x IPv6 BGP to AS6939 router id 213.214.215.216; protocol static { ipv6 { table master6; }; route 2a10:fa80:aaaa::/40 blackhole; } protocol bgp peer_he6 { local as 213123; neighbor 2001:470:1f0a::1 as 6939; ipv6 { import filter { reject; }; export filter { if net = 2a10:fa80:aaaa::/40 then accept; reject; }; }; }
! FRRouting IPv6 BGP router bgp 213123 bgp router-id 213.214.215.216 no bgp default ipv4-unicast neighbor 2001:470:1f0a::1 remote-as 6939 ! address-family ipv6 unicast network 2a10:fa80:aaaa::/40 neighbor 2001:470:1f0a::1 activate neighbor 2001:470:1f0a::1 prefix-list PL-OUT out neighbor 2001:470:1f0a::1 prefix-list PL-IN in exit-address-family ! ipv6 prefix-list PL-OUT seq 5 permit 2a10:fa80:aaaa::/40 ipv6 prefix-list PL-IN seq 5 deny any
# MikroTik RouterOS 7.x /routing bgp template add name=peer-he6 as=213123 router-id=213.214.215.216 \ output.filter-chain=bgp-out input.filter-chain=bgp-in /routing bgp connection add name=he6 template=peer-he6 remote.as=6939 \ remote.address=2001:470:1f0a::1 /routing filter rule add chain=bgp-out rule="if (dst in 2a10:fa80:aaaa::/40) { accept }" add chain=bgp-out rule="reject" add chain=bgp-in rule="reject"
! Cisco IOS / IOS-XE router bgp 213123 bgp router-id 213.214.215.216 no bgp default ipv4-unicast neighbor 2001:470:1f0a::1 remote-as 6939 address-family ipv6 network 2a10:fa80:aaaa::/40 neighbor 2001:470:1f0a::1 activate neighbor 2001:470:1f0a::1 prefix-list PL-OUT out neighbor 2001:470:1f0a::1 prefix-list PL-IN in exit-address-family ! ipv6 prefix-list PL-OUT seq 5 permit 2a10:fa80:aaaa::/40 ipv6 prefix-list PL-IN seq 5 deny any
% Information related to '2a10:fa80:aaaa::/40' inet6num: 2a10:fa80:aaaa::/40 netname: EXAMPLE-NET descr: Example Ltd. IPv6 allocation country: RO org: ORG-EXML1-RIPE admin-c: JD1234-RIPE tech-c: JD1234-RIPE status: ALLOCATED-BY-LIR mnt-by: ro-dreamserver-1-mnt mnt-by: MNT-EXAMPLE created: 2026-04-08T10:41:22Z last-modified: 2026-04-08T10:41:22Z source: RIPE route6: 2a10:fa80:aaaa::/40 origin: AS213123 mnt-by: MNT-EXAMPLE source: RIPE
| Date | Action | Object | Result | Details |
|---|---|---|---|---|
| 2026-04-14 09:21 | create_roa | roa 2a10:fa80:aaaa::/40 | ✓ OK | AS65001 /40 |
| 2026-04-12 15:10 | create_roa | roa 2a10:fa80:aaaa:1000::/44 | ✓ OK | AS213123 /48 |
| 2026-04-12 15:08 | create_route6 | route6 2a10:fa80:aaaa:1000::/44 | ✓ OK | origin AS213123 |
| 2026-04-09 09:17 | create_roa | roa 185.72.40.0/24 | ✓ OK | AS213123 /24 |
| 2026-04-09 09:15 | create_route | route 185.72.40.0/24 | ✓ OK | origin AS213123 |
| 2026-04-09 11:02 | update_rdns | rdns a.a.a.a.0.4.b.6.b.0.a.2.ip6.arpa | ✓ OK | ns1, ns2.example.com |
| 2026-04-08 10:44 | create_roa | roa 2a10:fa80:aaaa::/40 | ✓ OK | AS213123 /48 |
| 2026-04-08 10:42 | create_route6 | route6 2a10:fa80:aaaa::/40 | ✓ OK | origin AS213123 |
| 2026-04-08 10:41 | provision | inet6num 2a10:fa80:aaaa::/40 | ✓ OK | ALLOCATED-BY-LIR, mnt-by MNT-EXAMPLE |
Leaving your current LIR does not have to hurt
Send us the resource list and we draft the migration plan the same day.
