Based in Amsterdam, NL
Articles
Likes on articles
I'm a data scientist at the RIPE NCC. I'm a chemist by training, but have been working since 1998 on Internet related things, as a sysadmin, security consultant, web developer and researcher. I am interested in technology changes (like IPv6 deployment), Internet measurement, data analysis, data visualisation, sustainability and security. I'd like to bring research and operations closer together, ie. do research that is operationally relevant. When I'm not working I like to make music (electric guitar, bass and drums), do sports (swimming, (inline) skating, bouldering, soccer), and try to be a good parent.
• 7 min read
Following on from last year's during World IPv6 Day, we again looked at relative performance of IPv4 and IPv6 from the measurements we conducted. In this article we describe the methodology and the show the results of these measurements.
• 3 min read
With the introduction of a new firmware version for RIPE Atlas probes, the structure of the measurement results will be changing. Anyone making use of the raw results is advised to read about these upcoming changes and to subscribe to our RSS feed or subscribe to our mailing list to be notified of …
• 3 min read
Similar to last years World IPv6 Day, this year, the RIPE NCC is measuring selected World IPv6 Launch participants from over 50 vantage points all over the world. We're measuring DNS, ping, traceroute and HTTP and show results at http://ipv6launch.ripe.net/ .
• 7 min read
We developed a script to measure IPv6 capabilities of DNS resolvers and clients two years ago. Recently we found some interesting trends in IPv6 capable DNS infrastructure.
• 3 min read
As a follow-up to the previous article and prompted by a question in the mailing list, we looked into connectivity of one particular instance of K-root: the one located in Delhi. India.
• 5 min read
With the depletion of the IPv4 free pool in the APNIC region and the imminent IPv4 free pool run out in the RIPE NCC's service region, it is interesting to look at IPv4 allocation rates per country to see where free pool run out has and will have the most consequences, in terms of curtailing growth…
• 5 min read
The prefix 128.0/16 is filtered in Juniper devices up to and including JUNOS software version 11.1. We looked at three ways to get a rough estimate on how much filtering of 128.0/16 is going on on the Internet.
• 5 min read
Often when looking at IPv6 deployment statistics, the size of the organisation or the network is not taken into account. In this article, we look at IPv6 deployment of Local Internet Registries (LIRs) per country in correlation with the size of the LIR.
• 16 min read
In this article we look at two "Happy Eyeballs" implementations, that aim to reduce degraded user experience as the result of broken dual-stack configurations. We call this degraded user experience "Unhappy Eyeballs". The Chrome web browser implementation seems to succeed in this aim, while Apple's…
• 4 min read
This weekend the NANOG mailing list was abuzz about an F-root IPv6 route leak, that resulted in the F-root DNS server instance located in Bejing, China, being queried from outside of China. This normally doesn't happen, as this instance is advertised with the BGP attribute NO_EXPORT, which means it…
• 4 min read
Following the Facebook outage that took place on 4 October, we saw people looking to BGPlay to get a better view of what went on. Here's a look at what the RIPEstat visualisation has to show us about the event in question.
• 7 min read
RIPE Atlas probes actively measure Internet connectivity through a variety of measurement types. In this article, we take a closer look at what probes can tell us about outages.
• 3 min read
As part of the Internet health hackathon, we studied RIPE Atlas delay signals before and during the COVID-19 pandemic. Here's what we found.
• 5 min read
After the recent earthquake in Croatia we looked at RIPE Atlas and RIS data to visualise the impact a large event like this can have on the resilience of the Internet.
• 8 min read
...or, how RIPE Atlas measurement data just got a little bit more complex. Some people say IPv6 is "96 more bits, no magic". And while this is true for most network operators, if you're a RIPE Atlas system programmer, you can run into interesting situations. In this article, we described how link-l…
• 2 min read
How can you quickly figure out if a network you are using is dropping invalid Resource Public Key Infrastructure (RPKI) BGP announcements? You can do so by opening up a browser and visiting our RPKI test web page.
• 8 min read
When withdrawing an IP prefix from the Internet, an origin network sends BGP withdraw messages, which are expected to propagate to all BGP routers that hold an entry for that IP prefix in their routing table. Yet network operators occasionally report issues where routers maintain routes to IP prefi…
• 3 min read
Based on RIPE Atlas measurements, we can illustrate if paths between different networks in a given country stay in that country. We can also provide sketches of interconnections between networks in that country. In this article we look at the situation in Bosnia and Herzegovina.
• 6 min read
This post describes the result of an internship of a month of integrating an experimental data analysis method into RIPE Atlas.
• 8 min read
Networks rely increasingly on Internet Exchange Points (IXPs) and carrier-neutral interconnection facilities that enable dense localised peering connectivity to handle the massive traffic exchange between clients and servers.
“One may assume that, if some people delayed the changes, other people rushed in to adapt the networks to the increased load? Both behaviour may explain why the change rate is more or less the same?”
I think it would be interesting to dig into this data deeper indeed. I looked at splitting this out per country a bit, but could try figure out if there are trends in the sets of ASNs in this timeseries. Would you be willing to look at this? My colleague Vesna is doing a virtual hackathon around Internet and Corona ( https://labs.ripe.net/Members/becha/hackathons-in-the-time-of-corona ), I'd love it if we could collaborate around this. Let me or Vesna know, or hop on to the conf calls, Mon 2pm UTC ( 3pm Paris timezone :) )
“Ghost routes: https://www.sixxs.net/tools/grh/what/”
I've added a reference to the different names 'stuck routes' and 'ghost routes' for this phenomenon at the beginning of the post. Thanks for the pointer!
“Interested in repeating this analysis for 2018 world cup?”
Hi Dan, we have no plans of repeating this analysis this time. This type of signal is still there, see for instance https://twitter.com/search?q=%40ohohlfeld%20%23worldcup&src=typd for a couple of graphs that show the impact in various places.
“@emileaben Rather than standardizing human-readable output format, why not emitting a standard structured format, separating the network part (traceroute) and the visualisation part (a tool using the structured output format). Such a format already exists, in RFC 5388. I let you do the same in JSON :-)”
thanks for the interest in the topic Stephane. You hit the nail on the head, the main idea was to standardise a structured format for traceroute. I notice a lack of enthusiasm for RFC5388, probably due to it's verbosity. quick test shows that gzip compression of RFC5388-style results would need 3x more storage relative to plain-text traceroute results. But the RFC is likely very useful to see if we cover all bases in a slimmer structured output format.
One other activity that may be worth mentioning here: We organised a get-together for traceroute implementers. As many traceroute implementations do things slightly different, a bit more coordination can help in making things more consistent, for instance in output formats.
“I'm trying to work with the ixp-jedi tool. In this step: ## measure.py This script runs one-off measurements for the probes specified in _probeset.json_ and stores their results in _measurementset.json_ This uses the RIPE Atlas measurement API for measurement creation, And it needs a valid measurement creation API key in ~ / .atlas / auth When trying to execute the script ./measure.py I get the following and I do not know how to solve it. Authentication file /root/.atlas/auth not found Please, I need your help.”
hi, thanks for trying to use the tool. i hope the docs on github are clear enough: https://github.com/emileaben/ixp-country-jedi/#measurepy --- This script runs one-off measurements for the probes specified in probeset.json and stores their results in measurementset.json This uses the RIPE Atlas measurement API for measurement creation, and it needs a valid measurement creation API key in ~/.atlas/auth . For more information on RIPE Atlas API keys see https://atlas.ripe.net/docs/keys/ --- if not let me know how to improve that. if you are interested in country-level monthy runs. these are available at: http://sg-pub.ripe.net/emile/ixp-country-jedi/history/
“Hi, Is there a way to download multiple days dataset without having to do them individually? Also do you have any API's which will permit me to download the datasets using wget?”
Hi Meenakshi, I think you'll have to download the files individually. I think, if your RIPE Access account doesn't have 2 factor authentication, you can use wget to download the files with the --user and --password options.
While we were busy pushing this post out, it looks like the Gambian Internet was restored, roughly around 12h UTC on 2 December. RIPE Atlas probes came online again, and we see 6 out of 7 ASNs in RIS data again.
Showing 18 comment(s)