❌

Modalità di lettura

Restricting the Acquisition of Additional LIR Accounts

The RIPE NCC Executive Board has decided to temporarily restrict members' ability to acquire additional Local Internet Registry (LIR) accounts. Taking effect on Tuesday, 29 September, the restriction also covers requests already in progress. The decision is a first step towards addressing the administrative burden of multiple accounts, while allowing related questions about IPv4 allocations from the IPv4 Waiting List to be discussed within the RIPE community.
  •  

PeeringDB Update April - September 2026

The last six months has seen important improvements to PeeringDB. We've added in page maps for searches of interconnection facilities and improved the data quality for AS-SET names.
  •  

Moving to a New Board Structure

A governance structure is strongest when the responsibilities written down on paper match the responsibilities exercised in practice. This proposal to change the RIPE NCC’s governance structure is intended to make sure that they do.
  •  

The /3 Body Problem

A large chunk of IPv6 is heading for space, and every policy question about it is currently going to be deferred to the RIR communities. This article outlines what those questions look like, and argues why now is the time to start asking them.
  •  

The Internet’s New Edge Builders

After building private backbones, content and cloud platforms are now moving closer to users. In doing so, they are taking on delivery roles once associated mainly with independent CDNs.
  •  

The IRR Landscape: What RPKI Can Replace

In the third part of our IRR landscape series, we use traffic measurements from AMS-IX and DE-CIX to assess which parts of the IRR landscape can safely be replaced with RPKI. Third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain essential for BGP filter generation.
  •  
❌