Measuring World IPv6 Day - Long-Term Effects
• 6 min read
In this article we'll look at some of the more long-term effects of World IPv6 Day, as seen in our measurements a number of weeks after the event itself.
Based in Amsterdam, NL
Articles
Likes on articles
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.
• 6 min read
In this article we'll look at some of the more long-term effects of World IPv6 Day, as seen in our measurements a number of weeks after the event itself.
• 7 min read
As already stated by us and others, World IPv6 Day on 8 June, was a big success. No major issues came to light, and most minor issues that surfaced were resolved, and as such were a useful learning experience. In this article we provide details on some of the events we observed by looking at our me…
• 4 min read
World IPv6 Day is on 8 June 2011. On this day, a lot of organisations, including some of the most popular ones like Google, Yahoo and Facebook, are going to provide IPv6 addresses for AAAA queries for their websites. This will make content available over IPv6 for one full day. Since DNS responses a…
• 3 min read
The RIPE NCC is doing some measurements for World IPv6 Day. One of them is the IPv6 eye chart, a web page that allows you to test your connectivity to selected dual-stacked web sites and World IPv6 participants. The goal is to see if an end user has connectivity problems to dual-stacked websites. T…
• 6 min read
As announced earlier, the RIPE NCC is going to measure World IPv6 Day. This article details the measurements we intend to do.
• 7 min read
Amidst the recent political unrest in the Middle East, researchers have observed significant changes in Internet traffic and connectivity. In this article we tap into a previously unused source of data: unsolicited Internet traffic arriving from Libya. The traffic data we captured shows distinct c…
• 8 min read
In a previous article we measured that a large percentage of 6to4 connections fail. In this article we show our attempts to find out why these connections fail.
• 4 min read
This article is about the lottery of an iPad for people hosting RIPE Atlas probes. As an extra motivator for people to keep their probes up as much as possible, the lottery drawing is weighted based on probe-uptime.
• 6 min read
At the recent RIPE 61 meeting in Rome and at earlier meetings, we heard that connectivity over 6to4 is not very dependable, which hampers IPv6 deployment. I wondered how bad it really is and started measuring it. This article describes what I measured and shows the results. Spoiler: It's pretty bad.
• 2 min read
Following up from the IPv6 RIPEness graphs we published earlier, those Local Internet Registries (LIRs) that fulfill all 4 IPv6 RIPEness criteria are now listed on the RIPE NCC web site.
• 7 min read
Last week, the Network Traffic, Measurement and Analysis Conference (TMA) took place in Maynooth, Ireland. A full week was scheduled, featuring a PhD school across Monday and Tuesday, the Mobile Network Measurements (MNM) workshop on Tuesday, and the main conference from Wednesday to Friday. We wer…
• 6 min read
In this article we present a prototype web portal, which demonstrates the deployment of RIPE Atlas probes within eyeball networks based on Internet user population estimates per Autonomous System Number (ASN) per country.
• 9 min read
BGP routing table growth is one of the major Internet scaling issues, and prefix deaggregation is thought to be a major contributor to table growth. In this work we quantify the fragmentation of the routing table by the type of IP prefix. We observe that the proportion of deaggregated prefixes has …
• 11 min read
Please find below the third part of our technical services update. This time we're focusing on our research activities and a number of tools we are developing.
• 9 min read
Last month we covered the 2015 leap second ahead of the insertion of a leap second at the very end of 2016. As stated previously, leap seconds can trigger poorly-tested code paths; leap second handling always unearths bugs and issues. This one was no exception!
• 7 min read
In this article, we give one example of the possible communities that are now easier to build around RIPE Atlas probes. With the tagging of similar probes, existing communities can use additional tools for creating and analysing RIPE Atlas measurements, such as "IXP Country Jedi", to create their o…
• 8 min read
We look into why dynamic addresses change and find ISPs that renumber periodically, most commonly every 24 hours or a multiple of 24 hours. We also find that outages influence address changes.
• 8 min read
This article is intended to make RIPE Atlas users aware of ethical issues that could arise when using RIPE Atlas. We do not intend to propose any new formal processes or procedures to address the relevant ethical issues, but we do want to encourage members of the RIPE Atlas community to consider th…
• 6 min read
We used a number of RIPE NCC tools and data sets to take a quick look at the recent DDoS attack on Dyn’s infrastructure. We wanted to see if this could be found in the data produced by the RIPE Atlas community.
“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)