Based in Amsterdam
Articles
Likes on articles
Hailing from a research background in philosophy, linguistics and computer science, I came to the RIPE NCC back in 2016 and took on the role of RIPE Labs Editor in 2020.
The RIPE NCC's 2017 campaign to sponsor fifteen RIPE Atlas anchors has come to an end. Find out where the latest batch of sponsored anchors are located and learn more about some of the developments that took place in the last leg of the campaign.
In August 2017, just short of seven years after RIPE Atlas was launched, the number of connected RIPE Atlas probes hit 10,000. That’s a lot of probes and it marks a big moment for the RIPE Atlas project.
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.
With the v2 RIPE Atlas anchors no longer in production, we're busy looking at new hardware options. Here's the story so far.
Ever since the RIPE Atlas anchor network went online, the RIPE NCC has been scheduling anchoring measurements to provide a clear overview of the health of the network. Over time, however, a certain imbalance has crept into such measurements. Here's a look at the problem along with our solution.
The second phase of the RIPE NCC’s campaign to sponsor 15 RIPE Atlas anchors has been completed, with another five anchor hosts selected for sponsorship. We want to tell you about the new anchor hosts and also take a look at some related developments here at the RIPE NCC.
The RIPE NCC launched its campaign to sponsor fifteen new RIPE Atlas anchors in January. We're glad to announce that we've now selected the first five candidates who'll benefit from the campaign!
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.
The RIPE NCC's fifth hackathon event will happen in Amsterdam, in April 2017. We would like to invite operators, designers, researchers and developers to take on the challenge and join us in developing new tools and visualisations for DNS measurements.
“great podcast! is there a way to get a subtitles?”
Thanks Maxim! And good suggestion - we have been looking into ways to do this. Watch this space!
“Hi, first Link on this page (https://atlas.ripe.net/docs/software-probe/) is broken.”
Thanks Jan - that's due to the recent update of the RIPE Atlas documentation. Fixed now!
“Hi. Could you please share sample articles so that we get better idea on what is the expectation of one”
Hi Sankalp - no problem. All the articles that have been submitted so far can be viewed on the main competition page: https://labs.ripe.net/competitions/the-ripe-labs-article-competition/
“Has RIPE considered removing the routing information for Russian IP space - cutting Russia off from the internet at large?”
Hi Alexis - here's a link to a statement the RIPE NCC Executive Board published yesterday: https://www.ripe.net/publications/news/announcements/ripe-ncc-executive-board-resolution-on-provision-of-critical-services
Interested readers might want to take a look at the follow-up discussion currently taking place on the RIPE NCC Services Group Mailing List: https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2021-May/thread.html
“When I and my journalistic colleague, Jan Vermeulen of MyBroaddband.co.za began our investigations into this colossal and truly epic malfeasance and theft of valuable IPv4 resources in mid 2019, the notion of either of us becoming famous or of receiving any credit for unraveling and publicly documenting this gigantic scandal was not what motivated us, nor has it been, since the beginning. Rather, we merely wished to right some wrongs and return to the people of Africa some IP resources critically needed for the ongoing development of the Internet in Africa. Nonetheless, it would have been, I think, at least minimally respectful if either AFRINIC or (now) RIPE had taken a moment to at least mention our names and our very evident, abundant, and key contributions towards exposing this whole huge mess. Neither organization, it seems, has thus far elected to do so publicly. Such is the reward, or lack thereof, of a job well done.”
Sorry for the oversight. I've updated the article with some additional information and a link so readers can find out more about how the news emerged.
“The link to the full AFRINIC whois audit report is not working.”
Thanks Wessel! Should be working for everyone now.
“small (almost rhetorical but not really) question. do you assume these outages were created manually on request of state regulator?”
As we say, our purpose here is really to see what our data has to tell us about the scale and impact of the outages. Nothing in the data we've been looking at determines what caused the outages.
“Any info about traffic packet loss from probes?”
Good question. Arriving at a proper answer to this would require looking at all measurements from all probes for the past four days to find out if any observed packet losses is related to the outage or to other issues in the path to the destination. From a first peek at one probe that disconnected for two days and came back, it seems that (some/all?) IPv4 pings did make it through all the time. IPv6 on the other hand had 100% packet loss. See: https://atlas.ripe.net/probes/25114/#tab-builtins
“A small correction - population is 9,5 mil. people”
Fixed. Thank you!
Showing 23 comment(s)