RIPE NCC: All You Need To Know

RIPE NCC at a glance

If you are adding customers, launching a hosting service or expanding into Europe, understanding RIPE NCC helps you separate the address records you need from the capacity and support your business needs.

• Registration: RIPE NCC maintains number-resource records for Europe, the Middle East and parts of Central Asia.
• Deployment: your addresses, origin ASN, routing records and upstream configuration need to work together.
• Growth: LARUS gives you direct IPv4 supply and a Continuity relationship built around keeping your customers connected.

What is RIPE NCC?

RIPE NCC means Réseaux IP Européens Network Coordination Centre. It is the Regional Internet Registry (RIR) for Europe, the Middle East and parts of Central Asia. Its work includes registering IPv4 and IPv6 addresses and Autonomous System Numbers (ASNs), alongside technical coordination services.

An IP address identifies an interface on an IP network; an ASN identifies an autonomous network in interdomain routing. Those records help independently operated networks connect. They are one part of delivering the reachable services your customers buy.

RIPE NCC and the RIPE community

Based in Amsterdam, RIPE NCC began operations in 1992. It describes itself as a not-for-profit membership organisation. Its members include ISPs, telecoms companies and other organisations operating networks. See its description of its role and service region.

RIPE is the wider technical community; RIPE NCC is the organisation that provides registry services and supports that community as its secretariat. Participating in a RIPE discussion and holding RIPE NCC membership are different relationships.

How RIPE NCC fits into your IPv4 expansion

Resource registration distinguishes an allocation, from which a registry or provider can make further assignments, from an assignment for use by an end network. The RIPE Database also carries resource, contact and routing-policy information that operators use when coordinating a deployment or investigating a problem.

RIPE NCC exhausted its remaining IPv4 pool in November 2019. Its published waiting-list process uses recovered addresses and offers one /24 to an eligible LIR that has never received an IPv4 allocation from RIPE NCC. Check the current waiting list rather than building a launch date around an assumed allocation.

IPv4 exhaustion describes that registry pool, not the disappearance of working IPv4 networks. Existing blocks still support services and change hands through transfers and leasing. RIPE NCC's run-out explanation sets out the allocation history.

For a growing operator, the practical question is how to get usable capacity when customers need it. Direct LARUS leasing lets you expand without putting the purchase of address blocks ahead of investment in servers, bandwidth and service delivery.

RIPE NCC services your network team will encounter

Resource records and transfers

IPv4, IPv6 and ASN registrations identify resources and their registered holders. Transfer processing updates registration when resources move between organisations. Accurate contacts and routing objects make it easier for your team and upstream providers to coordinate changes.

RPKI and routing confidence

A Route Origin Authorisation (ROA) states which ASN may originate a prefix. Networks performing route origin validation compare BGP announcements with validated ROA data. This helps them identify an unexpected origin or an announcement outside the authorised prefix length.

RPKI signs resource-related objects; it does not sign every BGP announcement or establish address ownership. Before a launch, align the ROA's origin ASN and maximum length with the routes you intend to announce. RIPE NCC documents this in its ROA management guide.

Measurements and operational learning

RIPE Atlas measurements and RIPEstat information help teams investigate reachability and routing. Training covers subjects such as IPv6, database management and BGP security. Use these tools to answer a customer-facing question: can people reach the service reliably from the networks that matter to them?

Membership, fees and policy: what each changes

Organisations can apply for RIPE NCC membership and open a Local Internet Registry (LIR) account for registry services. Membership also provides a route to participate in the association's General Meeting, including board elections and decisions on the charging scheme.

The 2026 charging scheme uses an annual contribution per LIR account with additional resource-related charges. It is not simply a sliding scale based on company size. The published 2027 scheme sets out the next year's model. Use the applicable scheme for budgeting.

RIPE policy development is separate: the community discusses proposals and reaches consensus through its Policy Development Process. It is not a members-only ballot. The Executive Board oversees the association and approves its activity plan and budget after member input; management handles daily operations.

For your business, these distinctions clarify where decisions sit. They do not replace a plan for address supply, renewals and the operational support your customers depend on.

RIPE NCC's strategic objectives

RIPE NCC's 2022–2026 strategy describes priorities around registry operations, community participation, network resilience, organisational governance and staff. Its 2027–2031 strategy is also published. The strategy index keeps the two periods distinct.

Assess those institutional plans against your own operating needs: dependable records, useful technical services and room to grow. Your expansion should be driven by customers and delivery, with a clear party responsible for the address service you use.

Why registration matters—and why continuity goes further

RIPE NCC is one of five RIRs, alongside AFRINIC, APNIC, ARIN and LACNIC. Coordinated number records help networks interoperate. The commercial value, however, comes from the services you build and the customers you keep connected.

Buying a block leaves the registry relationship in place. LARUS puts that interface upstream of your business, with direct responsibility for the IPv4 service. Its position is backed by Cloud Innovation's court-recognized statutory shareholder position and authorization to LARUS. Explore the rights foundation behind LARUS.

Lu Heng's Note35 explains this structural distinction. Note66 follows the responsibility beyond the transaction. Bring that longer view to your next rollout: grow with Unlimited IPv4 and a direct LARUS Continuity relationship.

RIPE NCC questions from network operators

Does joining RIPE NCC give me the IPv4 capacity I need?

Membership opens access to registry services. IPv4 supply follows a separate process, including the limited recovered-address waiting list. Start with the capacity and launch schedule your customers need, then plan the supply route around them.

Can I lease IPv4 while developing an IPv6 network?

Yes. IPv4 serves the customers and applications that still need it while you develop IPv6 connectivity. Direct leasing helps you keep expansion moving without committing capital to an IPv4 block purchase.

What should be ready before my new addresses go live?

Agree the address block, origin ASN, routing records, ROA, reverse DNS and upstream announcement with the teams involved. Then check reachability from customer networks. A coordinated handoff saves time when the first customers arrive.

What makes LARUS different from an address broker?

You work directly with the provider responsible for your IPv4 service, from deployment through renewal and continued use. LARUS combines address supply with Continuity so your team can focus on the services customers are buying from you.