RIPEstat has a new widget: Geolocation History. Geolocation History provides information about the physical location of address space over time. This article describes the features of the widget, and explains how the results can be interpreted.
The RIPE NCC is proud to introduce the IP Analyser. This is a brand new service accessible through the LIR Portal that gives our members an insight into their IPv4 and IPv6 allocations and assignments. The ultimate goal is to offer a complete overview of all the IP resources you hold, and inform you about everything related to them.
We're about to change RIPE Atlas to use RIPE NCC Access, a system which enables single sign on for RIPE NCC services for authentication. Some of the details are described below.
This article is based on a lightning talk Matthew Luckie of CAIDA presented at the recent NANOG 54 meeting of work done in conjunction with Amogh Dhamdhere and Bradley Huffaker. The article is structured around a number of hypotheses about the state of IPv6 deployment and the IPv6 capability of networks. In order to verify these hypotheses, the authors looked at various data sets. The full slide set can bee seen on the NANOG 54 web site.
One year after we released the interactive graph to show the percentage of ASes announcing IPv6 prefixes, we looked at the progress made since then.
RIPE NCC Access, a system which enables single sign on for RIPE NCC services, has been enabled in RIPEstat. The introduction of RIPE NCC Access allows us to offer more functionality tailored to your preferences.
In the last RIPEstat demo, we announced the introduction of a new module, ASN Neighbours, which was only available via the data API. Today we released the module as a widget, which is also included on the RIPEstat webpage. In this article we'll explain how to interpret the results displayed by the widget.
The amount of members requesting a Resource Certificate is steadily climbing, soon reaching 900. What is even more impressive is the amount of routing information these LIRs have entered in the system by creating Route Origin Authorisations (ROAs). But what is the quality of the data and is it used by anyone?
In this article we provide some analysis on the updates received by the RIPE Database during 2011 and in the first two months of 2012.
On Monday, 20 February, we discovered that the application servers belonging to the labs.ripe.net production cluster were compromised over the weekend. We investigated this and found no evidence that any harm was done to the servers.