Fact-checked by Grok 2 weeks ago

RIPE NCC

The RIPE Network Coordination Centre (RIPE NCC) is an independent, not-for-profit membership organisation and one of five Regional Registries (RIRs) that allocate and register number resources—such as IPv4 and addresses and Autonomous System Numbers (ASNs)—while supporting the technical infrastructure and coordination of the in its service region of 76 countries across , the , and parts of . It serves over 20,000 member organisations, primarily service providers, telecommunications companies, and large corporations acting as Local Registries (LIRs) to distribute these resources locally. The origins of the RIPE NCC trace back to the RIPE community, which formed in 1989 when a group of European network operators began holding regular meetings to exchange experiences and coordinate technical aspects of development. In 1990, the community decided to establish a dedicated coordination centre, leading to the formal creation of the RIPE NCC in April 1992 as the entity responsible for distributing space in the region. It became a legal entity in 1998, solidifying its role in fostering an open and inclusive model through community-driven policies and activities. Beyond , the RIPE NCC maintains the RIPE Database—a public registry of Internet routing information and contact details for networks in its region—and serves as the secretariat for the RIPE community, organising biannual RIPE Meetings, facilitating working groups on topics like and , and developing policy documents. It also operates the K-root server, one of the 's 13 authoritative DNS root name servers, contributes to global stability through neutral data analysis and publications, and delivers technical training programs on subjects including BGP, the RIPE Database, and . These efforts underscore its commitment to enabling the reliable operation and evolution of the while upholding values of trustworthiness, openness, and inclusivity.

Overview

Role as Regional Internet Registry

The RIPE NCC operates as the not-for-profit (RIR) for , the , and parts of , where it allocates and registers number resources such as and addresses and Autonomous System Numbers (ASNs) to ensure their unique and efficient use across the region. This service region spans 76 countries, enabling the to support the growth and stability of infrastructure by distributing these resources to network operators and service providers. As one of five RIRs globally, the RIPE NCC coordinates with other registries through the Number Resource Organization (NRO) to maintain consistent policies and practices in resource management. In collaboration with the (IANA), the RIPE NCC receives initial allocations from the global pools of IP addresses and ASNs, which it then subdivides and assigns to local entities while upholding principles of fairness, conservation, and technical coordination to prevent conflicts and support scalable expansion. This partnership is essential for preserving the hierarchical distribution model that underpins the Internet's addressing system, ensuring resources are available where demand is highest without global fragmentation. As of October 2025, the RIPE NCC serves approximately 20,000 members, consisting of Local Registries (s) operating more than 20,000 accounts, which primarily operate within its 76-country service region but extend to organizations in over 120 countries worldwide. These members, largely consisting of service providers, telecommunications companies, and content networks, rely on the RIPE NCC for resource access and registration to facilitate their operations. Headquartered in , , the RIPE NCC functions as a membership-based that prioritizes from commercial interests, in its operations through , and community-driven to align its activities with the needs of the broader ecosystem. The RIPE NCC serves as the administrative body, distinct from the RIPE community, which acts as an open technical forum for policy discussions and development.

Organizational Structure and Membership

The RIPE NCC operates under a governance model centered on its Executive Board, which is elected by members during the biannual General Meetings to oversee operations and provide strategic guidance to senior management. The Executive Board, consisting of seven members, is responsible for representing the membership and ensuring alignment with interests. Additionally, the RIPE provides oversight through these General Meetings, where members vote on key resolutions, including board elections and policy matters. As of 2025, the RIPE NCC employs approximately 197 full-time equivalents (FTEs), encompassing staff directly hired by the organization and those contracted through an Employer of Record for flexibility. This workforce is distributed across functions, including The Registry (43 FTEs); Information Services (70 FTEs); External Engagement & Community (47 FTEs); and Organisational Sustainability (37 FTEs). Membership in the RIPE NCC is primarily structured around Local Internet Registries (LIRs), which include Internet service providers and other organizations responsible for managing networks and making assignments to end users. End Users, typically non-network providers requiring direct Provider Independent (PI) resources, receive assignments through a sponsoring rather than direct membership, while Legacy Holders—entities with pre-RIR assignments—maintain resources under separate service agreements or can opt to join as full members without a sign-up fee. To join, organizations must submit an application, undergo verification, and sign the RIPE NCC Standard Service Agreement (), a governed by Dutch law that outlines rights, obligations, and access to services. Members benefit from allocations of number resources, such as addresses and Autonomous System Numbers, along with access to tools like the LIR Portal for management and services including (RPKI) certification. They also hold voting rights at General Meetings, enabling participation in and decisions, and gain entry to , analysis tools, and community events.

History

Founding and Early Development

The RIPE (Réseaux IP Européens) community emerged in 1989 as a cooperative forum for European network operators, enabling them to share operational experiences and coordinate technical aspects of development. The inaugural RIPE Meeting convened in that year, establishing a foundational platform for collaboration among academics, researchers, and early network providers in the region. Key founders included Daniel Karrenberg and Rob Blokzijl, who played pivotal roles in initiating these discussions amid the nascent growth of -based networking in . As adoption accelerated, the volunteer-based RIPE community recognized the need for dedicated administrative support, leading to the formal establishment of the RIPE NCC on 1 April 1992 in , hosted initially at the NIKHEF institute. This marked the creation of the world's first (RIR), tasked with handling operational duties such as allocation and registration to alleviate the burden on the informal RIPE forum. Daniel Karrenberg was appointed as the inaugural manager, overseeing a small team focused on building essential infrastructure. From August 1992, the RIPE NCC began distributing and recording allocations in the RIPE Database, an early whois-accessible system for maintaining public network registration details. The early years presented significant challenges, including the need to manage Europe's rapidly expanding infrastructure in the early 1990s, which strained limited resources and personnel. Despite a surging workload from growing network demands, the organization faced staffing shortages with no expansion since its . Initial funding came primarily from (the European academic network association), supplemented by contributions from EARN and EUnet, facilitating the shift from coordination to a structured registry model.

Key Milestones and Expansions

