What does RIPE NCC do with IP addresses and ASNs?
RIPE NCC is the Regional Internet Registry serving Europe, the Middle East and parts of Central Asia. It distributes and registers Internet number resources, including IP address space and autonomous system numbers (ASNs), under the policies applicable to its region. It also maintains a database of registration and contact information used by network operators.
RIPE is a community; RIPE NCC is an organisation
RIPE is an open forum in which network specialists discuss the operation of the Internet and develop resource policies. RIPE NCC is a separate non-profit organisation that administers those policies and provides services to its members and resource holders. The community chair, RIPE NCC management and the organisation’s board have different responsibilities. Names and board composition can change; a timeless explanation is more useful than an old list of office holders. For current roles, consult the organisation’s own site.
What the database reveals
A RIPE Database query may show the registration of an IP prefix, an ASN, an organisation and technical or abuse contacts. These records help operators coordinate routing and report problems. They do not show who sat at a particular computer when an event happened. A provider can assign addresses dynamically, share one public IPv4 address among many customers, or operate a proxy. If you investigate suspicious traffic, record the address, an exact timestamp with time zone and a concise description before contacting the relevant network operator. Avoid sending personal data that the operator does not need.
How Internet number resources are obtained
IPv4, IPv6 and ASN requests have different rules and contractual requirements. RIPE NCC has exhausted its free IPv4 pool for normal distribution; some IPv4 allocation requests use a waiting list under restricted conditions. It no longer issues new IPv4 provider-independent assignments, while IPv6 PI remains available under its policy. An ASN alone does not provide Internet access: the holder still needs network connections and a routing configuration. The official RIPE NCC resource page links to the current policies and procedures.
Using a result responsibly
A resource holder, route registration and autonomous system are related but distinct objects. A matching name in one record is not a substitute for checking the others or confirming current operational arrangements. Registration data can also be incomplete or out of date. For a security incident, the operator’s logs and timing may be necessary to connect an address to a customer. For a business decision, verify ownership and transfer conditions with the relevant registry process rather than assuming that a publicly visible record proves a transaction.
