RIPE Database Search

By pressing the "Search" button you explicitly express your agreement with the RIPE Database Terms and Conditions.

Service Announcements
  • All of our services are operating normally.

Application Complete? What now?

Click on each box to get more help.

I am a new LIR

Get an LIR Portal account
Required

Create the first person and mntner objects
Required

Request your first IPv6 allocation
Required

Request your IPv4 allocation
Required if you want IPv4 resources

Request an AS Number if you need one
Optional

Set up reverse delegation for your allocation
Optional but advisable

Create a route object for your allocation
Optional

The LIR Portal provides increased access to the RIPE NCC for members via a web interface. In addition to managing registry data and making queries and updates without contacting the RIPE NCC staff, the LIR Portal also allows you to request resources from the RIPE NCC.

The LIR Portal is the LIR’s main communication interface with the RIPE NCC.

Before you can make full use of the LIR Portal, you will need to carry out two steps:

  • create and activate a RIPE NCC Access account
  • make sure your RIPE NCC Access account has the relevant level of access for your LIR

During the membership application process, we assign admin privileges for the LIR Portal to a RIPE NCC Access account nominated by the applicant LIR. Account holders with admin privileges can manage access to the LIR Portal for other RIPE NCC Access account holders and decide which level of access they are given (e.g., billing, resources, general, certification, ticketing and admin privileges).

Log in to the LIR Portal.

If you need any assistance with the LIR Portal, please contact us.

What is a PERSON object?
A person object contains information about technical or administrative contact persons that are responsible for the object where it is referenced. Each object has a unique NIC handle ("nic-hdl:").

What is a NIC handle?
NIC handles are unique identifiers of persons.

It is basically the person's unique ID and it helps to keep different people with the same name apart from each other.

Whenever a person object is referenced in another object they are referenced by their NIC handle ("nic-hdl:") and not by their name.
See example person object

What is a MNTNER (pronounced "maintainer"):

Objects in the RIPE Database may be protected using mntner objects. A mntner object specifies authentication information required to authorise creation, deletion or modification of the objects protected by the mntner.

It is now mandatory to include a “mnt-by:” attribute in every database object. The value of the "mnt-by" attribute is the name of the maintainer (mntner) object that will protect the object.

To create a PERSON object and a maintainer at the same time, you can use the start-up application.

For more information about maintainers and hierarchical authorisation please see:
http://www.ripe.net/data-tools/support/security

We have an E-Learning online tutorial for creating person and mntner objects, and how to protect objects with your mntner here:
http://www.ripe.net/lir-services/training/e-learning/ripe-database

Allocation: Address space set apart by the RIPE NCC for an LIR’s future use: for their End Users and their own infrastructure.
RIPE NCC >>> LIR

Assignment: Address space taken by an LIR from their allocation and given to an End User or to the LIR’s own infrastructure (to itself).
LIR >>> End User or LIR >>> to itself

LIR’s Allocation: /22
Each LIR can receive only one /22 IPv4 allocation.

Steps to receive the first allocation:

  • Complete the "IPv4 First Allocation Request Form".
  • The RIPE NCC issues ticket numbers.
  • The RIPE NCC IPRA (IP Resource Analyst) will evaluate and approve the first allocation request.

The IPRA enter the allocation inetnum object into the RIPE Database for the LIR. Afterwards, the LIR can assign address space from this allocation to active networks and enter the resulting assignments in the RIPE database.

The whole allocation can be announced immediately. The LIR can create a route object for the whole allocation (see optional steps for more information).

Allocation: Address space set apart by the RIPE NCC for an LIR’s future use: for their End Users and their own infrastructure.
RIPE NCC >>> LIR

Assignment: Address space taken by an LIR from their allocation and given to an End User or to the LIR’s own infrastructure (to itself).
LIR >>> End User or LIR >>> to itself

LIR's IPv4 Allocation: /19
[sketch]
The LIR will receive the first allocation and the first assignment at the same time. Each LIR can receive only one /22 IPv4 allocation.

Steps to receive the first allocation and first assignments:

  • Complete the “PROVIDER AGGREGATABLE (PA) ASSIGNMENT REQUEST FORM” for the first assignment in the LIR Portal.
  • The RIPE NCC issues ticket numbers.
  • Complete the “IPv4 FIRST ALLOCATION REQUEST FORM” in the LIR Portal.
  • The RIPE NCC IPRA (IP Resource Analyst) will evaluate and approve the first allocation and the assignment requests.

The RIPE NCC IPRA enter the allocation inetnum object into the RIPE Database for the LIR.
The whole allocation can be announced immediately. The LIR can create a route object for the whole allocation (see optional steps for more information).

Complete the "AS Number Request Form".

Please find the instructions for requesting reverse delegation for your allocation at the following url:
http://www.ripe.net/reverse/

The route object represents a route in the Internet.

A route is represented as a prefix, which is the network part of the address that points to the network in question, and the originating AS Number. Both prefix and the originating AS Number are the primary key for the route object (this means if you change the prefix or the originating AS Number, a completely new route object will be created).

It is the responsibility of the LIR to create route objects for the address space originating from their AS.
Please note there are multiple authorisation checks required when creating a route object.

More information can be found at:
http://www.ripe.net/data-tools/db/faq/faq-route-object

The minimum initial allocation size is a /32. Organisations may qualify for an initial allocation greater than a /32 by submitting documentation that reasonably justifies the request.

Steps to receive the first IPv6 allocation:

  • Complete the "IPv6 First Allocation Request Form"
  • The RIPE NCC issues ticket numbers
  • The RIPE NCC IP Resource Analyst (IPRA) will evaluate and approve the first IPv6 allocation