During the 1990s, the RIPE NCC underwent substantial expansion, reaching over 1,000 members by 1999 as infrastructure proliferated across and beyond. The organization launched the RIPE Database in 1992 to facilitate the registration and management of number , marking a foundational step in coordinated . Additionally, the RIPE community, through the RIPE NCC, played a key role in the early development of during the mid-1990s, contributing to specifications aimed at addressing the limitations of IPv4 . In the 2000s, the RIPE NCC participated actively in the formation of the in 1998, helping to establish a global framework for and resource coordination. The exhaustion of the IPv4 free pool began in 2011 when the allocated its final blocks to the Regional Internet Registries, prompting the RIPE NCC to implement phased allocation policies from its remaining reserves. Service region boundary adjustments also occurred during this period, including the 2005 establishment of the , which assumed responsibility for several African territories previously served by the RIPE NCC and other RIRs. The 2010s and 2020s brought further pivotal developments, including the full exhaustion of the RIPE NCC's IPv4 pool in November 2019, which accelerated the establishment of a regulated transfer market for IPv4 addresses to meet ongoing demand. The organization marked its 25th anniversary in 2017, reflecting on decades of growth and contributions to stability. In response to the in 2020, the RIPE NCC adapted by converting its flagship RIPE 80 meeting to a fully , ensuring continued community engagement amid global restrictions. The 2024 annual report noted 19,993 members as of the end of 2024. By October 2025, membership had exceeded 20,000, reaching 20,060. In 2025, the RIPE NCC published its Activity Plan and Budget, outlining priorities such as enhanced resource management and community support, including the introduction of a new €50 annual fee per Autonomous System Number (ASN) assignment to sustain operations. The plan emphasizes three key focus areas for (RPKI) deployment to bolster routing security, reflecting ongoing efforts to mitigate risks.

Core Services

Internet Number Resource Allocation

The RIPE NCC serves as the (RIR) responsible for allocating number resources, including IPv4 addresses, addresses, and Autonomous System Numbers (ASNs), within its service region covering , the , and parts of . These allocations ensure the efficient and fair distribution of globally unique identifiers to Local Internet Registries (LIRs) and end users, guided by policies developed by the RIPE community to promote the 's stability and growth. Allocations are made exclusively to RIPE NCC members, who must demonstrate compliance with established criteria to receive resources. For IPv4 addresses, allocations have become sparse following the exhaustion of the RIPE NCC's free pool in November 2019. Current policy limits new allocations to a single /24 block (256 addresses) per , placed on a first-come, first-served waiting list, with no guaranteed processing time. Justification is required through registration in the RIPE Database, including administrative and technical contacts, and confirmation that the addresses will be used for assignments within the service region. Smaller blocks returned to the pool are reserved for specific uses, such as Exchange Points (IXPs), while larger recovered blocks may be reallocated. Inter-RIR transfers of IPv4 resources have been permitted since under the RIPE Resource Transfer Policies, allowing resources to move between RIR service regions with evaluation by both involved registries. IPv6 allocations follow a needs-based approach to encourage adoption and long-term planning. Initial allocations to LIRs are typically a /32 prefix, provided the LIR submits a plan for sub-allocations or end-site assignments within two years, with larger sizes (/29 to /23) requiring additional justification based on projected users, infrastructure, and utilization over three to five years. Subsequent allocations are granted when at least 80% of the existing space is utilized (using the HD-Ratio of 0.94 as a metric) or when new needs are demonstrated, often doubling the previous allocation size for contiguous efficiency. These criteria aim to minimize fragmentation while supporting scalable deployment. ASN assignments are designed to support multi-homing, where an organization connects to multiple external networks requiring a unique external routing policy as defined in . Under current policy, a single ASN is assigned per organization upon justification of multi-homing needs, with the routing policy described in and registered in the ; additional ASNs require further evidence of distinct routing requirements. Legacy ASNs, obtained prior to the establishment of RIRs, are handled through special service agreements with the , providing maintenance, database registration, and other registry services without altering ownership rights, subject to accurate data provision and compliance with policies. The may terminate such services for non-compliance, with members given opportunities to regularize their status. Procedures for all allocations begin with a RIPE NCC member submitting an application through their account in the LIR Portal, including detailed justification and contact information. RIPE NCC staff evaluate the request against applicable policies, typically processing it within one working day if complete, though complex cases may require additional documentation or sanctions checks. Approved resources are registered directly in the RIPE Database by the RIPE NCC to ensure transparency and accuracy. Inter-RIR transfers for and ASNs follow similar evaluation processes, with both registries confirming compliance since their introduction in 2009. Policies governing these allocations are developed through the RIPE Policy Development Process (PDP), an open, bottom-up, consensus-based mechanism involving the community via working groups, mailing lists, and RIPE Meetings. Proposals are submitted using a standard template, discussed for at least four weeks, reviewed for consensus by working group chairs, and finalized after a last-call period, with the RIPE NCC providing administrative support and impact analyses. Recent examples include proposal 2024-01, which seeks to revise IPv6 Provider Independent (PI) assignment policies by clarifying requirements, setting minimum /48 and maximum /36 sizes at nibble boundaries, and prohibiting sub-assignments to reduce operational burdens and fragmentation; it remains in the discussion phase as of October 2025. Similarly, proposal 2025-01 proposes relaxing ASN criteria to allow a single ASN without justification for LIRs and end users, reflecting the non-scarce nature of 32-bit ASNs, while requiring justification for additional ones; it is also in discussion as of October 2025. PI assignments, intended for end users needing portable addresses independent of providers, are requested via a sponsoring LIR and limited in size to prevent routing table bloat. In 2024, the RIPE NCC issued 1,116 allocations compared to 773 IPv4 allocations, alongside 2,205 ASN assignments, highlighting the shift toward amid IPv4 scarcity. These figures underscore the RIPE NCC's role in managing resource distribution, with all allocations registered in the RIPE Database for global visibility.

RIPE Database and Routing Registry

