Modalità di lettura

Discovery of IPv6 Router Addresses Using Subnet-Router Anycast

Brute-force IPv6 scanning doesn't scale, and ICMPv6 rate limiting can undermine topology measurements. Maynard Koch and colleagues show how Subnet-Router Anycast (SRA) probing discovers more router addresses, delivers more stable results, and expands the IPv6 measurement toolbox.
  •  

What We Learned from a Multi-Service Vulnerability Disclosure

A series of vulnerabilities reported through the RIPE NCC bug bounty programme revealed weaknesses across multiple services and highlighted the risks posed by vulnerability chains. We look at how the issues were addressed, and what the disclosure taught us about handling complex security reports that span teams and systems.
  •  

Sustaining the Commons in an Age of Digital Sovereignty

Digital sovereignty raises legitimate questions about dependency, resilience and control. It can strengthen the Internet when it builds capacity and meaningful choice. It becomes risky when it is pursued as control over the common layer that keeps the global Internet interoperable.
  •  

RIPE 92 Daily Meeting Blog

Sixty-one RIPE Meetings on, RIPE 92 brings us back to Edinburgh - city of festivals, gothic skylines, and uphill walking. As always, there's the slides, there's the videos, but to get a real feel for what's happening through the week, tune into the daily meeting blog.
  •  

Legacy Out of Contract

Last time, we looked at legacy address space in terms of contract coverage, ROA coverage, and proportion of announced prefixes. Now it’s time to take a closer look at those blocks still to be brought under contract and get a clearer picture of what kind of behaviour we see coming from them.
  •  

Operational Review of Public ENUM Under e164.arpa

A 2026 operational review of Public ENUM under e164.arpa found that half of the current delegations show some form of DNS problem. The findings are expected to be discussed at RIPE 92, including the operational status and future support of Public ENUM under e164.arpa.
  •  

The RIPE Chair Team Reports - May 2026

The RIPE Chair Team reports on what to expect at RIPE 92, including the main programme and parallel events, WG chair selections and support for newcomers, as well as highlights from recent industry events.
  •  

PeeringDB Update October 2025 - April 2026

PeeringDB is a widely used resource for interconnection data, and in these regular updates, we help users keep track of how the platform evolves. This report summarises significant PeeringDB changes over the last six months.
  •  

Questioning the IPv8 Proposal

The IPv8 proposal brings together routing, identity, and network management into a single design, but does it leave too many operational questions unanswered?
  •  

Making Resource Holders Easier to Identify: Introducing reg-nr: in the RIPE Database

Proposed at RIPE 91 in the Address Policy Working Group and then further discussed in the Database Working Group, the reg-nr: attribute (NWI-21) has already been implemented ahead of RIPE 92, showing how quickly community input can lead to practical results. It adds official company registration numbers to organisation objects co-maintained by the RIPE NCC. This helps clearly identify organisations, especially when names are similar or identical.
  •  

The Internet’s New Builders

Content and cloud platforms are no longer just the largest customers of global connectivity. They are increasingly financing and building the infrastructure itself, from submarine systems to edge and data center footprints.
  •  

ADoX Deployment in the Wild

Encryption between DNS resolvers and users is growing - but what about the next hop? We measure the real-world deployment of encrypted resolver-to-authoritative DNS (ADoX), finding limited, highly concentrated adoption and little support among resolvers.
  •  

Understanding DDoS Scrubbing in BGP: Five Leading Scrubbers

DDoS mitigation often relies on BGP for "scrubbing", but how this appears in routing data is not well understood. We analyse five major providers to distinguish between always-on and on-demand protection, showing how mitigation manifests in practice and what it means for routing visibility and RPKI.
  •  
❌