During the RIPE 70 Meeting in Amsterdam this week (on 13 May around 10:00 UTC), we experienced a network outage at AMS-IX. Let's see how this was monitored by various tools.
We introduce a new tool to read BGP RIB dump files, called BGPdump2. It has a unique feature, in which users can compare routes from BGP RIB files in the ”diff”-like display format. It is good for checking the correctness of BGP operation by comparing one ISP’s BGP routing table to another ISP’s.
In 2013 and 2014 we looked into measuring Interdomain Routing in Africa using the RIPE Atlas infrastructure. This resulted in a paper published at the PAM (Passive and Active Measurement) 2015 conference. Here we present some highlights of this research.
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.
At the RIPE 69 meeting, the use of the RIPE Database as an Internet Routing Registry (IRR) and it's relationship with other IRRs was raised. But there hasn't been much discussion on options for the way forward since. Based on what was said at RIPE 69 and the few comments made on the mailing list, I feel that some issues might need further clarification and discussion.
We looked at Internet measurements for the South East Europe (SEE) region in order to share these with attendees at the SEE 4 Meeting that took place from 21-22 April 2015 in Belgrade, Serbia. This is the long version of the lightning talk Vesna Manojlovic gave at SEE 4.
We're getting ready to expand K-root coverage, and we'll soon be inviting interested members of the community to express their interest in hosting their own K-root node. Learn more about how we propose expanding the network, what the requirements are for hosting your own K-root node, and the projected timeline.
When re-designing www.ripe.net, we paid extra attention to how we can improve the interface for the Policy Development Process (PDP). This open and transparent process determines RIPE Policies, which govern the distribution and use of nearly all Internet resources in the RIPE NCC service region. Our aim was to make it easier to review policies and proposals and encourage participation in policy discussions. This post explains these improvements in more detail.
In March 2015, a diverse group of contributors got together to come up with creative ways to visualise the health of the Internet using RIPE Atlas open measurements data. It was the first RIPE Atlas hackathon. Impressive results were hacked together by programmers, designers and operators during an intensive weekend of work and fun in Amsterdam. In this article we celebrate hackathon achievements, document and promote hackathon results, create a memento for participants and report in detail for the benefit of the rest of the community.
This article is the third in a series that explains the main changes we're making to the RIPE NCC website as part of the website redesign project. Now that we're just a few days away from the launch on 13 April, we wanted to give you a sneak peek of the new visual design, and explain some of the back-end changes we made in order to support it.