This article summarises the third RIPEstat demo session that took place today, 22 March 2011. At the end of the article you can find the date of the next demo, and options for providing feedback.
In a previous article we measured that a large percentage of 6to4 connections fail. In this article we show our attempts to find out why these connections fail.
We have redesigned and improved the way we mirror other databases. We now have a method of translating the operational data from other registries (for instance from other Regional Internet Registries or the RADb) into the RIPE Database structure.
In order to ensure accurate and up to date registration data, the RIPE NCC started the Registry Data Quality project in 2009. The article below describes this activity and the problems we found and how we fixed them.
This article, prompted by a panel discussion at the RIPE 61 Meeting, describes the most significant implications of network complexity and suggests ways to deal with it. This is a topic that requires more work and a lot of input from network operators. We hope you’ll work with us to advance this subject.
Caidagram is a tool developed at CAIDA (the Cooperative Association for Internet Data Analysis). It allows the user to visualise geographically-based measurements about the Internet, focusing on trends and variations over time.
This article summarises the second RIPEstat demo session that took place today, 22 February 2011.
We partnered with several Regional Internet Registries (RIRs), including the RIPE NCC, to examine what traffic is going to unallocated IP address ranges. In this particular case, we looked at traffic going to 5/8 and 37/8.
Last year, in a series of two articles, we presented statistics on the number of RIPE NCC members and the resources distributed to our members. With twelve months passed, we revisit the topic and look at how things evolved in 2010.
When we started developing the RIPE Database API and the accompanying RESTful web services, we first implemented the "Read" service. The RESTful web services now also support Create, Update and Delete functionalities. Not only did we implement these methods, but we also introduced some workflow refinements that should make programmatic interaction with the RIPE Database much easier, taking away some of the common aches of the way the legacy "Mail" and "Sync" update interfaces work.