Tips for Resource Requests
- LIR Portal
- Classful Assignments
- Admin-c or Tech-c?
- RIPE Database Tools for LIR's
- Training Courses
- In need of another IPv4 allocation?
- Don't send too many requests at once!
- Don't Paste the Network Template to the RIPE Database!
- AS Requests - multihomed
The RIPE NCC introduced the LIR Portal in January 2003. This members-only part of the website has an on-line request interface which will validate and lets you submit requests. An interactive help function is also provided.
The LIR Portal is also the place to view and update registry information and some parts of your IPv4 allocation objects.
Although using the LIR Portal is a very handy way of requesting resources, we still recommend every requester to study thethe tips on this page.
The 'class' concept on the Internet is replaced by classless routing (CIDR). You should not refer to 'class A, B, or C' anymore.
Due to the requirement to increase the utilisation efficiency of IPv4 address space, all assignments are made with the assumption that sites make use of variable length subnetting and classless technologies within their network. Any customers using classfull equipment can only be assigned the amount of addresses that they would normally need if they were using classless addressing.
The admin-c for a network should be someone within that organisation who can be contacted in case of an emergency. They should be able to order the network to be disconnected or machines to be turned off. Although the admin-c does not have to be physically located on the site of the network, they should have a position of authority within the organisation that runs the network.
The tech-c is a person who should be physically located on the site of the network and is technically skilled to operate a network environment.
You can verify your invalid RIPE Database assignments that require your attention using the IP Analyser. In addition to offering an overview of your invalids, this LIR Portal application also displays all allocations and assignments as well as all available free space.
Data in the IP Analyser is available in a user-friendly web interface, but we also provide JSON and plain text output in ASused format through an API. You can read more about this functionality on our developer documentation page.
To help you understand RIPE NCC policies and procedures, the RIPE NCC offers LIR Training Courses throughout our service region. These courses help LIRs with their Internet resource administration. It is highly recommended that you attend an LIR Training Course.
The LIR Training Course is included in the fee for every new LIR. LIR Portal.can be found in the
On 14 September 2012, the RIPE NCC began to allocate IPv4 address space from the last /8. This means that section 5.1 of “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” is now in effect. This section states that, once the RIPE NCC begins to allocate address space from the last /8, a RIPE NCC member may receive only a /22 (1,024 IPv4 addresses), even if they can justify a larger allocation. Allocations will only be made to LIRs if they have already received an IPv6 allocation from an upstream LIR or the RIPE NCC.
Give a summary of all assignments from your current allocation. For all the procedures involved in obtaining a further IPv4 allocation, please refer to the and the IPv4 Address Allocation and Assignment Policies.
The RIPE NCC advises not to send more than four requests at one time. You can make use of the LIR Portal request forms and submit one request per resource.
8. Avoid Pasting the Network Template to the RIPE DataBase
Do not paste the #[ Network Template ]# straight from your request form into the RIPE Database. It will NOT be accepted.
When requesting an AS Number please make sure you include the following information:
- Explain why you (or your customer) need an AS number.
- What address space do you plan to announce (needs to be registered in the RIPE Database)?
- Include the email addresses of your peering partners' contacts. We may decide to verify the information at any time.
We can only assign AS Numbers to multihomed organisations who need to define their own routing policy.
You need to be connected to at least two Autonomous Systems in order to be considered Multihomed.
We understand there is the 'chicken and egg' situation here. But the RIPE NCC requires a routing policy that shows the new AS peering with at least two AS Numbers.
When the peering information is known to you, you may fill out the technical template :
Part B - TECHNICAL TEMPLATE
You can use the LIR Portal's on-line request form.