Compliance Requirements for RIPE LIRs (2026)

An LIR must keep its RIPE Database records accurate and keep a validated abuse contact on its resources (ripe-705). It must follow the RIPE policies for every resource it holds or sponsors, and pay its invoices within 30 days. In 2026 that means €1,800 per LIR account plus €50 per ASN and €75 per independent assignment under the RIPE NCC Charging Scheme 2026 (ripe-848). An unpaid invoice leads to suspension at day 60 and a termination notice at day 120 (ripe-858).

This page is written for the member itself. If you hold one ASN or a PI block through a sponsoring LIR, the membership duties below sit with that LIR, not with you; see What is a Local Internet Registry? for the difference.

Legal and Contractual Obligations

The Standard Service Agreement (ripe-812)

A RIPE NCC member signs the Standard Service Agreement (ripe-812), which covers its first LIR account; each additional LIR account adds an LIR Account Agreement signed by an authorised representative. Under the SSA the member follows the RIPE policies and RIPE NCC procedures, keeps its registration data correct, pays the annual contribution and answers the RIPE NCC's registry inquiries.

Either side can end the agreement. A member gives three months' written notice (ripe-858). To avoid paying the next year's contribution, file the closure request before 31 December: a request filed later leaves the following year's fee due in full, with no pro rata refund (RIPE NCC Billing Procedure 2026).

Due diligence and sanctions screening (ripe-863)

The RIPE NCC's due diligence procedure (ripe-863) asks legal persons for proof of registration with the national authorities, approved by an authorised representative, and natural persons for an identity document. Every signing party and authorised representative is checked against EU and Dutch sanctions lists before registration, and again when administrative details change. Keep the company documents current: failure to submit valid trade register documentation is a ground for termination with immediate effect (ripe-858).

Obligations when you sponsor End User resources

Each sponsored ASN or PI assignment needs a contract with the End User that contains the clauses of ripe-637: the End User keeps its registration data current, cannot sub-assign the resource, pays the annual fee to the LIR, and loses the resource by default if it becomes unreachable or stops paying. The RIPE NCC bills the LIR €50 per sponsored ASN and €75 per sponsored PI assignment per year (ripe-848), counted on the resources held on 31 December.

Ending a sponsorship is a self-service LIR Portal form since November 2025 and takes effect immediately. File it before 31 December: ending a sponsoring agreement in December and signing a new one for the same resource after 1 January is treated as continuous, and the full fee stays due (Billing Procedure 2026). An End User left without a sponsor gets 10 working days, then 10 more after the RIPE NCC's notice, before deregistration starts (ripe-815).

RIPE Policy Framework

RIPE policies are developed through an open, bottom-up process involving the Internet community. As an LIR, you must comply with all current policies, which cover:

Resource Allocation Policies:

• IPv4 allocation and assignment rules
• IPv6 allocation and assignment policies
• ASN assignment criteria
• Resource transfer regulations
• Recovery of unused resources

Database Policies:

• Registration requirements
• Data accuracy standards
• Abuse contact obligations
• Privacy and data protection

Database Registration Requirements

Mandatory Registration Data

For each resource you hold or assign, you register:

Organization Information:

• Legal organization name (exactly as registered)
• Organization type (LIR, OTHER, etc.)
• Registered business address
• Country of legal registration
• The reg-nr: attribute, added on 4 March 2026, carries the registration number the RIPE NCC verified; it sits on organisation objects the RIPE NCC co-maintains and the LIR does not type it

Contact Information:

• Administrative contact (admin-c)
• Technical contact (tech-c)
• Abuse contact (abuse-c), mandatory and validated by the RIPE NCC at least once a year (ripe-705)
• All contacts must be reachable and responsive

Resource Details:

• IP address ranges (inetnum/inet6num objects)
• Network names and descriptions
• Status values (ALLOCATED PA, ASSIGNED PA, ALLOCATED-ASSIGNED PA, AGGREGATED-BY-LIR)
• Country where resources are used
• Organization links

Routing Information:

• ASN details (aut-num objects)
• Routing policy information
• BGP configuration data
• Peering relationships

Data Accuracy Standards

