Alun Davies
Based in Amsterdam
52
Articles
2023
Likes on articles
Based in Amsterdam
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.
operational
internet number resources
dns
routing
security
rpki
ipv6
measurements
atlas
ripestat
tools
geolocation
ris
statistics
governance
policy
privacy
country
sustainability
research
community
diversity
events
hackathons
nogs
ripe
podcast
production
prototype
bgp
regulations
outages
internet infrastructure
open source
Does the Internet Route Around Damage? - Baltic Sea Cable Cuts
• 10 min read
This week's Internet cable cuts in the Baltic Sea have been widely reported, even as attempts to understand their cause and impact continue. We turn to RIPE Atlas to provide a preliminary analysis of these events and ask to what extent the Internet in the region has been resilient to them.
10 Years of Legacy Policy
• 9 min read
10 years ago, consensus was reached on the legacy policy. In this article, we report on the current status of legacy address space administered by the RIPE NCC and a look at what's changed over the past decade.
Shane Kerr: Approaching the RIPE Gender Data Gap
• 2 min read
After the Women in Tech session at RIPE 84, Anastasiya Pak caught up with Shane Kerr to hear more about measuring the gender gap at RIPE Meetings. In this episode of the RIPE Labs podcast, hear about the goals and challenges in approaching the RIPE gender data gap.
Rolling Out the RIPE Atlas Redesign
• 6 min read
You may have noticed that, as of this past week, RIPE Atlas is looking different. To explain what's changed and why, here's a quick update on our latest efforts in rolling out the new design we've been working on for our services.
IGF 2018 Liveblog
• 29 min read
The 13th annual meeting of the Internet Governance Forum (IGF) runs from 12-14 November 2018 in Paris. The RIPE NCC staff at the event will be liveblogging key moments and session take-aways. Check back on this page for regular updates on the issues, arguments and ideas from RIPE NCC staff and RIPE…
Outcome of the RIPE Atlas Anchor VMs Pilot
• 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.
The Avans Academy - Top of the Class in IPv6 Usage in the Netherlands
• 8 min read
Together with SURFnet we met with Harold van Ham and David Schrok, both active in the IPv6 team at the University of Applied Sciences in Breda and talked to them about the steps they took to deploy IPv6 in their network.
Showing 7 article(s)
I'm sorry to see that the tone of the article has infuriated some of our readers. Speaking for RIPE Labs, our only goal is to give people in the community a space where they can express views on community-relevant topics. That's important to us - but we do understand that there will sometimes be disagreement and debate over the views expressed. We would of course be equally happy to publish an article making a positive case for the use of personal ASNs.
“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
Showing 24 comment(s)