Based in Amsterdam, The Netherlands
Articles
Likes on articles
I joined RIPE NCC in May 2013. Since then I am working as Project Coordinator in the Measurements Community Building Team. Occasionally I write articles for RIPE Labs or I contribute to them.
• 8 min read
The peering strategy for RIS has traditionally been an open one, geared towards maximising the number of peers. But over the past couple of years we've been working with a more selective approach that reduces redundancy and cost, while also helping make sure RIS provides a diverse view of global ro…
• 8 min read
Our work on improving the user interfaces for our services continues. And as always, we're keen to find out what you think. In this article, we look over the recent feedback users have shared with us and how we're working to transform their suggestions into tangible improvements.
• 3 min read
Expanding the RIPE NCC Authoritative DNS Service means cooperating with the community to find organisations out there willing to host AuthDNS instances on their networks. In this article, find out exactly what's required from hosts and how to apply.
• 7 min read
The pilot we ran to assess the feasibility of involving virtual machines in the pool of RIPE Atlas anchors is complete and the results are good.
• 4 min read
The wait for the next generation of RIPE Atlas anchors is at an end. The RIPE NCC is ready to start approving applications for the new RIPE Atlas v3 anchors...although at a steady pace to start.
• 4 min read
With the v2 RIPE Atlas anchors no longer in production, we're busy looking at new hardware options. Here's the story so far.
• 4 min read
The RIPE NCC is pleased to announce that we will be sponsoring 15 new RIPE Atlas anchors in 2017. This article provides details about the campaign and introduces the criteria that will be used to decide which applicants will receive sponsorship.
• 5 min read
Four years have passed since the RIPE NCC announced its plans to put RIPE Atlas anchors into production. Since the first anchors went online in 2013, we’ve been working hard to both maintain and expand the network. As a result, we currently have 238 anchors deployed across 66 countries!
“Thank you for this report. I have a couple of questions: Have you tested the impact of VM performance on measurements? In particular have you implemented performance reporting that would allow us to detect if measurements are impacted by VM performance problems? Are there draft requirements for anchor VMs and do they consider VM performance? As you mention scaling the back-end and support infrastructure may become a problem if the investment of the host becomes very low. Have you considered asking the hosts of VM anchors to contribute to these costs? Daniel”
Hi Daniel, I’ll respond to each of your questions in turn. No, we haven't tested the impact of VM performance on measurements and have no plans to do any performance reporting. However, if more people are interested in it we might include this in our planning. What we did do was compare the measurement results between a physical and virtual anchor both hosted in the same location. We didn’t see any significant differences. You can read more in this article on RIPE Labs: https://labs.ripe.net/Members/stephen_strowes/comparing-virtual-and-metal-ripe-atlas-anchors There are draft requirements that were given to the volunteers in the pilot. As it might be interesting for everyone to see these, we have added them to the end of this article as an addendum. As you can see, they do not consider VM performance but they are based on the requirements of the hardware anchors. Yes, we are talking about possible contributions. It is not new to ask contributions to RIPE Atlas users when they become more involved in the usage of our system (but this is independent from the anchor being a VM or the Hardware version). Thank you for your questions!
Showing 1 comment(s)