Timeliness: update the database when details change. The Assisted Registry Check compares legal name, address and contacts with the LIR account (see the audit section).

Completeness:

• All mandatory fields must be populated
• Optional but relevant fields should be included
• Descriptive information should be meaningful
• Contact details must be complete and functional

Accuracy:

• Information must reflect current reality
• No placeholder or dummy data
• Addresses must be genuine locations
• Contact emails must be monitored

Consistency:

• Information across related objects must align
• Internal records should match database entries
• Updates should maintain referential integrity

Prohibited Database Practices

Violations that trigger enforcement:

Inaccurate Information:

• Fake organization names or addresses
• Non-existent contact information
• Misleading descriptions
• Incorrect country codes

Unresponsive Contacts:

• Abuse contacts that don't respond
• Bouncing email addresses
• Contacts that refuse to cooperate

RIPE Database access and authentication

Password (MD5) authentication for maintainers ended on 4 March 2026; updates now use RIPE NCC Access single sign-on, API keys, OAuth 2.0 or OIDC, or PGP and X.509 keys. Two-factor authentication on RIPE NCC Access has been mandatory since 2024. The contact-method rules for person and role objects changed on 30 April 2026 (NWI-20). Account-level detail is in Managing Your RIPE LIR Account.

Abuse Contact Requirements

What is an Abuse Contact?

The abuse contact is a designated role or person who:

• Receives and handles abuse reports
• Responds to security incidents
• Addresses spam, hacking, or malicious activity
• Coordinates with law enforcement if needed
• Takes action to resolve abuse issues

What ripe-705 requires

ripe-705 makes abuse-c: mandatory on every aut-num object and on at least every directly allocated inetnum and inet6num; more-specific objects either carry their own or are covered by the object above them. The RIPE NCC validates each abuse-mailbox: at least once a year. The policy sets no rule on how reports are handled and no response time: how fast you answer is your own operational choice.

The follow-up procedure the RIPE NCC described in February 2019 still applies as published: an automated check first tests whether the address accepts mail. An address that fails gets an email with a validation link, two reminders at one-week intervals, then a ticket handled by staff. For an LIR's own organisation object, an LIR that refuses or stays unresponsive enters the closure procedure and has three more months to update the contact before membership is terminated (RIPE Labs, 14 February 2019). For sponsored End User objects the RIPE NCC adds a database remark pointing at the responsible LIR instead.

Best Practices for Abuse Handling

1. Dedicated Abuse Team or Role:

• Assign specific personnel to abuse handling
• Provide training on abuse response
• Establish escalation procedures
• Document processes

2. Rapid Response:

• Set your own target (many operators use 24 hours); ripe-705 imposes none
• Acknowledge receipt immediately
• Investigate claims thoroughly
• Take appropriate action
• Follow up with reporter

3. Documentation:

• Log all abuse reports received
• Record actions taken
• Maintain evidence of investigations
• Track trends and patterns

4. Automation Where Appropriate:

• Auto-acknowledgment of receipt (but follow up manually)
• Ticketing systems for tracking
• Integration with monitoring tools
• Reporting and analytics

Resource Usage and Justification

LIRs must use allocated resources according to RIPE policies and provide justification for requests.

Proper Resource Usage

IPv4 Allocations:

• The RIPE NCC allocates exactly one /24 per LIR, ever, from a waiting list (ripe-826); 791 LIRs were queued on 25 September 2026 and the first had waited 485 days. More IPv4 comes only by transfer.
• The allocation must be used to make assignments to your own or your customers' networks, with an active element in the RIPE NCC service region.
• IPv4 cannot be transferred for 24 months after you receive it, by allocation, transfer or merger (ripe-807 2.2.1); IPv6 and 32-bit ASNs carry no such restriction.

IPv6 Allocations:

• An LIR receives a /32 up to a /29 without further documentation, and can extend an existing allocation to a /29 the same way (ripe-738 5.1.2 and 5.7).
• Beyond that, a subsequent allocation needs the HD-Ratio of 0.94 on your assignments or a justified new need (5.2.1 and 5.2.2).
• Register every assignment in the RIPE Database, individually or with an AGGREGATED-BY-LIR object whose assignment-size: gives the size of the individual assignments (5.5).

