The RIPE NCC, the network coordination center of the Réseaux IP Européens community, is the regional internet registry for Europe, the Middle East and parts of Central Asia. It allocates and registers IPv4 addresses, IPv6 addresses and autonomous system numbers for its region and maintains the public registry that records who holds them. In internet governance, it is one of five regional internet registries that together administer the global number resources delegated by IANA.
The organization is an independent, not-for-profit membership association based in Amsterdam and established in 1992. It serves a region of roughly 75 countries, and its members are mainly internet service providers, hosting companies, telecommunications operators, universities and large enterprises.
Role of the RIPE NCC in number resource distribution
The RIPE NCC sits in the middle tier of a three-level hierarchy for internet number resources. IANA holds the global pool and delegates large blocks to the regional registries; the RIPE NCC then allocates and assigns resources to its members, and those members, often acting as Local Internet Registries, assign addresses to their own customers and networks.
| Level | Organization | Main function |
|---|---|---|
| Global | IANA | Delegates large blocks to the five RIRs |
| Regional | RIPE NCC and the other RIRs | Allocates resources and keeps the registry |
| Local | Local Internet Registries | Assign addresses to end users and networks |
| End user | Companies, institutions, households | Use addresses on their networks |
Its tasks go beyond handing out numbers. The RIPE NCC keeps the registration accurate through the RIPE Database, delegates reverse DNS zones for its address space, and operates a trust anchor for RPKI, which lets network operators cryptographically verify which autonomous system may announce a given prefix.
The five regional registries coordinate through the Number Resource Organization, which presents their joint positions and handles global policies that require the agreement of all regions, such as rules for how IANA distributes returned address space. Within its own region, however, the RIPE NCC applies only the policies adopted by the RIPE community, so allocation rules can differ noticeably from those of ARIN or the other registries.
RIPE and the RIPE NCC are not the same
A frequent source of confusion is the difference between RIPE and the RIPE NCC. RIPE is an open community forum of network operators and other interested people, with no formal membership, which meets twice a year and works through mailing lists. The RIPE NCC is the legal entity that implements the policies and provides the services.
| Aspect | RIPE community | RIPE NCC |
|---|---|---|
| Legal form | Open forum without legal personality | Association under Dutch law |
| Membership | Anyone may participate | Paying members, mostly LIRs |
| Main output | Policies and best practice documents | Registry services and operations |
| Decision process | Consensus in working groups | General Meeting and Executive Board |
| Funding | Not applicable | Membership fees |
This split reflects the bottom-up model of internet governance. The community writes the rules through an open Policy Development Process, while the RIPE NCC members decide on budget, fees and governance of the organization at the General Meeting, where they also elect the Executive Board.
Services and resources the RIPE NCC provides
The RIPE NCC combines registry services for members with public tools for the whole internet. Several of these services are used daily by network engineers far outside its own region.
- RIPE Database: the public registry of address and AS holders, routing policy objects and contact details, queryable through WHOIS and RDAP.
- RPKI: certificates that bind address blocks to holders, allowing route origin validation against hijacks.
- K-root: operation of one of the thirteen named DNS root server identities, distributed through anycast.
- RIPE Atlas: a global network of measurement probes for connectivity and latency tests.
- RIPEstat: an interface that combines routing, registry and geolocation data for any prefix or AS.
These services make the RIPE NCC a neutral source of routing and registration data, which is why its databases appear in abuse handling, outage analysis and research.
Address policy after IPv4 exhaustion
The RIPE NCC ran out of freely available IPv4 address space in November 2019, after years of rationing. Since then, IPv4 space comes mainly from returned or recovered addresses, distributed in small blocks through a waiting list, and from transfers between holders, which the registry records but does not price.
| Resource | Typical route | Practical note |
|---|---|---|
| IPv4 addresses | Waiting list or transfer market | Small blocks, long waits or market prices |
| IPv6 addresses | Direct allocation, commonly a /32 for an LIR | Larger blocks available with justification |
| AS numbers | Assignment on request | Requires a routing need, usually multihoming |
| Reverse DNS | Delegation for held address space | Managed through the registry |
The registry strongly encourages IPv6 deployment, since IPv6 space is plentiful and a single standard allocation contains far more addresses than the entire IPv4 internet.
Limitations and common misconceptions
The RIPE NCC does not own IP addresses and does not sell them. It registers who holds them according to community policy. It also does not control routing: a registry entry does not force any network to accept an announcement, which is why RPKI adoption by operators matters.
Similarly, the registry is not a content regulator. It does not decide what is hosted on an address, and complaints about spam or illegal content belong with the abuse contact of the resource holder, which the RIPE Database publishes. The RIPE NCC can deregister resources only in narrow cases, such as false registration data or unpaid fees.
The simple explanation
Every device on the internet needs a numeric address. Someone has to make sure that no two networks get the same numbers. For Europe, the Middle East and parts of Central Asia, that job belongs to the RIPE NCC. It works like a land registry for internet addresses.
Providers and large organizations become members and receive blocks of addresses. The RIPE NCC writes down who holds which block. That record helps the whole internet know where traffic should go and whom to contact when something goes wrong.
How it is used in practice
A regional broadband provider in Central Europe plans to connect to two upstream carriers for redundancy. To route its own address space independently, it becomes a member of the RIPE NCC and opens a Local Internet Registry.
Through the member portal it requests an AS number, receives an IPv6 /32 allocation and joins the waiting list for a small IPv4 block, buying a further /22 on the transfer market to cover immediate needs. The registry records the transfer and updates the RIPE Database. The network team then creates RPKI route origin authorizations so that other networks can validate its announcements.
Within a few weeks the provider announces its prefixes through both carriers. When a carrier fails during a storm, traffic shifts automatically, and customers notice no lasting outage.