When you lease IPv4 space, who controls its RIPE records — you, or a support queue? On IP4 Market you manage it yourself. This guide shows how to set up your RIPE details once so every action that follows runs in your own name.
- Why self-service RIPE management matters
- What “your RIPE details” are
- Before you start
- Step by step
- What we keep, what you control
- Next steps
Why self-service RIPE management matters
Most IPv4 leasing providers keep the keys to themselves: every route object, every description change, every abuse contact update means opening a ticket and waiting. That is slow, and it puts your operational reality in someone else’s hands.
Need IPv4 addresses?
Browse clean, RIPE-verified subnets at $0.50/IP/month.
We took the opposite approach. When you lease a range from IP4 Market, we delegate the relevant RIPE maintainers (mnt-routes and mnt-lower) to your maintainer. From that moment you announce, describe and register your space yourself, straight from your dashboard — a level of autonomy very few providers hand over.
The short version: set your RIPE identity once in Company Settings, and creating route objects or publishing your description and abuse contact becomes a two-minute, self-service job.
What “your RIPE details” are
Your RIPE details are the identity we use on your behalf when you register usage:
- Organisation — your RIPE org handle, e.g.
ORG-EXAMPLE-RIPE. It carries your abuse contact. - Admin and tech contacts — your
nic-hdls, e.g.AA1234-RIPE. - Maintainer — your
mntner, the object that authorises what you do in RIPE.
Set them once and they become the defaults for every route object and sub-assignment you create.
Before you start
- You are a RIPE member, or you already have a RIPE organisation object and at least one contact (
nic-hdl). - You have your own maintainer. When you lease a range from us, we delegate routing and sub-allocation rights on it to that maintainer.
Step by step
In your dashboard, open Company Settings.
Scroll to the RIPE settings section.
Fill in your Organisation ID, Default maintainer, and your Admin and Tech contacts.
Click Save Changes. That’s it.
Why the organisation matters for abuse. Your abuse contact is published through your RIPE organisation. Once your Organisation ID is set here, the sub-assignments you create for your leased ranges carry your abuse contact automatically — so reports reach you, not us.
What we keep, what you control
The parent allocation object stays under our maintainer, so it can never be altered or transferred by mistake. Everything about how you use the space — routing and registration — is delegated to you. It is the standard, transparent leasing model, with the controls actually in your hands.
Next steps
With your RIPE details in place, you can:
- Announce your range by creating your RIPE route object.
- Publish your description and abuse contact with a sub-assignment.
Need IPv4 addresses? Lease RIPE-verified /24–/22 subnets from $0.50/IP per month — LOA + RPKI/ROA in minutes, instant company verification, and full self-service RIPE management from your dashboard. See available subnets →
