
Visualising Network Outages With RIPE Atlas
This article shows some prototypes of visualising network outages with RIPE Atlas using CartoDB.
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.
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.
This time we explored Twitter feed visualisation with CartoDB, a map visualisation tool.
As the RIPE Atlas network continues to grow, it's useful for ambassadors and potential probes hosts to easily see where we already have probes deployed and where we'd like more probes installed. We created a few useful maps to help with this.
Under ARIN's Number Resource Policy Manual (NRPM) Section 4.10, the IPv4 address block 23.128/10 is reserved for allocations and assignments dedicated to facilitate IPv6 deployment. The maximum allocation size is a /24; the minimum allocation size is a /28. There has been much discussion on the NAN…
The Time Warner Cable network suffered an outage on 27 August 2014 between approximately 9:40 and 10:55 UTC. We looked at some interesting details of this outage using RIS and RIPE Atlas.
A week after the 512K-routes problem started making waves, we took a look at the global effects to see what impact it had. Spoiler: Not much.
The World Cup is one of the most watched events on the planet, and we've been looking at traffic changes at Internet Exchange Points during the matches in Brazil at World Cup 2014. The final part of our analysis is now available, with a look at what happened during the final four matches of the tou…
Article tags:
Engineers from the Wikimedia Foundation and the RIPE NCC recently collaborated on a project to measure the latency of Wikimedia sites for users worldwide. Together, we identified ways to decrease latency and improve performance for users around the world.
In RIPE Atlas we see latencies to Google's 8.8.8.8 DNS resolver service drop in Turkey. We expect this is due to hijacking of the 8.8.8.8 service. Our measurements show a timeline of these events. Note that even when the Twitter ban had been lifted, RIPE Atlas still saw fake 8.8.8.8 DNS service…
The European Football Championships is the third most watched sporting event in the world (after the World Cup and the Olympics). Euro 2012 takes place in Poland and Ukraine from 8 June, so we are teaming up with Euro-IX (The European Internet Exchange Point Association) to look at Internet Exchang…
This article is looking at different measurements done at the network level and at the end user level and the results seen through these measurements.
RIPE Atlas is releasing a new service for Local Internet Registries (LIRs): if you are a member of the RIPE NCC, you can test the reachability of your IPv6 website from all IPv6-capable RIPE Atlas probes (currently more than 600).
One year after we released the interactive graph to show the percentage of ASes announcing IPv6 prefixes, we looked at the progress made since then.
In this article we will be delving into the behaviour of the Linux implementation of TCP, and looking at the way in which TCP establishes a connection. There are socket options in Linux that cause the TCP handshake to behave in a rather curious way.
Following your feedback, we decided to make IPv6 RIPEness a production service. We are currently working on some new features. Stay tuned!
After we observed increased query load on the root name severs recently, we did some investigation and analysis which is described in the article below.
World IPv6 Day took place on 8 June 2011. The RIPE NCC did a number of measurements both before and during World IPv6 Day. We've done an initial analysis of the data and would like to share our first impressions and results with you.
RIPE NCC and BBN have been working on measuring the impact of 6to4 on the latency of Internet traffic. This article describes the measurement techniques used for this survey, and some initial findings based on measurements conducted at BBN.
A year ago we introduced IPv6 RIPEness - a system that rates IPv6 deployment of Local Internet Registries based on certain criteria. It was meant to encourage LIRs to deploy IPv6. Now, one year later, we are proud to present the progress of this project.
This RIPE Labs article has good information on how to avoid effects from unknown attributes showing up at your BGP routers: https://labs.ripe.net/author/berislav_todorovic/bgp-path-attribute-filtering-a-powerful-tool-to-mitigate-alien-attributes/
“Hi Emile, I remember attribute 28 showing up in several previous studies. Interesting to see it causing a problem this time! As bgpdump maintainer, I'd ask you to check out v1.6.2 or higher, since 2020 there is a '-u' flag to output unknown attributes in the short (-m) mode (helpfully submitted by Italo Cunha) - it may make your future parsing life much easier :) Kind regards, Colin”
Thanks Colin, I didn't know, and this would have speeded up my analysis if I had!
Code for looking into AS Adjacency changes is available here: https://github.com/emileaben/as-neighbour-diff
Code on how to create graphs like Figure 1 ( ie. BGP view of how networks in a country interconnect ) is available here: https://github.com/InternetHealthReport/country-as-hegemony-viz
NOG Alliance is helping out network operators in Ukraine: https://nogalliance.org/our-task-forces/keep-ukraine-connected/
An effort related to keeping Urkanian servers/websites online by the Dutch Cloud Community: https://dutchcloudcommunity.nl/community/cloud4ukraine/
We got a request for the HHI scores for other countries. I've put these in a small repo on github together with the code that generated this. repo: https://github.com/emileaben/hhi-eyeballs HHI scores for 2022-03-07 are available here: https://raw.githubusercontent.com/emileaben/hhi-eyeballs/main/eyeball-hhi.2022-03-07.csv
“This is awesome work, thank you! Do you maybe have the script/notebooks/sources to reproduce this? This could be potential used for other countries.”
Hi Jenneth, The observable notebook we used for this is here: https://observablehq.com/@aguformoso/internet-outages-as-seen-by-ripe-atlas . It's a little rough around the edges, so it would be great if you could help improve it!
Thanks for your comment Maxime. I would love to see more analysis too, and the tool allows people to do this. Take for instance this thread on Twitter where Jason Livingood analyses the signals for the US: https://twitter.com/jlivingood/status/1245142990336688130 If others have analysis for specific countries they want to share it would be great to have them collected, for instance as comments to this RIPE Labs post!
“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 :) )
Showing 17 comment(s)