Skip to content
Article LIR • •

Managing Your RIPE LIR Account

What an LIR administrator handles after joining: Portal users and roles, maintainer authentication since March 2026, one invoice per LIR account, sponsored End Users and the Assisted Registry Check.

Managing a RIPE LIR account comes down to four recurring jobs: keeping the users and contacts on your LIR Portal account current, keeping the objects your maintainers hold in the RIPE Database accurate, paying the invoice for each LIR account within 30 days, and looking after the End Users you sponsor. In 2026 each LIR account costs €1,800 a year, plus €50 per ASN and €75 per independent assignment registered to it, under the RIPE NCC Charging Scheme 2026 (ripe-848).

The RIPE NCC reviews your registry through the Assisted Registry Check. If you are still deciding whether to join, start with how to become a RIPE LIR.

Understanding Your LIR Account

Key Components

1. Registry ID and organisation object

  • The registry ID (regid), in the form nl.example, identifies the LIR account in the LIR Portal and on invoices
  • The member organisation object (ORG-XXXX-RIPE, org-type: LIR) is created by the RIPE NCC and referenced by org: on your allocations; it is partly managed by the RIPE NCC, so some attributes can only be changed through the LIR Portal
  • Since 4 March 2026 the RIPE NCC adds a reg-nr: attribute with the verified company registration number to the organisation objects it co-maintains (RIPE Database release 1.121)
  • Accounts and their resources can move to another member through a merger, acquisition or transfer under ripe-831

2. Member Services

  • Access to RIPE NCC services and support
  • Right to request IP resources and ASNs
  • Participation in RIPE community activities
  • Training and educational resources

3. Associated Resources

  • IP address allocations and assignments
  • Autonomous System Numbers (ASNs)
  • Reverse DNS delegations
  • Sponsored PI resources

4. Billing and Financial Account

  • Annual membership fees
  • Per-resource charges
  • Payment methods and invoicing
  • Financial history

The LIR Portal: Your Primary Interface