ASN Assignments:

• The network must be multihomed and its routing policy provided, in RPSL (ripe-679); the LIR Portal request form asks for at least two peering partners.
• The RIPE NCC contacts holders of unannounced ASNs; a number not put into use within three months is returned.
• Proposal 2026-01, which would drop the needs check for a holder's first ASN, was in drafting in September 2026 and is not policy.

Assignment Documentation

When assigning resources to customers or infrastructure, document:

Customer Assignments:

• Organization details
• Justification for address space size
• Intended usage
• Assignment date
• Contract or service agreement references

Infrastructure Assignments:

• Network purpose and design
• Equipment and service details
• Growth projections
• Technical architecture

How does the RIPE NCC audit an LIR?

The Assisted Registry Check (ARC)

The RIPE NCC's audit of an LIR is the Assisted Registry Check, which the RIPE NCC describes as an enhancement of "the traditional auditing process that all LIRs are required to take part in". An ARC compares the registry data with the LIR account (legal name, address, contacts), the routing registry with the BGP announcements seen for your resources, and the reverse DNS delegations; it also looks at RPKI and tests reachability through RIPE Atlas. Sponsored PI and ASN assignments are reviewed with the rest. The RIPE NCC publishes no fixed cycle or response deadline for an ARC; an LIR can also ask for one at reg-review@ripe.net.

What RIPE NCC Requests in Audits

Database Accuracy Verification:

• Confirm organization information is correct
• Verify contact persons are reachable
• Validate business address is accurate
• Confirm resources are properly registered

Resource Usage Documentation:

• Assignment records for customer allocations
• Justification for address space requests
• Evidence of resource utilization
• Network diagrams or topology information
• Customer contracts or service agreements

Policy Compliance Checks:

• Confirmation of proper assignment practices
• Evidence of needs-based allocation
• Verification of proper status codes
• Review of transfer or sub-allocation practices

Abuse Handling Evidence:

• Abuse contact monitoring procedures
• Examples of abuse report handling
• Corrective action documentation

How to Respond to Audits

Step 1: Acknowledge Receipt

• Confirm you received the audit request
• Indicate you're preparing response
• Ask for clarification if anything is unclear

Step 2: Gather Information

• Collect all requested documentation
• Review database entries for accuracy
• Prepare explanations for any discrepancies
• Organize materials systematically

Step 3: Review and Verify

• Check every figure against the RIPE Database before sending
• Verify documents are current
• Remove sensitive customer data if appropriate

Step 4: Submit Response

• Send through LIR Portal or email as instructed
• Include all requested materials
• Provide clear explanations
• Submit before deadline

Step 5: Address Findings

• Review RIPE NCC's findings carefully
• Correct any identified issues promptly
• Update database as needed
• Implement process improvements
• Confirm completion of corrective actions

What does an LIR pay the RIPE NCC, and when?

Payment Requirements

Annual contribution:

• €1,800 per LIR account in 2026 (ripe-848); €1,000 sign-up fee for a new account.
• Invoices are due 30 days after the invoice date; members joining mid-year pay pro rata per quarter (Billing Procedure 2026).
• From 2027 the fee is €1,894 per LIR account with the first ASN included; each additional ASN costs €50 and each independent assignment €75 (ripe-867, adopted at the May 2026 General Meeting).

Per-resource fees in 2026:

• €50 per ASN assignment per year, €75 per independent assignment (PI, anycast, IXP), both counted on the resources registered on 31 December and invoiced in January.
• Every LIR account's contribution must be paid before the member can transfer resources.

Unpaid invoices:

The RIPE NCC sends a reminder 30 days after the invoice date. At day 60 it suspends services and sends a final reminder; from then on no new or ongoing requests are processed. At day 120 the termination notice goes out (ripe-858 A.1.2.2). Reactivating a terminated agreement costs the €1,000 sign-up fee plus every outstanding invoice. A full cost picture, including what membership buys against a sponsored alternative, is in RIPE LIR Membership Costs and Benefits.

Maintaining Good Financial Standing

