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.
Learn more about the RIPE Atlas active measurements network.
You can also find a collection of use cases, reviews and other articles written by RIPE Atlas users.
With the MENOG 15 meeting taking place this week, we look at Internet measurements and statistics for countries in the MENOG region.
There was a power outage last week in the north of The Netherlands, a country with a very high density of RIPE Atlas probes. This density provides us with some interesting data and visualisation.
We've been working with various Internet Exchange Points (IXPs) over the last few months to see how RIPE Atlas active measurements can provide insight into how they are keeping local traffic local. This could help to improve performance and efficiency for IXPs and their members. To explore this we've created a set of python scripts to analyse Internet traffic paths between RIPE Atlas probes in a given country, and see if we can identify if they traverse IXPs.
We visualised the measurements collected by our RIPE Atlas anchor. This allows us to analyse the quality of our connectivity and topology changes and to help debugging network issues. This monitoring page is publicly available.
The RIPE NCC's Chief Information Officer, Kaveh Ranjbar, gives an update on the state of our technical services and tools, and gives readers a heads up about what they can expect in 2015.
While the cyclone Pam is battering the South Pacific, we're monitoring how this affects Vanuatu.
The increasing number of middleboxes (such as firewalls, NATs, proxies, or Deep Packet Inspection) has raised concerns over the impact of such middleboxes on the network and the possibility to innovate. As a result, operators and researchers are studying the distribution and behaviour of middleboxes in large networks. In this article, we will describe a tool called Tracebox that helps in detecting middleboxes. Tracebox was developed at the Université Catholique de Louvain (UCL) and at university of Liège (ULg) in 2013 and funded by Change (INFSO-ICT-257422), mPlane (ICT-318627), and Bestcom IAP. We believe that adding tracebox-like capabilities to RIPE Atlas could give network operators a deeper insight into their systems and help debugging network problems.
Microsoft ended support for Windows XP as of April 2014. We're about to change RIPE Atlas and RIPEstat to stop support for Internet Explorer 8 running on these systems.
This article describes how RIPE Atlas probes and anchors maintain their clocks, and how accurate these clocks are. We also plan to make the NTP measurements we describe here available as an additional measurement type for RIPE Atlas users.
This article shows some prototypes of visualising network outages with RIPE Atlas using CartoDB.
While at this point it is still unclear what exactly happened at Facebook this morning (27 January), we collect data on the Internet control plane (BGP) and data plane that allows us to provide some insight into what happened with Facebook's connectivity to the rest of the Internet.
We're pleased to announce a major milestone in the RIPE Atlas anchors project: the 100th anchor is now online!
As the RIPE Atlas network continues to grow, it's useful for ambassadors and potential probes hosts to easily see where we already have probes deployed and where we'd like more probes installed. We created a few useful maps to help with this.
Calling all developers, designers, network operators, computer science students, and open data enthusiasts - the RIPE NCC is hosting a RIPE Atlas data visualisation hackathon in March 2015, and we want you!
RIPE Atlas data is now available as a live data stream, opening the door to a host of new applications and use cases. Learn more about how this powerful new functionality can benefit your network.
We used RIPE Atlas to measure latency times to K-root, and we believe we can improve those times by adding new nodes to K-root in strategic locations. Here, we propose the idea of developing an experiment that would let us measure this potential improvement.
We're very excited to announce an all-new user interface (UI) for RIPE Atlas measurements. Users can now schedule, monitor and manage their own customised measurements more efficiently than ever before, and can now make use of the tagging feature when selecting probes for use in those measurements. Learn more about the new features below, explore the new interface, and let us know what you think.
During its meeting in September, the RIPE NCC presented the RIPE NCC Executive Board with a value proposition document detailing the value that RIPE Atlas can bring to network operators, researchers and the Internet community as a whole. The board asked the RIPE NCC to publish this document, which we have done here. We also plan to incorporate much of its content into the RIPE Atlas website so that RIPE Atlas users can clearly understand the different ways this global Internet measurement network can be used and the many unique benefits it provides.
Under ARIN's Number Resource Policy Manual (NRPM) Section 4.10, the IPv4 address block 23.128/10 is reserved for allocations and assignments dedicated to facilitate IPv6 deployment. The maximum allocation size is a /24; the minimum allocation size is a /28. There has been much discussion on the NANOG mailing list about the usability/routability of prefixes longer than a /24. In order to try to provide some additional data on this topic, the RIPE NCC has requested a small block of address space from the reserved /10 to test these types of prefixes.