The LIR Portal (https://my.ripe.net/) is your main communication and management interface with RIPE NCC.

Accessing the LIR Portal

Initial Setup: During the membership application process, you nominate one RIPE NCC Access account to receive administrator privileges for the LIR Portal. This person becomes your initial Portal administrator.

Authentication:

  • RIPE NCC Access accounts (single sign-on across the LIR Portal, the RIPE Database and the RPKI Dashboard)
  • Two-factor authentication is mandatory on every RIPE NCC Access account (required since 2024); the Users section of the LIR Portal shows whether each user has it enabled
  • Administrators create, view and revoke API keys from the LIR Portal

User roles:

  • Administrator: full access, including user and API-key management
  • Regular user: account details, tickets, General Meeting registration and training
  • Billing user: billing and payment information only
  • Several administrators can be assigned; keep the user list current and remove leavers the same day

LIR Portal Dashboard

When you log in, the dashboard provides an overview of:

  • Current resource allocations and assignments
  • Pending requests and tickets
  • Account status and compliance notifications
  • Recent activity and changes
  • Upcoming renewals and deadlines
  • Training opportunities and announcements

Key Portal Functions

1. Resource Requests

Requesting IPv4 Addresses: Under the IPv4 policy (ripe-826), an LIR that has never received IPv4 from the RIPE NCC can request exactly one /24, served from the IPv4 waiting list. On 25 September 2026 the list held 791 LIRs, and the LIR at its head had waited 485 days. Anything more comes from the transfer market.

Process:

  1. Navigate to "Request Resources" section
  2. Select "IPv4 Allocation"
  3. Submit request
  4. The RIPE NCC processes the request in around one working day and places it on the first-come, first-served waiting list (no guaranteed waiting time)
  5. Receive allocation confirmation once a /24 is available

Requesting IPv6 Addresses: LIRs can request IPv6 allocations based on their addressing plans and justified needs.

Process:

  1. Prepare addressing plan showing:
    • Current infrastructure
    • Projected growth
    • Assignment plans for the next 2 years
  2. Submit request through Portal
  3. Provide technical justification
  4. Receive a /32 up to a /29 without further justification (ripe-738 5.1.2)

Requesting Additional IPv6 Space: An allocation smaller than /29 can be extended up to /29 without further documentation (ripe-738 5.7). Beyond that, a subsequent allocation needs an HD-Ratio of 0.94, measured in /56 assignments (5.2.1), or a new justification under 5.1.2:

  • Demonstrate usage of current allocation
  • Provide updated addressing plan
  • Show specific need for expansion
  • A subsequent allocation doubles your space (5.2.3)

Requesting ASNs: LIRs can request Autonomous System Numbers for BGP routing.

Requirements:

  • Demonstrate need for unique routing policy
  • Show that the network will be multihomed (ripe-679); the LIR Portal form asks for at least two peering partners
  • Provide routing policy documentation
  • Pay the per-ASN fee: €50 per year under ripe-848; from 2027 the first ASN registered to an LIR account is included in the annual fee and each additional ASN costs €50 (ripe-867, adopted at the May 2026 General Meeting)

Process:

  1. Submit ASN request through Portal
  2. Provide BGP peering details
  3. Document routing policy
  4. RIPE NCC evaluates technical justification
  5. Receive ASN assignment

2. Contact Management

Types of Contacts:

Admin Contact:

  • Primary administrative contact for the LIR
  • Receives important notifications
  • Responsible for account management
  • Can have multiple admin contacts

Tech Contact:

  • Technical personnel for resource management
  • Handles database and routing issues
  • Receives technical notifications

Billing Contact:

  • Financial and invoicing communications
  • Payment processing
  • Fee notifications and reminders

Abuse Contact:

  • Mandatory on every aut-num and every directly allocated inetnum and inet6num (ripe-705), through an abuse-c: that points to a role object with one abuse-mailbox:
  • Receives abuse reports and complaints
  • Must be reachable and responsive
  • The RIPE NCC validates the abuse-mailbox: at least once a year

Managing Contacts:

  1. Navigate to "Contacts" section in Portal
  2. Add, edit, or remove contact persons
  3. Assign appropriate roles to each contact
  4. Keep all contact information current
  5. Update immediately when personnel changes occur

Keep at least two people on each contact role, so holidays or staff turnover never leave it empty.

3. Account Information Management

Organization Details:

  • Legal name and registration information
  • Physical address
  • Correspondence preferences
  • Language settings

Updating Organization Information:

  • Requires supporting documentation for legal name changes
  • Address changes must reflect actual location
  • Changes may trigger verification process
  • Keep information current to maintain compliance

Membership Status:

  • View current membership status
  • Check payment status
  • Review compliance standing
  • Access membership history

4. Billing and Payments

Invoicing:

  • One invoice per LIR account held on 1 January, sent in January for the resources registered on 31 December
  • The invoice carries the LIR account fee and the per-resource fees
  • Invoice history and archives
  • Download invoices in PDF format

Payment Methods:

  • Bank transfer, quoting the invoice number as reference
  • Credit or debit card, PayPal or Wero through the payment link printed on each invoice (processed by Adyen)
  • No direct debit and no cheques

Payment Terms:

  • Payment is due 30 days from the invoice date
  • After 60 days unpaid the RIPE NCC processes no new requests and suspends services
  • After 120 days it terminates the Standard Service Agreement and closes every LIR account you hold; reactivation costs €1,000 plus all outstanding invoices (ripe-858)
  • Closing an account during the year does not reduce the fee: a closure request filed before 31 December is what avoids next year's invoice

Managing Billing:

  1. Set up payment method preferences
  2. Check that the billing contact receives the invoices
  3. Keep payment information current
  4. Review charges for accuracy

5. Training and Certification

Available Training:

  • Training courses and webinars, included in the membership fee
  • IPv6 deployment workshops
  • RIPE Database training
  • Security and routing courses
  • Online tutorials

Booking Training:

  1. Browse courses on the RIPE NCC Academy (academy.ripe.net) or in the LIR Portal's Training section
  2. Register for in-person or online sessions
  3. Receive confirmation and materials
  4. Complete courses and assessments
  5. Obtain certificates

RIPE NCC Certified Professionals:

  • Professional certification program
  • Members receive three exam vouchers each year, claimed from the Academy dashboard
  • Demonstrates expertise to customers

6. Tickets and Support

Creating Support Tickets:

  • Technical questions about resources
  • Account management issues
  • Policy interpretation
  • Database problems
  • General membership inquiries

Ticket Management:

  1. Submit ticket through Portal
  2. Provide detailed description
  3. Attach relevant documentation
  4. Track ticket status
  5. Receive responses via email and Portal
  6. Close ticket when resolved

The RIPE NCC publishes processing figures for only a few requests: around one working day to process an IPv4 request before it joins the waiting list, and one or two business days for most transfers.

Managing the RIPE Database

The RIPE Database is the public registry of Internet number resources in the RIPE NCC service region. As an LIR, you're responsible for maintaining accurate information about your resources.

Understanding Database Objects

Key Object Types:

inetnum (IPv4) / inet6num (IPv6):

  • Represents IP address ranges
  • Contains allocation or assignment information
  • Includes status, usage details, and contacts

aut-num:

  • Represents ASN assignments
  • Contains routing policy information
  • Includes peering details

organisation:

  • Your LIR organization record
  • Legal and contact information
  • Links to all your resources

person / role:

  • Contact information for individuals or roles
  • Used for admin, tech, and abuse contacts
  • Must be kept current
  • Role objects are the only type that can be referenced by abuse-c:

mntner (Maintainer):

  • Authentication object for database modifications
  • Controls who can update your objects
  • Anyone listed in its auth: can change the objects it protects

Database Maintenance Tasks

Creating New Objects

When creating assignments to customers:

  1. Prepare assignment information:
    • Customer organization details
    • IP address range being assigned
    • Purpose and justification
    • Contact information

  2. Create organization object (if new customer):

    organisation: AUTO-1
org-name: Customer Organization Name
org-type: OTHER
address: Customer Address
e-mail: noc@customer.example
admin-c: ABC1-RIPE
tech-c: ABC1-RIPE
mnt-ref: YOUR-LIR-MNT
mnt-by: YOUR-LIR-MNT
source: RIPE

    A new organisation is created with AUTO-1; the database assigns the ORG- handle. e-mail: is mandatory.

  3. Create inetnum or inet6num object:

    inetnum: 192.0.2.0 - 192.0.2.255
netname: CUSTOMER-NETWORK
descr: Customer Network Description
country: NL
admin-c: ABC1-RIPE
tech-c: ABC1-RIPE
status: ASSIGNED PA
mnt-by: YOUR-LIR-MNT
org: ORG-ABC1-RIPE
source: RIPE

    Since 30 April 2026 (release 1.122) an ASSIGNED PA object no longer accepts mnt-lower:, and descr: and remarks: may contain UTF-8.

  4. Submit through webupdates, the REST API, or a PGP-signed e-mail

Updating Existing Objects

Common updates:

  • Contact information changes
  • Organization details
  • Network descriptions
  • Abuse contact updates

Update process:

  1. Query existing object to get current version
  2. Make necessary modifications
  3. Authenticate with your RIPE NCC Access account, an API key or an OAuth token, or sign the update with PGP or X.509
  4. Submit update via webupdates, email, or API
  5. Verify update was successful

Authentication methods:

  • RIPE NCC Access single sign-on, for webupdates and the LIR Portal
  • API keys, for scripts (available since 30 January 2025)
  • OAuth 2.0 or OIDC tokens, for applications (OAuth since April 2025, OIDC since August 2026)
  • PGP or X.509 signatures, the only option for updates sent by e-mail

Password (MD5) authentication on mntner and irt objects was removed on 4 March 2026 (RIPE Database release notes, release 1.121). Move every maintainer to SSO, API keys or PGP before you need an urgent update.

Deleting Objects

When to delete:

  • Returning IP space to your pool
  • Customer termination
  • Organizational changes
  • Resource transfers

Process:

  1. Confirm the resource is no longer in use
  2. Remove any dependent objects first
  3. Submit deletion with proper authentication
  4. Verify deletion completed
  5. Update internal records

Database Best Practices

1. Accuracy:

  • Keep all information current
  • Update within reasonable time of changes (days, not months)
  • Inaccurate data can lead to compliance issues

2. Abuse Contact Maintenance:

  • Keep the abuse mailbox monitored
  • Respond to abuse reports promptly
  • The RIPE NCC validates the mailbox at least once a year
  • An abuse mailbox that fails validation is followed up under RIPE NCC procedures

3. Security:

  • Remove any leftover auth: MD5-PW lines from your maintainers; they no longer authenticate anything
  • Put each person's own RIPE NCC Access account on the mntner instead of a shared secret
  • Anyone listed in auth: on a maintainer can change every object it protects, so review the list when staff leave

4. Documentation:

  • Document your database management procedures
  • Train multiple staff on database updates
  • Keep internal records matching RIPE Database
  • Maintain history of changes

5. Automation:

  • Use the RIPE Database REST API with an API key for bulk operations
  • Implement IP address management (IPAM) tools
  • Automate routine updates where possible
  • Check that automated updates stay accurate

Resource Management Workflows

Assigning IP Addresses to Customers

Step 1: Verify Available Space

  • Check your allocation for available addresses
  • Confirm there is enough space for the request
  • Plan how the remaining space will be used

Step 2: Document Justification

  • Record customer's need for IP addresses
  • Keep justification documentation
  • May be requested during an Assisted Registry Check

Step 3: Create Assignment

  • Create database objects
  • Set appropriate status (ASSIGNED PA)
  • Include all required fields
  • Link to customer organization

Step 4: Update Internal Records

  • Record assignment in your IPAM system
  • Update capacity planning
  • Track utilization rates

Step 5: Configure Routing

  • Implement routing for the assigned space
  • Update reverse DNS if applicable
  • Verify connectivity

Processing PI Resource Sponsorship Requests

As an LIR, you can sponsor independent resources for End Users that are not members: ASNs and IPv6 PI assignments. The RIPE NCC no longer assigns PI space from its IPv4 pool (ripe-826), though existing IPv4 PI blocks can still be sponsored.

Each End User needs a contract with you that carries the clauses of ripe-637. The RIPE NCC publishes your LIR as sponsoring-org: on every object you sponsor (ripe-603).

Step 1: Receive PI Request

  • Customer provides their requirements
  • Explain PI resource implications
  • Gather necessary documentation

Step 2: Prepare Application

  • Complete PI request form in LIR Portal
  • Provide customer's justification
  • Include supporting documentation
  • Submit to RIPE NCC

Step 3: RIPE NCC Evaluation

  • May request additional information
  • Approval or rejection notification

Step 4: PI Resource Assignment

  • RIPE NCC makes assignment
  • Create database objects
  • Set up billing for the independent resource fee (€75 per assignment per year, billed to you on the 31 December snapshot)

Step 5: Ongoing Sponsorship

  • Maintain sponsorship relationship
  • Handle database updates for customer
  • Process annual fees
  • Coordinate with RIPE NCC as needed
  • Ending a sponsorship is a self-service form in the LIR Portal that takes effect immediately (since November 2025). File it before 31 December, because the RIPE NCC bills per-resource fees on the 31 December snapshot. Ending before 31 December and re-signing the same resource after 1 January keeps the fee due.
  • If you close the LIR account, each End User you sponsor gets 10 working days, then a reminder with 10 more, to sign with a new sponsoring LIR before deregistration starts (ripe-815). Point them to a page that explains how to keep an ASN when the LIR closes.

Handling ASN Requests

Step 1: Verify BGP Requirement

  • Confirm customer needs ASN
  • Verify the customer will be multihomed and has a routing policy to publish
  • Check the customer's technical capability

Step 2: Submit Request

  • Complete ASN request form
  • Provide routing policy details
  • Document BGP peering arrangements
  • Submit through LIR Portal

Step 3: Create aut-num Object After approval:

  • Create aut-num object in database
  • Document routing policy
  • Set up BGP configurations
  • Create the route objects for every prefix the ASN will originate
  • Create the RPKI ROAs in the RPKI Dashboard, then confirm them with the RPKI checker

Step 4: Annual Fee Management

  • Track the per-ASN fee (€50 per year in 2026, see the 2027 rule above)
  • Include in customer billing if applicable
  • Maintain active ASN status

Assisted Registry Check and Compliance

What the ARC Covers

The RIPE NCC's review of an LIR is the Assisted Registry Check (ARC). It covers three areas: the accuracy of your registry data (legal name, address, contacts, role objects, documented usage of your allocations, and the resources you sponsor), consistency between your route objects and what you announce in BGP, and lame reverse DNS delegations.

On request the RIPE NCC also tests the reachability of your network over IPv4 and IPv6 with RIPE Atlas. The obligations behind these checks are listed in LIR compliance requirements.

Responding to an ARC Review

Step 1: Receive the ARC Request

  • RIPE NCC sends the request via email and Portal
  • Includes specific information requested

Step 2: Gather Required Information

  • Collect documentation for all requested items
  • Review database accuracy
  • Prepare explanations for any discrepancies
  • Compile evidence of resource usage

Step 3: Submit Response

  • Respond through LIR Portal or email
  • Provide all requested documentation
  • Explain any issues clearly
  • Submit before deadline

Step 4: Address Findings

  • Review the RIPE NCC's findings
  • Correct any identified issues
  • Update database if needed
  • Implement preventive measures

Step 5: Follow-Up

  • Complete any required corrective actions
  • Confirm resolution with RIPE NCC
  • Update internal processes to prevent recurrence

Maintaining Compliance

Between reviews, keep the records the ARC will look at: contacts that answer, role objects with a monitored abuse-mailbox:, assignments registered for every network in use, and route objects that match your announcements. Answer abuse reports promptly and keep a record of how each was handled. No policy sets a response time, but an unreachable abuse contact fails the yearly validation.

Advanced LIR Management

Managing Multiple LIR Accounts

Some members hold several LIR accounts: 19,977 members held 20,687 LIR accounts in August 2026 (RIPE NCC member update). Each account is invoiced separately and pays the full €1,800 (2026) or €1,894 (2027).

Resource Transfer Management

Transferring Resources: LIRs can participate in IPv4 transfer markets:

As Transferor (Selling):

  1. Identify space available for transfer
  2. Find buyer or use broker
  3. Submit transfer request through Portal
  4. Provide required documentation
  5. RIPE NCC evaluates and approves
  6. Resources transfer to buyer

As Transferee (Buying):

  1. Identify needed resources
  2. Find seller or use broker
  3. Submit transfer request
  4. Prepare the RIPE NCC transfer documents; no needs justification applies inside the RIPE region (transfers coming in from another RIR need a plan to use 50% within five years)
  5. Pass the RIPE NCC due diligence check (ripe-863: registration papers, and identity documents for natural persons)
  6. Receive transferred resources

Transfer Restrictions:

  • IPv4 and 16-bit ASNs cannot be transferred again for 24 months after you received them, including by transfer or merger (ripe-807)
  • 32-bit ASNs and IPv6 carry no such restriction
  • The RIPE NCC charges nothing for a transfer, but the annual fee for every LIR account you hold must be paid first
  • Most transfers complete within one or two business days

Implementing Automation

API Integration:

  • The RIPE Database REST API for queries and updates, authenticated with an API key or an OAuth token
  • RIPEstat for routing and registry data about your prefixes and ASNs
  • API keys are created and revoked by an LIR Portal administrator

Resource requests (IPv4, IPv6, ASNs, PI for End Users) go through the LIR Portal only: the Resource Request API was switched off on 6 January 2025 (RIPE Labs).

Common Automation:

  • IPAM system integration
  • Automated database object creation
  • Reverse DNS management
  • Reporting and analytics

Disaster Recovery and Business Continuity

1. Access Management:

  • Maintain multiple administrators
  • Document access credentials securely
  • Plan for staff turnover or unavailability
  • Test access periodically

2. Contact Information:

  • Keep more than one contact point
  • Use role-based addresses (not individual emails)
  • Maintain current phone numbers
  • Plan for personnel changes

Best Practices Summary

Daily Operations

  • Monitor abuse contact mailbox
  • Check Portal notifications
  • Review new support tickets
  • Address urgent issues promptly

Weekly Tasks

  • Review pending resource requests
  • Update database for any changes
  • Check billing and payment status
  • Coordinate with team on ongoing issues

Monthly Activities

  • Conduct database accuracy review
  • Review resource utilization
  • Update contact information as needed
  • Review training opportunities
  • Analyze resource usage trends

Quarterly Reviews

  • Compliance self-audit
  • Review and update documentation
  • Assess resource needs and planning
  • Team training and knowledge updates

Annual Planning

  • Budget the RIPE NCC fees: in 2026, €1,800 per LIR account plus €50 per ASN; in 2027, €1,894 with the first ASN included and €50 per additional ASN; €75 per sponsored PI assignment in both years
  • Capacity planning for IP resources
  • Staff training and certification plans
  • Policy and procedure updates

Getting Help

RIPE NCC Support Resources

LIR Portal Help:

  • Built-in documentation and guides
  • FAQ sections
  • Video tutorials
  • Getting Started resources

RIPE NCC Support:

  • E-mail: lir-help@ripe.net
  • Tickets through the LIR Portal
  • Live chat on ripe.net and in the LIR Portal, Monday to Thursday 09:00 to 17:00 CET and Friday 09:00 to 16:00 CET, except bank holidays
  • A Technical Emergency Hotline, for a suspected outage or compromise of a RIPE NCC service only

Community Resources:

  • RIPE mailing lists
  • RIPE Labs articles
  • Community documentation
  • Peer support and discussions

Help from Via-Registry

Our LIR consulting covers the membership application, first allocation requests, RIPE Database object work, RPKI and ROA setup, and preparation for the Assisted Registry Check, quoted per case.

If what you need is one ASN or one PI block rather than a membership, ASN registration under our sponsorship costs €130 per year (as of September 2026) and needs no RIPE NCC membership. The RIPE LIR membership costs and benefits page compares the two routes.

What to Keep on the Calendar

Three dates drive the year: 30 days to pay the January invoice, 31 December for stop-sponsorship requests and closure requests, and the yearly abuse-mailbox validation. Keep SSO or API keys on every maintainer, one role object per contact function, and your internal records matching the RIPE Database, and an ARC review has little to find.

Frequently Asked Questions

What replaced maintainer passwords in the RIPE Database?

RIPE NCC Access single sign-on, API keys, OAuth 2.0 or OIDC tokens, and PGP or X.509 signatures for e-mail updates. MD5 password authentication was removed on 4 March 2026, in RIPE Database release 1.121.

Can an LIR still get IPv4 addresses from the RIPE NCC?

Only a first /24. An LIR that has never received IPv4 from the RIPE NCC joins the waiting list, which counted 791 LIRs on 25 September 2026. Any further IPv4 comes from the transfer market.

What happens when an invoice goes unpaid?

Payment is due at 30 days. After 60 days the RIPE NCC processes no new requests. After 120 days it terminates the Standard Service Agreement, and reactivation costs €1,000 plus the outstanding invoices.

How do I stop sponsoring an End User's resource?

Use the stop-sponsorship form in the LIR Portal, which takes effect immediately. File it before 31 December, since the per-resource fee follows the 31 December snapshot.

Sources:

Related Articles

Article

RIPE NCC Charging Scheme 2027: What ripe-867 Changes and Who Pays More

Every 2027 fee line next to its 2026 value, who pays €94 more and who pays €44 more, the category model that lost by 68 votes, and the 31 December 2026 snapshot behind the January invoice.

Guide

How to Become a RIPE LIR: Application Process and Setup

Who can apply, what the RIPE NCC checks before it activates an LIR account, what membership costs in 2026 and 2027, and which resources to request first.

Article

What is a Local Internet Registry?

What an LIR does, who can become one, what RIPE NCC membership costs in 2026 and 2027, and why one ASN or one PI block needs only a sponsoring LIR.

Back to Resources