Keep the billing contact current in the LIR Portal, and if an invoice will be late, contact the RIPE NCC billing department before day 60, when services are suspended.

Staying Compliant: Ongoing Requirements

RPKI: keep a delegated CA alive

If you run a delegated RPKI CA, keep its manifest and CRL current: since 8 June 2026 the RIPE NCC revokes a delegated CA that has had no valid manifest and CRL for 90 days (ripe-847). Check that your ROAs still cover what you announce with the RPKI checker.

Staying Informed

RIPE policies change through the Policy Development Process; proposals and their phases are listed on the RIPE policies page. In September 2026, for example, proposal 2026-01 (first ASN without needs justification) was in drafting and proposal 2024-01 (larger PI assignment sizes in IPv6) closed its Review Phase on 23 September 2026; neither is policy.

What happens if an LIR does not comply?

The grounds and the clocks are published in ripe-858, section A.1.2.

A closed member loses the right to act as sponsoring LIR, and its End Users' resources enter deregistration: four weeks to object, then three months during which the RIPE NCC locks the maintainers and revokes the RPKI certificates before the objects are deleted (ripe-858 B.2). There is no fine and no fee adjustment in the charging scheme; the money consequence of a termination is the €1,000 sign-up fee plus arrears if you want the agreement back.

Appeal and Dispute Resolution

A member can request arbitration under the RIPE NCC Conflict Arbitration Procedure, referenced in ripe-858 A.1.2.1 and B.2.1; during the four-week objection window the RIPE NCC locks the records pending the arbiter's ruling. Write to ncc@ripe.net first with the evidence: most registry disputes are corrected data, not arbitration cases.

Getting Compliance Help

RIPE NCC Support

• Guidance on policy interpretation
• Compliance questions answered
• Audit preparation assistance
• Training and resources

Help from a sponsoring LIR

We are a RIPE NCC member LIR ourselves. For RIPE Database objects, RPKI setup or audit preparation on your own LIR, see LIR consulting, on quote. If you need one ASN rather than a membership, a sponsoring LIR carries these obligations for you: an ASN through our sponsorship costs €130 per year (as of September 2026), see ASN registration. If your current sponsoring LIR is closing or stops sponsoring you, change your sponsoring LIR inside the ripe-815 windows described above. Membership itself is covered in How to Become a RIPE LIR.

FAQ: LIR compliance questions

How much notice does a member give to close an LIR? Three months in writing (ripe-858 A.1.1). File the closure request before 31 December, otherwise the next year's contribution is due in full.

What happens if an LIR does not pay its RIPE NCC invoice? A reminder at day 30, suspension of services and a final reminder at day 60, and a termination notice at day 120 (ripe-858). No new requests are processed while the invoice is more than 60 days overdue.

Does ripe-705 require abuse reports to be answered within 24 hours? No. The policy requires a valid abuse-mailbox on the objects, validated by the RIPE NCC at least once a year, and says nothing about handling or response times.

Does the holder of a sponsored ASN have LIR compliance duties? No membership duties. The End User signs a contract with the ripe-637 clauses (keep data current, no sub-assignment, pay the fee) and the sponsoring LIR answers to the RIPE NCC for the registration.

Summary

The RIPE NCC enforces four things: correct registry data, a working abuse-c, policy-compliant use of resources and paid invoices. The deadlines that matter are 30, 60 and 120 days on an invoice, three months' notice to leave, and 31 December for closures and ended sponsorships. If you only need one ASN, those duties sit with your sponsoring LIR.

Sources:

• ripe-848, RIPE NCC Charging Scheme 2026
• ripe-867, RIPE NCC Charging Scheme 2027
• RIPE NCC Billing Procedure 2026
• ripe-812, RIPE NCC Standard Service Agreement
• ripe-858, Closure of Members and Deregistration of Internet Number Resources
• ripe-863, Due Diligence for the Quality of the RIPE NCC Registration Data
• ripe-705, Abuse Contact Management in the RIPE Database
• ripe-637, Contractual Requirements for Provider Independent Resource Holders
• ripe-815, Sponsoring LIR and End User changes
• ripe-847, Revocation of non-functional delegated RPKI CAs
• Assisted Registry Check
• RIPE Policies