The RIPE Database is a publicly accessible, -compatible repository maintained by the RIPE NCC, serving as the primary for registering and querying details of number resources, including IPv4 and address allocations, Autonomous (AS) numbers, and associated contact information within the RIPE NCC service region. It structures data into discrete objects, such as inetnum for IP network ranges, aut-num for AS identifiers, and person or role for maintainer and administrative contacts, enabling transparent tracking of resource usage and ownership. The database employs the Routing Policy Specification Language (RPSL), as defined in RFC 2622, to standardize object syntax and attributes, while supporting queries through web interfaces, command-line clients, and programmatic APIs for integration into tools. The RIPE Routing Registry (RR), a specialized of the RIPE Database, functions as an Internet Routing Registry (IRR) that stores routing policies, route objects specifying announced prefixes, and details on sessions to document network operators' BGP intentions. Using RPSL, operators publish filter rules and policy statements that automate BGP configurations, such as prefix validation and route filtering, reducing the risk of unintended announcements or hijacks. The RR also facilitates (RPKI) by representing Route Origin Authorizations (ROAs) as RPSL-compatible route or route6 objects, allowing cryptographic validation of prefix origins during BGP session setup. Integration with complementary RIPE NCC tools enhances the database's utility for routing analysis and verification. The Routing Information Service (RIS) collects real-time BGP data from global collectors, cross-referencing it with database registrations to map prefix-to-AS relationships and detect anomalies like route leaks. Similarly, RIPE Atlas leverages a worldwide probe network to measure connectivity and latency, correlating results with database entries for end-to-end network diagnostics. In 2024, security-focused updates introduced new inetnum statuses, including AGGREGATED-BY-LIR for grouping assignments and ALLOCATED-ASSIGNED PA for compact registration of small provider-aggregatable blocks, alongside deprecation of legacy authentication methods like MD5-PW to bolster object protection. Maintenance of the RIPE Database ensures data integrity and interoperability through daily mirroring of operational records from other Regional Internet Registries (RIRs), providing a unified view of global resource distributions. Since its implementation in phases concluding by early 2014, policy requires an abuse-c: attribute in all organisation objects, linking to a role with an abuse-mailbox: email for streamlined reporting of security incidents across allocated and assigned resources. Community-driven access policies emphasize maintainer responsibility for updates, with RIPE NCC oversight via tools like hierarchical authorizations (mnt-ref:) and notifications (notify:), promoting reliable, open usage while verifying resource allocations.

Community Engagement

RIPE Meetings and Events

The RIPE Meetings are biannual five-day events held twice a year, typically in spring and autumn, where Internet service providers, network operators, and other stakeholders gather to discuss technical, operational, and policy-related topics in infrastructure. For example, RIPE 91 took place in , , from 20 to 24 October 2025, drawing participants for sessions on , , and . These meetings typically attract over 500 attendees, with a attendance of around 618 over the past decade, including representatives from more than 100 countries. Hosted in cities within the RIPE NCC's service region, such as or , the events have adopted a format since to enable broader participation amid the . The structure emphasizes hands-on training through tutorials on topics like and BGP operations, alongside presentations, (BoF) sessions, and informal networking opportunities that foster collaboration among operators. Social components, including welcome receptions and dinners, complement the technical agenda, enhancing peer connections and community building. Beyond the main RIPE Meetings, the RIPE NCC organizes targeted workshops, webinars, and regional events to support technical skill-building and knowledge sharing. Examples include the (SEE) workshops and and Internet Forum (CAPIF) gatherings, which address localized Internet challenges through practical sessions on and . Additionally, the RIPE NCC supports initiatives via the Community Projects Fund, which allocated up to EUR 250,000 in 2023 to fund non-commercial projects enhancing and . These events serve as key venues for proposing and refining Internet resource policies, while facilitating networking that strengthens ties across the global operator ; they also connect participants to ongoing RIPE working groups for deeper collaboration.

Working Groups and Policy Development

The RIPE operates through a network of active working groups that facilitate collaborative discussions on technical standards and operational challenges related to number resources and infrastructure. There are currently 10 such groups, including the Address Policy , which develops policies for Internet address and routing identifier management; the , focused on promoting IPv6 adoption through education and deployment experiences; the Routing , addressing IP routing technologies; and the Security , which tackles online security from both technical and non-technical angles. Each group is moderated by 2-3 community-elected chairs who assess and organize activities. These working groups function primarily through open mailing lists, where members—open to anyone without requiring RIPE NCC membership—exchange ideas and propose solutions, with archives publicly available for . Discussions often extend to sessions held during RIPE Meetings, serving as key venues for in-depth review and refinement of topics. This structure ensures a bottom-up approach to addressing issues like and . Policy development within the RIPE community follows an established, consensus-based process outlined in the RIPE Policy Development Process (), which is open, transparent, and driven by community input rather than top-down directives. Proposals are submitted via mailing lists or directly to the RIPE Document Editor, then enter phases of discussion, last call for review, and evaluation of consensus, often tested through simulations or impact analyses prepared by the RIPE NCC. Final ratification occurs at RIPE Meetings following broad community feedback, after which the RIPE NCC implements approved policies. The process emphasizes inclusivity, allowing global participation from operators, researchers, and other stakeholders, which has historically extended the community's influence to broader standards, such as contributions to IETF (RFCs) that shaped space management. Early examples include RIPE's role in RFC 1466, which provided guidelines for allocation and helped establish the model. The RIPE NCC provides neutral administrative support throughout, ensuring policies are documented and enforced without altering their substance. In recent years, working group activities have increasingly centered on enhancing routing security and data-driven insights, with a particular 2025 emphasis on accelerating Resource Public Key Infrastructure (RPKI) adoption to mitigate BGP hijacks. This includes the ratification of Proposal 2025-02, which enables the revocation of persistently non-functional delegated RPKI Certificate Authorities to improve system reliability. Additionally, the MAT Working Group has fostered collaborations on measurement tools and analysis, such as integrating RPKI validation data with broader Internet metrics to support evidence-based policy refinements.

Service Region

Current Geographic Coverage

The RIPE NCC's service region encompasses 76 countries, primarily spanning , the , and parts of , as defined by the with specific adjustments to align with its operational boundaries. This includes all member states, the , , , the , , and , among others, enabling the allocation of number resources such as addresses and Autonomous System Numbers (ASNs) to support regional infrastructure. The exact boundaries are determined by the assignment of country codes to the RIPE NCC by the (IANA). Eligibility for RIPE NCC membership is open to any legal entity or that provides services within this service region, without a strict residency requirement for the organization itself, which facilitates participation from global entities operating locally. To function as a Local Internet Registry (LIR) and receive resource allocations, members must demonstrate intent to assign or sub-allocate these resources to end users or networks in the service region, ensuring resources are utilized effectively within the defined area. This structure promotes broad involvement while maintaining focus on regional needs. In managing resources across this diverse region, the RIPE NCC applies tailored policies that account for varying economic and infrastructural conditions, such as higher adoption rates in —where countries like and exceed 70% IPv6 traffic—compared to slower progress in , where adoption remains below 20% in nations like as of late 2024. These differences influence allocation strategies, with an economies benefiting from advanced deployment and Central Asian areas receiving targeted support for . As of 2025, the RIPE NCC continues to monitor growth across its region, with particular emphasis on supporting new members in expanding areas like the , including through a dedicated legal entity established in in 2024 and collaborations such as a with the to enhance digital infrastructure.

Historical and Former Regions

