In February 2011 the RIPE NCC implemented the "pingable:" and "ping-hdl:" attributes in the RIPE Database. These attributes were added to the Routing Policy Specification Language by RFC 5943 to allow networks to advertise IP addresses that are reachable and can be used as a target for diagnostic tests. Five years later we check how the new attributes have been adopted and how reachable the pingable addresses registered in the RIPE Database are when pinged from RIPE Atlas.
Pages created by Rene Wilhelm
In the course of 2015 we have expanded the K-root anycast cluster with 17 hosted servers in 15 new cities. We look at RIPE Atlas to see what impact this had on performance on both global and regional scales.
We look at the RIPE NCC in terms of growth, geographic distribution and IPv6 deployment. We find that recent RIPE policy changes have had an impact on membership statistics and development trends.
In September 2012 the RIPE NCC reached its last /8 of available IPv4 addresses. This activated a new phase in the RIPE IPv4 policies, with each LIR now eligible to receive one final /22 allocation. In this article we look at developments in IPv4 allocations and remaining addresses at the RIPE NCC in the three years since then.
Now that the RIPE NCC has reached its last /8, some Local Internet Registries (LIRs) are choosing to obtain additional address space from other organisations via the emerging transfer market. Here we examine statistics from the last two and a half years of transfers and visualise per country aggregates on a map.