Iran and K-root: The Rest of the Story
Dyn Research published an article on K-root recently. Here we would like to augment the picture with data from RIPE Atlas in order to provide a more complete picture of the effect of the K-root node in Iran.
Emile Aben
Based in Amsterdam, NL
98
Articles
408
Likes on articles
About the author
Based in Amsterdam, NL
I'm a system architect/research coordinator at the RIPE NCC, where I work in the science group. 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.
Looking at France-IX with RIPE Atlas and RIS
This article describes our recent collaborations with France-IX on collecting data plane and control plane Internet data with RIPE Atlas and the RIPE NCC's Routing Information Service (RIS).
Has the Routability of Longer-than-/24 Prefixes Changed?
In October 2014 we started announcing a few longer-than-/24 prefixes and determined they were not very visible according to the Routing Information Service (RIS) and RIPE Atlas measurements. Now, almost a year later, we revisit this.
The Internet in North Korea - Hanging by a Single Thread?
North Korea is one of the most secluded countries in the world, but it is nonetheless connected to the Internet. We investigate North Korea's Internet connectivity in light of recent outages and discuss the fragile nature of its setup.
Improving RIPE Atlas Coverage - Which Networks Are Missing?
In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see which eyeball networks are missing out on RIPE Atlas probes.
Measuring Countries and IXPs in the SEE Region
We looked at Internet measurements for the South East Europe (SEE) region in order to share these with attendees at the SEE 4 Meeting that took place from 21-22 April 2015 in Belgrade, Serbia. This is the long version of the lightning talk Vesna Manojlovic gave at SEE 4.
Measuring Countries and IXPs with RIPE Atlas
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 improve performance and efficiency for IXPs and their members. To explore this, we've…
#facebookdown? What Internet Measurement Data Shows
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.
Visualising IPv4 and IPv6 Tweets
This time we explored Twitter feed visualisation with CartoDB, a map visualisation tool.
On the Diversity of Interdomain Routing in Africa
In 2013 and 2014 we looked into measuring Interdomain Routing in Africa using the RIPE Atlas infrastructure. This resulted in a paper published at the PAM (Passive and Active Measurement) 2015 conference. Here we present some highlights of this research.
How Does the MENOG Region Measure Up?
With the MENOG 15 meeting taking place this week, we look at Internet measurements and statistics for countries in the MENOG region.
One Year Later: Who's Doing What With IPv6?
On the anniversary of the World IPv6 Launch, this article takes a look at the readiness of networks to deploy IPv6, using statistics from the RIPE NCC service region and beyond.
IXP Traffic Levels During the Stratos Skydive
Together with Euro-IX we take a look at Internet Exchange Point (IXP) traffic levels during Felix Baumgartner's 39-kilometre jump to Earth, and we take a closer look at what exactly we can see at IXPs.
Comparing TCP and UDP Response Times of DNS Root Servers
We did some measurements on the round-trip (RT) values of DNS queries for SOA (Start of Authority) records from our RIPE Atlas probes, over both UDP and TCP. We plotted the TCP/UDP ratios on graphs, and found that, as expected, for the majority of the measurements, it is around 2. However, we also …
Number of New LIRs and their IPv6 RIPEness
We observed an increase in the number of new LIRs in the RIPE NCC service region. Many of these new LIRs show 1-star IPv6 RIPEness.
Internet Traffic During the 2012 Olympics
Following on from the European Championship earlier this year, we looked at changes in Internet traffic volume at Internet Exchange Points (IXPs) during the Olympics. This is a joint project with Euro-IX.
Top Ten Olympic Winners and Indicators of IPv6 Preparedness
Olympic fever didn't escape us here at the RIPE NCC!
“@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 15 comment(s)