In the , the RIPE NCC expanded its service region beyond to include the and parts of , responding to the rapid growth of and the need for coordinated number in these emerging areas. This expansion allowed the RIPE NCC to support a broader geographic scope, aligning with the increasing participation of network operators from these regions in activities. The RIPE NCC also served parts of during this period, providing allocations and registration services to local providers in those areas. These additions reflected the global spread of the and the RIPE NCC's role in facilitating where no dedicated regional registry yet existed. Boundary adjustments in 2005 marked significant changes to the RIPE NCC's service area, primarily through the establishment of as Africa's dedicated , leading to the transfer of responsibility for African countries—such as and —from the RIPE NCC to in line with IANA guidelines. This handover ensured alignment with local needs, with existing resource holdings, database entries, and Local Internet Registry (LIR) memberships transitioned to to maintain continuity for affected members. The rationale for these adjustments was to enhance efficiency, reduce administrative burdens on members through regionally tailored support, and adhere to international standards for avoiding jurisdictional overlaps in number management. Impacts on members included seamless transfers without loss of allocations, though they required updating contracts and directing future requests to the new RIR. As of 2025, legacy effects persist through inter-RIR transfer policies, allowing former RIPE NCC members in these regions to IPv4 addresses and ASNs with the RIPE NCC via mechanisms coordinated among the five RIRs.

Financial Model

Membership Fees and Charging Scheme

The RIPE NCC has maintained a flat fee structure for membership since 2012, charging a uniform annual service fee to all Local Internet Registries (LIRs) regardless of the size or quantity of resources held. For 2025, this fee is set at €1,800 per LIR account, representing a 16.13% increase from €1,550 in 2024 to account for and economic pressures. New LIR members also pay a one-time sign-up fee of €1,000, applied for mid-year joins, while existing members are billed for the full year based on account status as of 31 December 2024. End Users and Legacy Internet Resource Holders follow separate but aligned structures. End Users, who do not maintain LIR accounts, incur no annual membership fee but pay for sponsored independent assignments, such as Provider Independent (PI) IPv4/IPv6 addresses at €75 each in 2025 (up from €50). Legacy Holders with direct agreements pay the same €1,800 annual fee per account as LIRs, without a sign-up fee unless requesting additional resources, at which point the €1,000 fee applies. A new annual fee of €50 per Autonomous System Number (ASN) was introduced in 2025, covering infrastructure, sponsored, and legacy ASNs as part of the service fee. The 2025 charging scheme, published on 5 September 2024, emphasizes adjustments for while ensuring fees remain independent of holdings, promoting equitable to services. These revenues fund core operations, including training programs and community initiatives, without tying costs to allocation volumes. Billing occurs via emailed PDF invoices in the first quarter of each year, with due within 30 days through options like bank transfer or ; overdue accounts receive reminders and may face service restrictions after 60 days. Any excess contributions from the prior year, such as 2024's redistribution, are allocated across accounts to maintain financial balance. The RIPE NCC's 2024 financial report highlights the stability of this model, with membership fees generating €34.1 million in income—comprising the bulk of the organization's €35.7 million —supporting operations and adding a €0.385 million surplus to reserves despite a minor operational deficit of €0.518 million from fewer new accounts. This approach ensures ongoing sustainability without deficits impacting service delivery.

IPv4 Transfer Market and Policies

The RIPE NCC introduced its IPv4 transfer policy in 2011 to address address space scarcity following the exhaustion of its free pool in 2012. This policy permits intra-regional transfers of complete or partial IPv4 blocks between legitimate resource holders and RIPE NCC members, without requiring needs-based justification from the recipient. Inter-regional transfers, enabled since 2016, allow movement of IPv4 resources to or from other Regional Internet Registries (RIRs) under compatible policies, where recipients from needs-based RIRs must demonstrate a plan to utilize at least 50% of the space within five years. All transfers must be documented in the RIPE Database, and IPv4 addresses are subject to a 24-month hold period after receipt to discourage rapid resale. The transfer system operates without direct fees from the RIPE NCC, relying solely on standard membership charges, which makes it accessible for participants. In 2024, the RIPE NCC facilitated over 6,200 intra-regional IPv4 transfers, involving millions of addresses and reflecting sustained market activity post-exhaustion. These transactions are typically brokered through third-party marketplaces, where average prices ranged from €30 to €40 per address, influenced by block size and demand. The policy supports both permanent and temporary () arrangements, promoting efficient circulation while maintaining registry oversight. Regulations emphasize compliance with anti-speculation measures, including the 24-month hold to prevent "" for profit and prohibitions on transfers solely for resale without operational use. Transfers require thorough documentation of the agreement between parties, and the RIPE NCC reviews for adherence to community-developed guidelines, excluding speculative entities from abusing the market. In 2025, inter-RIR coordination through the Number Resource (NRO) continued via updated comparative policy overviews, ensuring reciprocal needs-based evaluations and compatibility among RIRs to facilitate global transfers without fragmentation. This framework has significantly enabled IPv4 address reuse, allowing organizations to reallocate underutilized space amid ongoing scarcity and slow adoption. In 2024, transfers accounted for a notable portion of resource movement, with reports indicating approximately 1% (17 million addresses) of RIPE NCC-held IPv4 addresses changing hands annually, underscoring the policy's role in sustaining network growth.

Other Regional Internet Registries

The other Regional Internet Registries (RIRs) complement the RIPE NCC by managing Internet number resources in distinct geographic areas: the , established in ; the , founded in ; the Latin American and Caribbean Network Information Centre (), created in 2002; and the African Network Information Centre (), formed in 2005. All five RIRs, including the RIPE NCC, operate as not-for-profit membership-based organizations delegated by the to allocate and register IPv4 and space as well as Autonomous System Numbers (ASNs) within their service regions. These RIRs exhibit structural similarities, including bottom-up policy development processes driven by their communities and a focus on equitable resource distribution. They collaborate via the Number Resource Organization (NRO), formed in 2003 as a coordinating body to align on global initiatives such as promoting to mitigate IPv4 exhaustion and enabling inter-RIR transfers of IPv4 addresses under standardized guidelines. The RIPE NCC stands out as the oldest RIR, serving over 20,000 organizations (as of September 2025) compared to APNIC's approximately 10,000 members (as of 2024), ARIN's around 26,500 (as of 2025), LACNIC's over 13,000 (as of late 2025), and AFRINIC's about 2,500 (as of 2025). Differences arise primarily from the diverse scales and contexts of their service regions; the RIPE NCC's region spans 76 countries across , the , and , fostering a dense network of , whereas AFRINIC covers 54 African countries but contends with under-resourcing, including disputes and limited that have constrained its operations; a new board was elected in September 2025 as a step toward addressing these challenges. As of mid-2025, ASN assignment policies also vary to reflect regional needs: ARIN permits any organization to receive one ASN without justification while requiring proof of unique policies for additional ones; APNIC mandates interconnection with other ASNs for portable assignments; LACNIC and allow up to six months to demonstrate interconnection plans or technical needs; and the RIPE NCC insists on with a distinct external policy. These variations ensure tailored approaches to amid differing levels of maturity and demand. The RIRs' primary collaboration occurs through the NRO, which enables them to issue joint statements and coordinate advocacy, such as unified strategies addressing IPv4 exhaustion by encouraging conservation, transfers, and migration to sustain global growth. This framework also supports interactions with global governance bodies like for consistent oversight of number resources.

