Digital sovereignty is not simply good or bad. The commons test offers a practical framework for assessing whether different strategies expand choice, preserve interoperability, strengthen resilience and support meaningful participation, or create new dependencies and chokepoints.

IPv6-only networks often still depend on IPv4 subnets and ARP. This article introduces an IETF proposal to eliminate both, allowing IPv4 to operate as a service over IPv6-only infrastructure without translation or tunnelling.

The RIPE Chair Team rounds up the latest developments across the community, from RIPE 93 preparations and policy work to governance updates and community activities.

The IETF 126 Vienna meeting takes place 18–24 July 2026. As at every IETF meeting, alongside the established Working Groups there will be a handful of Birds-of-a-Feather (BoF) sessions - and these are often the most interesting place to watch where Internet standards work is heading next.

Why do live sports, ticket sales, and public service launches sometimes resemble DDoS attacks? This article explores how synchronised user behaviour turns Internet traffic into a physical phenomenon that places real pressure on network infrastructure.

On 3-4 June 2026, we convened in Riga, Latvia for RIPE NCC Days Baltics. 76 participants from nine countries participated in sessions covering important topics in network operations, with a special focus on resilience for a region that has seen repeated network disruptions in recent years.

Three local hubs at RIPE 92 brought people together to participate in the meeting remotely. We look at what organisers in Bulgaria, Türkiye and Poland learned about bringing the RIPE Meeting experience closer to home.

ASPA objects can be registered today with ARIN and RIPE NCC. Validators support RTR v2. But if you're an operator, can you actually see what ASPA is doing - or would do - on your network? We built a tool to find out.