Anchored Registry · RIPE NCC member
A sponsoring LIR
for your IPv4, IPv6
and AS numbers.
Provider-independent resources have to sit under a sponsoring LIR if you are not a RIPE member yourself. I am one — a real member with my own autonomous system, not a reseller page.
Moving your resources to me changes nothing about your routing and takes an agreement plus one form. Tell me what you hold and you get a price back, not a meeting invitation.
A person answers, within
two working days
Who is writing — check it yourself
organisation: ORG-TO334-RIPEorg-name: Tropynin Olegorg-type: LIRcountry: KZaut-num: AS41800as-name: TROPYNIN-ASsource: RIPE
The membership is real and so is the network behind it — anchoredip.com and status.anchoredip.com run on AS41800, with a paying customer on it.
Open directory
Who sponsors whom in the RIPE region
16,937 AS numbers held by an End User and sponsored by an LIR, and the 2,475 organisations doing the sponsoring. Counted from the registry’s published data, free, and no account.
Whether this is for you
Four situations. If one of them is yours, we should talk.
01
You hold independent resources and are not a RIPE member
Provider-independent IPv4 or IPv6, or your own AS number. Those have to sit under a sponsoring LIR, and full membership at €1,800 a year is not worth it for a handful of objects.
02
Your sponsor stopped being a service
The price moved at renewal, the answers stopped coming, or the company changed hands. A change of sponsoring LIR is a documented procedure, not a renegotiation with them.
03
You acquired address space and need somebody to hold it
A transfer needs a sponsoring LIR on the receiving side before the registry will record the resource in your name.
04
You are consolidating
Resources spread across two or three sponsors, each with its own invoice, contact and renewal date — under one agreement instead.
Not on the list: obtaining resources for you. Waiting-list requests and transfers are separate one-off work, and I would rather say that here than bundle it into a price.
Why not the cheapest signature on the market
A sponsor is only worth anything the day you need one.
Sponsorship is a signature until something happens — a renewal, an audit, a transfer, a sponsor that stops answering. That is the whole of what separates one from another, so it is what I put in the agreement.
A named person answers
Not a ticket queue and not a shared mailbox. One working day, from me, and my name is on the registry record above.
Sixty days' notice if I ever stop
Written into the agreement, not a policy page. Long enough to find another sponsoring LIR without your resources being at risk — which is the failure mode of a cheap sponsor that quietly closes.
Leaving is thirty days' notice before renewal
No exit fee, no minimum term beyond the year you paid for, and no cooperation needed from me to move elsewhere.
I never hold a credential of yours
No maintainer password, no portal login. A service that holds your credential is a service you cannot fire without asking it nicely.
The questions everybody asks, and the last one nobody does
Putting your address space in a stranger’s name
- What changes for my network?
- Nothing. Sponsorship is a contractual and registry relationship, not a routing one. Your announcements, your transit, your peers and your own maintainer are untouched. No BGP session is involved at any point.
- How much work is the move?
- An agreement to sign, and a form submitted on your behalf. The registry keeps the same objects and the same resource; what changes is which member is recorded as sponsoring them.
- Do you need access to anything of mine?
- No password, and no maintainer of mine on your objects. I do not accept a customer credential — a service that holds your credential is a service you cannot fire.
- What if you disappear?
- The resources are yours, and the agreement gives you sixty days' written notice if I ever cease sponsoring — a real window to move to another LIR rather than a clause that technically covered it. RIPE's own rules point the same way: the End User keeps the resources and moves.
What the process actually is
Two human moments, and neither is mine to remove.
The agreement, the invoice and the record-keeping are prepared before you see them. These two are the RIPE NCC’s rules, and you can check that they are.
Moment 01 — identity
I have to know who you are
The sponsoring member is responsible for the identity check and can be audited on it: the company register, a document, and the person who may bind the company. Usually one exchange of email.
Moment 02 — the form
A person submits the request
RIPE withdrew the Resource Request API in January 2025, so a change of sponsoring LIR is a portal form. I fill it from a payload assembled and validated in advance. Minutes, not an afternoon.
What it costs
Quoted, per resource, per year
A resource is one AS number, or one allocation or assignment — not one object. A /21 with eight route objects, four contacts and its reverse DNS is one resource. You are not charged more for keeping detailed records.
I quote rather than publish, because the number depends on how many resources you hold and I would rather give you one I can stand behind than post a figure and revise it later.
WHAT THE MARKET CHARGES
Published prices from other sponsoring LIRs run roughly €75–130 a year for an AS number and €105–240 for a PI assignment, some with a setup fee on top. I am in that range, not under it, and I will tell you where a cheaper one would serve you just as well.
Ask for a price
What do you hold, and who sponsors it today?
That is enough for a number. I look your resources up in public data before replying, so the answer comes back with the price and the steps in it rather than a request for a call.
- ✓No account, no card, no obligation
- ✓No credential of yours, at any stage
- ✓One reply from a person — I do not run sequences