Global Internet Governance Bodies

The RIPE NCC maintains a close operational relationship with the Corporation for Assigned Names and Numbers () and its functions under the (). Since 's establishment in 1998, IANA has been responsible for allocating large blocks of number resources, such as IPv4 and addresses and Autonomous System Numbers, to the RIPE NCC for subsequent distribution within its service region. The RIPE NCC participates in global policy development through 's Address Supporting Organization (), where it contributes via the Number Resource Organization Number (), which serves as the ASO Address Council to provide input on IP address policies and nominate Board members. As a founding member of the Number Resource Organization (NRO) established in 2003 through a Memorandum of Understanding among the initial four Regional Internet Registries (RIRs)—APNIC, ARIN, LACNIC, and RIPE NCC—the organization plays a pivotal role in coordinating unified RIR positions on global Internet governance matters. The NRO facilitates collaboration on issues such as WHOIS data privacy adaptations following the European Union's General Data Protection Regulation (GDPR) implementation in 2018, ensuring compliance while maintaining resource transparency across RIRs. It also advances standards for Resource Public Key Infrastructure (RPKI), promoting consistent deployment to enhance routing security worldwide through shared best practices and program alignment among RIRs. The RIPE NCC engages actively with international bodies to support the multistakeholder model of , a principle it has advocated since the NRO's inception to ensure inclusive, bottom-up policy development involving technical communities, governments, and . It contributes to the (IGF) by organizing workshops, participating in panels, and providing expertise on topics like stability and capacity building, including at the 2025 IGF in . In collaboration with , the RIPE NCC responds to cybersecurity initiatives, such as the EU Cybersecurity Strategy and the , offering technical input to ENISA and on enhancing infrastructure security. For 2025, the RIPE NCC emphasizes building organizational in response to new regulations like the Operational Resilience (DORA), focusing on compliance, risk management, and sustainable stewardship. Through these efforts, the RIPE NCC briefly references peer RIR collaborations under the NRO framework to align on broader global advocacy.

References

  1. [1]
    What We Do — RIPE Network Coordination Centre
    We're an independent, not-for-profit membership organisation that supports the infrastructure of the Internet in our service region.
  2. [2]
    About Us — RIPE Network Coordination Centre
    The RIPE NCC consists of over 20,000 organisations that act as Local Internet Registries (LIRs) to provide Internet services in their own countries. The service ...
  3. [3]
    The History of RIPE — RIPE Network Coordination Centre
    RIPE began in 1989 when a group of IP network operators based in Europe began a series of regular meetings to share experiences and carry out technical ...
  4. [4]
    RIPE NCC Service Region
    RIPE NCC serves over 75 countries, distributing Internet resources and supporting members through coordination and technical services.
  5. [5]
    Regional Internet Registries - The Number Resource Organization
    Jan 4, 2025 · Regional Internet Registries (RIRs) manage, distribute, and register Internet number resources within their regions, ensuring unique assignment ...
  6. [6]
    IANA / RIPE NCC Relationship
    IANA Transition: The RIPE NCC and IANA are key partners in ensuring the global uniqueness of Internet number resources.
  7. [7]
    Member Update: October 2024 - RIPE NCC
    Oct 24, 2024 · Registry. LIR Stats. Number of LIRs: 21,323 (-2). Number of members: 20,145 (+14). LIRs with IPv6: 15,793 (+ ...
  8. [8]
    The Relationship between RIPE and the RIPE NCC
    Mar 31, 2025 · At the end of the year 2023, the association had 20,077 members from 119 countries, a staff of 182 FTEs with 42 nationalities and operating ...
  9. [9]
    The RIPE NCC Executive Board
    The RIPE NCC Executive Board is elected by RIPE NCC members during the RIPE NCC General Meeting.
  10. [10]
    RIPE NCC Accountability Assessment
    Oct 27, 2016 · The Executive Board is charged with the management of the RIPE NCC. The Executive Board is appointed by the General Meeting from a list of ...
  11. [11]
    [PDF] Draft Activity Plan and Budget 2024 - RIPE NCC
    The full-time equivalent (FTE) numbers in this report include both employees directly employed by the RIPE NCC and staff contracted through our Employer of ...
  12. [12]
    None
    Nothing is retrieved...<|control11|><|separator|>
  13. [13]
    RIPE NCC Services to Legacy Internet Resource Holders
    The RIPE NCC maintains and publishes registry data for resources held by members and legacy Internet resource holders in our service region.Missing: End | Show results with:End
  14. [14]
    RIPE NCC Billing Procedure 2025
    There is no sign-up fee for Legacy Internet Resource Holders who become members and do not request any additional Internet number resources from the RIPE NCC.
  15. [15]
    Become a RIPE NCC Member
    Members with multiple LIR accounts are entitled to just one vote at RIPE NCC General Meetings. The oldest LIR account will receive the vote. Members opening an ...
  16. [16]
    RIPE NCC Standard Service Agreement
    Nov 10, 2023 · This Standard Service Agreement (SSA) shows the text of the contract between the RIPE NCC and its Members.Article 2 -- General · Article 6 -- Compliance · Article 9 -- Term And...
  17. [17]
    Celebrating 25 Years of RIPE — RIPE Network Coordination Centre
    In 1989, the very first RIPE Meeting was held in Amsterdam, marking the beginning of the Internet in our region as we know it today.
  18. [18]
    Daniel Karrenberg Recognised for 30 Years at the RIPE NCC
    May 18, 2022 · After starting the RIPE community with Rob Blokzijl in 1989, Daniel went on to serve as the RIPE NCC's first managing director after helping to ...
  19. [19]
    Celebrating 25 Years of the RIPE NCC
    Apr 26, 2017 · The RIPE NCC has three decades of experience in offering technical trainings on the RIPE Database, IPv6, BGP and routing security and more.
  20. [20]
    History of the RIPE Database
    From August 1992, the newly established RIPE NCC started distributing address space in its service region. Allocations made by the RIPE NCC have always been ...
  21. [21]
    RIPE 18 Minutes
    Rob Blokzijl described the current arrangement for the funding of the RIPE NCC and introduced an arrangement for the funding of the RIPE NCC of the future as ...Missing: initial early challenges<|control11|><|separator|>
  22. [22]
    25 Years of RIPE NCC Membership Development
    ### Summary of RIPE NCC Membership Development
  23. [23]
    The Regional Internet Registries, IPv6 Task Forces and ... - RIPE NCC
    Apr 27, 2004 · ... developed the basic specifications during the 1990s. The primary motivation for the design and deployment of IPv6 was to expand the ...
  24. [24]
    ICANN — RIPE Network Coordination Centre
    ICANN (the Internet Corporation for Assigned Names and Numbers) was formed in 1998. ... RIPE NCC Membership · General Meetings · Billing, Payment and Fees · RIPE ...
  25. [25]
    IPv4 Exhaustion: RIPE NCC Update
    Feb 3, 2011 · The IANA IPv4 free pool was exhausted today, 3 February 2011. Each of the Regional Internet Registries (RIRs) has now received one of the final ...Missing: date | Show results with:date
  26. [26]
    The Founding of AFRINIC - RIPE NCC
    In April 2005, ICANN recognized AFRINIC as the fifth Regional Internet Registry in the world according to criteria defined in its ICP-2 document (Criteria for ...
  27. [27]
    The RIPE NCC has run out of IPv4 Addresses
    Nov 25, 2019 · Today, at 15:35 (UTC+1) on 25 November 2019, we made our final /22 IPv4 allocation from the last remaining addresses in our available pool.Missing: date | Show results with:date
  28. [28]
    Coronavirus Update - RIPE NCC
    11‑15 May 2020. Will take place as a virtual meeting. -. RIPE NCC General Meeting. 13-15 May 2020. Scheduled with remote participation encouraged. -. ENOG 17. 8 ...
  29. [29]
    RIPE NCC Annual Report 2024
    Apr 2, 2025 · RIPE NCC Annual Report 2024. RIPE-840. Publication date: 02 Apr 2025. State: Published. Author. RIPE NCC. File(s): PDF (8.9 MB).
  30. [30]
    RIPE NCC Charging Scheme 2025
    Sep 5, 2024 · For 2025, the RIPE NCC will introduce an additional fee of EUR 50 per ASN assignment as part of the service fee and as an integral part of the ...
  31. [31]
    [PDF] Activity Plan and Budget 2025 - RIPE NCC
    Dec 31, 2024 · In 2025, we will have three focus points for RPKI. First, continuing ... RPKI and IPv6 deployment, ASNs and much more. We also have a ...
  32. [32]
    IPv4 Address Allocation and Assignment Policies for the ... - RIPE NCC
    Jun 20, 2024 · This document describes the policies for the responsible management of globally unique IPv4 Internet address space in the RIPE NCC service region.Abstract · IPv4 Address Space · Allocations made by the RIPE... · Sub-allocations
  33. [33]
    Request a /24 Allocation via the Waiting List - RIPE NCC
    While we have run out of IPv4 addresses, RIPE NCC members can still request a single /24 allocation (256 addresses). These requests are added to a waiting list ...RIPE NCC IPv4 Pool · Become a RIPE NCC Member · IPv4 Waiting List
  34. [34]
    RIPE Resource Transfer Policies
    Oct 30, 2023 · Any type of Internet number resource can be transferred to or from the RIPE NCC service region. This includes legacy resources, in spite of the ...
  35. [35]
    IPv6 Address Allocation and Assignment Policy - RIPE NCC
    Mar 16, 2020 · This document defines registry policies for the assignment and allocation of globally unique IPv6 addresses to Internet Service Providers (ISPs) and other ...Address space not to be... · Initial allocation · Subsequent allocation · Assignment
  36. [36]
    Autonomous System (AS) Number Assignment Policies - RIPE NCC
    Mar 14, 2017 · This document describes the policies for the assignment of globally unique Autonomous System (AS) Numbers within the RIPE NCC service region.Assignment Criteria · 32-bit AS Numbers
  37. [37]
    RIPE NCC Services for Legacy Internet Resources of RIPE NCC ...
    Oct 18, 2024 · 3.5. The Member shall provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the Legacy Services.Missing: End | Show results with:End
  38. [38]
    Policy Development Process in RIPE
    Jun 27, 2022 · The RIPE PDP is open, transparent, and bottom-up, with four phases: proposal, discussion, review, and concluding, using consensus.
  39. [39]
    Revised IPv6 PI Assignment Policy - RIPE NCC
    Aug 13, 2024 · This proposal aims to reduce the operational burden that operators experience when working with PI. It also clarifies some long-standing issues ...<|separator|>
  40. [40]
    ASN assignment criteria revisited - RIPE NCC
    May 6, 2025 · This policy proposal changes the requirements for ASN assignments. Under the new policy, LIRs and End Users may request a single ASN without justification.Summary of Proposal · Current policy text · New policy text
  41. [41]
    RIPE Database — RIPE Network Coordination Centre
    The RIPE Database contains registration information for networks in the RIPE NCC service region and related contact details.
  42. [42]
    Database Objects
    The RIPE Database contains records of: Allocations and assignments of IP address space (the IP address registry or INR);; Reverse domain registrations;; Routing ...<|separator|>
  43. [43]
    RPSL - Routing Policy Specification Language - RIPE NCC
    RIPE NCC members (LIRs) can attend a one-day hands-on Routing Registry course to learn more about RPSL and the Routing Registry. Course information and ...
  44. [44]
    Using the RIPE Database as an Internet Routing Registry
    Aug 22, 2013 · As an open routing registry, the RIPE Database is available for anyone to use to document their routing policy and information.
  45. [45]
    Serving ROAs as RPSL route[6] Objects from the RIPE Database
    Some of my colleagues at the RIPE NCC have written a “Certification Validator” tool that we used to validate ROA objects coming from the trust anchors published ...<|separator|>
  46. [46]
    Routing Information Service (RIS) - RIPE NCC
    RIS is a routing data collection platform. It collects data on BGP, the protocol by which traffic is routed between networks on the Internet.RIS Peers List · RIS Peering Policy · RIS Data Access
  47. [47]
    RIPE Atlas
    ### Summary of RIPE Atlas
  48. [48]
    [PDF] Gerardo Viviers | 28 October 2024 - RIPE 89
    Oct 28, 2024 · Some RIPE Database objects have an operational impact. • They can affect routing, security, and inter-network operations. • Key objects: route, ...Missing: enhancements | Show results with:enhancements
  49. [49]
    All Documentation Combined | RIPE Database docs
    From August 1992, the newly established RIPE NCC started distributing address space in its service region. Allocations made by the RIPE NCC have always been ...
  50. [50]
    abuse-c Information - RIPE NCC
    We expect to complete setting "abuse-c:" attributes for any remaining members by Q1 of 2014. RIPE members who wish to change their abuse contact email address ...Introduction · Policy Implementation And... · For Allocated (pa) Resource...
  51. [51]
    FAQ | RIPE Database docs
    Jul 17, 2025 · The RIPE NCC supports the operation of the RIPE Database. The maintainers are primarily responsible for the data but the RIPE NCC also has some ...Faq ​ · Why Has My 'as-Name:' Not... · My Update Failed. Please...
  52. [52]
    About RIPE Meetings — RIPE Network Coordination Centre
    A RIPE Meeting takes place over multiple days and brings together Internet service providers, network operators and other interested parties from around the ...
  53. [53]
    RIPE 91
    RIPE 91 took place in Bucharest, Romania from 20 – 24 Oct 2025. RIPE Meetings have brought together Internet service providers, network operators and other ...Programme · Attend · On Site · About
  54. [54]
    Reflecting on the Past Decade of RIPE Meetings
    May 2, 2024 · By examining RIPE Meeting attendance numbers over the past decade, we find that the median number of attendees is around 618, suggesting a ...
  55. [55]
    The RIPE Chair Team Reports - Highlights from RIPE 91 - RIPE Labs
    Oct 31, 2025 · The RIPE Chair Team Reports - Highlights from RIPE 91 · Some highlights · Policy discussions · Feedback · Rob Blokzijl award · Industry events · More ...
  56. [56]
    RIPE NCC Activity Plan and Budget 2023
    Dec 22, 2022 · The RIPE NCC has three decades of experience in offering technical trainings on the RIPE Database, IPv6, BGP and routing security and more.
  57. [57]
    Social Events - RIPE 91
    Oct 20, 2025 · Welcome Reception. When: 19:00-21:00. Where: Foyer Grand Ballroom (Conference Floor) - JW Marriott Bucharest Grand Hotel Entry ...<|control11|><|separator|>
  58. [58]
    Meetings and Events - RIPE NCC
    A RIPE Meeting is a five-day event where Internet Service Providers (ISPs), network operators and other interested parties from all over the world gather.Upcoming RIPE Meetings · Previous RIPE Meetings · Meetings · RIPE 91
  59. [59]
    RIPE NCC Community Projects Fund 2023 Recipients Announced ...
    The RIPE NCC Community Projects Fund opened its call for applications in March 2023. The application period was open for just over 12 weeks and 54 ...
  60. [60]
    RIPE NCC Community Projects Fund
    The RIPE NCC Community Projects Fund was set up to support projects contributing to the operation, resilience and sustainability of the Internet.
  61. [61]
    RIPE Working Groups
    RIPE Working Groups are composed of community members working together to discuss specific topics that are within the scope of the RIPE community.
  62. [62]
    RIPE Policy Development
    The RIPE community develops and sets policies through a long established, open, bottom-up process of discussion and consensus-based decision making.
  63. [63]
    Member Update: October 2025 - RIPE NCC
    Oct 31, 2025 · The full proposal is available. A new version of RIPE policy proposal 2025-01 "ASN assignment criteria revisited" is available for discussion.
  64. [64]
    MAT Working Group - RIPE NCC
    The purpose of the working group is to provide a forum in which the RIPE NCC and the community can collaborate in the areas of data, tools and analysis relating ...
  65. [65]
    List of Country Codes and RIRs - RIPE NCC
    The country names as given in ISO 3166-1. It also shows the five Regional Internet Registry (RIR) service regions serving those countries.
  66. [66]
    IPv4 Address Allocation and Assignment Policies for the ... - RIPE NCC
    Apr 15, 2024 · Its service region incorporates Europe, the Middle East, and Central Asia. The RIPE NCC is responsible for the allocation and assignment of ...
  67. [67]
    CAPIF 4: Advancing Internet Technologies in Central Asia - RIPE Labs
    Sep 18, 2025 · Recent data reveals varying levels of IPv6 adoption across Central Asia and Iran. ... In Uzbekistan, IPv6 adoption was at 0% as of September 2024, ...
  68. [68]
    RIPE NCC Middle East FZ-LLC
    In 2024, we formalised our presence in the Middle East by setting up a separate legal entity in Dubai. Corporate Governance. Find information related to the ...Missing: growth | Show results with:growth
  69. [69]
    UNDP and RIPE NCC Sign MoU to Strengthen Digital Cooperation ...
    Sep 25, 2025 · UNDP and RIPE NCC Sign MoU to Strengthen Digital Cooperation for Sustainable Development. September 25, 2025. Four men in suits signing ...
  70. [70]
    Development of the Regional Internet Registry System
    Dec 2, 2010 · The RIPE NCC published its first regional address distribution policy in July 1992 (RIPE-65). During the following months, European regional ...
  71. [71]
    RIPE NCC to AFRINIC Transition
    AFRINIC began operating as a fully functional RIR for the African region from 21 February 2005. LIRs that were members of the RIPE NCC based in Africa moved to ...Introduction · Resource Requests · Whois Data TransferMissing: expansions APNIC
  72. [72]
    Inter-RIR Transfers - RIPE NCC
    AFRINIC does not currently have an inter-RIR policy. This means that no resources of any kind can be transferred to/from this region. Overview: ...Which Resources Can Be... · How To Submit An Inter-Rir... · RpkiMissing: expansions | Show results with:expansions
  73. [73]
    [PDF] RIPE NCC Charging Scheme 2012
    For the 2012 Charging Scheme, the RIPE NCC proposes that no fees will be charged for the work involved in assigning and allocating IPv6 Internet number ...Missing: flat structure
  74. [74]
    RIPE NCC Financial Report 2024
    RIPE NCC Financial Report 2024. RIPE-841. Publication date: 02 Apr 2025. State: Published. Author. RIPE NCC. File(s): PDF (4.5 MB).
  75. [75]
    IPv4 Transfers in the RIPE NCC Service Region
    May 6, 2015 · For each transfer, we determined the originating and receiving country by locating the transferred block in the RIPE NCC delegation statistics ...Missing: 2017 | Show results with:2017
  76. [76]
    Transfer of IP Addresses and AS Numbers - RIPE NCC
    We authorise and facilitate transfers of Internet number resources, such as IPv4, IPv6 addresses and AS Numbers. A resource transfer changes the holdership ...Missing: regulations assessment anti- speculation rules
  77. [77]
    RIPE NCC 2024 Reports Reveal Strategic Insights for IPv4 Market ...
    May 6, 2025 · The financial report's €35.7M realized income[4] against €38M budget underscores the need for innovative monetization. Five actionable ...
  78. [78]
    2025 IPv4 Price Trends and 2026 Predictions - CircleID
    Sep 11, 2025 · Through 2024, IPv4 leasing stayed steady at about $0.50 per IP per month, even as purchase prices diverged by block size.
  79. [79]
    Alignment of Transfer Requirements for IPv4 Allocations - RIPE NCC
    Feb 11, 2015 · The goal of this policy proposal is to prevent speculating organisations from abusing the IPv4 transfer policy to make a financial profit.Impact Analysis · B. Impact Of Policy On... · C. Impact Of Policy On Ripe...Missing: anti- rules<|separator|>
  80. [80]
    [PDF] rir comparative policy overview - The Number Resource Organization
    Jul 1, 2025 · IPv4: At least a /22 used in region. • IPv6: At least a /44 used in region. • ASN: At least one ASn present on one more peering session and/or ...<|control11|><|separator|>
  81. [81]
    New Report Published: The State of IPv4 and the Evolving Transfer ...
    Jun 9, 2025 · The RIPE NCC has three decades of experience in offering technical trainings on the RIPE Database, IPv6, BGP and routing security and more.
  82. [82]
    History of the Regional Internet Registries - APNIC
    Today, there are five RIRs – APNIC, ARIN, RIPE NCC, LACNIC, and AFRINIC. Regional Internet Registries. With the active support of their respective communities, ...Missing: transfers | Show results with:transfers
  83. [83]
    About LACNIC
    LACNIC, the Internet Address Registry for Latin America and the Caribbean, manages IPv4 / IPv6 addresses and ASNs using the policy development process ...Missing: 2025 | Show results with:2025
  84. [84]
    About the NRO | The Number Resource Organization
    Feb 16, 2024 · The RIRs manage the distribution of Internet number resources (IP address space and Autonomous System Numbers) within their respective regions.
  85. [85]
    Welcome to RIPE and the RIPE NCC — RIPE Network Coordination ...
    The RIPE NCC is one of five Regional Internet Registries (RIRs) providing Internet resource allocation and registration, and coordination activities.About Us · RIPE Database Query · What We Do · RIPE Database
  86. [86]
    APNIC membership hits 10000
    Apr 11, 2024 · Of APNIC's 10,000 Members, 6,350 are service providers and the remaining 3,650 are end-user organizations. Direct membership by end-user ...Apnic By Economies: The Ldcs · Resource Distribution · Ip Resources
  87. [87]
    Membership - American Registry for Internet Numbers - ARIN
    There are three types of ARIN Members: Service Members, General Members, and Trustee Members. Each membership status is based on certain eligibility ...Overview · General Membership Benefits
  88. [88]
    AFRINIC Service Region
    AFRINIC Service Region ; EASTERN REGION, WESTERN REGION, CENTRAL AFRICA, NORTHERN AFRICA, SOUTHERN AFRICA ; Burundi, Benin, Cameroon, Algeria, Angola ; Djibouti ...
  89. [89]
    Communiqué from the AFRINIC Board of Directors and the Receiver
    Oct 13, 2025 · The Board is currently reviewing matters related to IP resource allocations and the rights of all Resource Members who have joined AFRINIC since ...
  90. [90]
    About the ASO | The Address Supporting Organization (ASO ICANN)
    Jan 3, 2025 · The ASO's purpose is to review and develop recommendations on Internet Protocol (IP) address policy and to advise the ICANN Board on policy issues.
  91. [91]
    History of the NRO | The Number Resource Organization
    Jul 11, 2018 · On 24 October 2003, the four existing RIRs – APNIC, ARIN, LACNIC, and RIPE NCC – entered into a Memorandum of Understanding (MoU) to form the ...
  92. [92]
    GDPR and the RIPE NCC
    An introduction to the RIPE NCC's preparation for the EU General Data Protection Regulation that comes into effect on 25 May 2018.
  93. [93]
    [PDF] The NRO & Resource Certification (RPKI)
    While standards for Resource Certification and RPKI are now well established, additional standards work is underway ... • RIPE NCC: www.ripe.net/certification.
  94. [94]
    RPKI Best Practices and Lessons Learned - ARIN
    Sep 25, 2025 · NRO RPKI Program Manager Sofía Silva Berenguer shares Resource Public Key Infrastructure best practices and lessons learned drawn from ...
  95. [95]
    Multi-stakeholder Engagement - Internet Governance - RIPE NCC
    The RIPE NCC is committed to engaging with a wide range of governments and related global institutions with an interest in the development of the Internet.Missing: advocacy | Show results with:advocacy
  96. [96]
    IGF - Internet Governance - RIPE NCC
    These contributions have included organising workshops, speaking on panels and contributing to discussions on a range of Internet governance topics. Further ...
  97. [97]
    RIPE NCC at the IGF 2025
    Jun 20, 2025 · The RIPE NCC team is heading to the 2025 Internet Governance Forum (IGF), which will take place in Lillestrøm, Norway from 23 until 27 June.
  98. [98]
    RIPE NCC Contributions to External Consultations
    Responses to consultations and proposals led by different governmental and intergovernmental organisations that are involved in Internet governance.
  99. [99]
    [PDF] RIPE NCC Response to the Cyber resilience act
    Jan 23, 2023 · The RIPE NCC welcomes the European Commission's efforts to further harmonise and improve cybersecurity in the Europe Union by setting essential ...Missing: collaborations | Show results with:collaborations
  100. [100]
    Recent Changes to Legal Framework - RIPE NCC
    Oct 20, 2025 · Most of these changes are in response to the EU regulation Digital Operational Resilience Act (DORA) which came into effect in January 2025.
  101. [101]
    Building Resilience: The RIPE NCC's Draft Activity Plan and Budget ...
    Oct 16, 2024 · The Draft Activity Plan and Budget 2025 outlines the RIPE NCC's plans for the coming year, along with the associated costs to achieve them.