Monitor the Syrian Blackout with RIPEstat
• 3 min read
The RIPE NCC developed a RIPEstat widget that provides a near real-time feed of what BGP updates and withdrawals we see from Syrian IP address space.
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.
Website: https://www.caida.org/~emile
• 3 min read
The RIPE NCC developed a RIPEstat widget that provides a near real-time feed of what BGP updates and withdrawals we see from Syrian IP address space.
• 13 min read
In this article we look at some of the effects Hurricane Sandy had on the Internet data plane, as we can see them in traceroutes done by RIPE Atlas.
• 3 min read
After causing lots of damage in the Caribbean, superstorm Sandy is having a devastating effect on the US East Coast. We looked at the RIPE Atlas network to find out what effects this superstorm has on the Internet. Below are some preliminary results of what we saw.
• 6 min read
At the recent RIPE Meeting, the question was raised whether Internet users would see significant filtering of AAAA DNS queries or replies. We used RIPE Atlas measurements to provide an answer to this question.
• 9 min read
IPv6 RIPEness helped in creating awareness and got people into action with regards to their first steps towards deploying IPv6 in the RIPE NCC service region. Up until now IPv6 RIPEness didn't measure actual IPv6 deployment. In this article we propose a measure (a "5th star"), which attempts to mea…
• 4 min read
Olympic fever didn't escape us here at the RIPE NCC!
• 9 min read
In this article I look at four different IPv6 destinations in different BGP set-ups and how these are seen by RIPE Atlas probes. This reveals some differences in reachability for the different networks, likely due to BGP route filtering. We see roughly 1% out of ~500 RIPE Atlas probes that can't re…
• 2 min read
Now that World IPv6 Launch is weeks behind us it's interesting to look at what long-lasting effects it had.
• 10 min read
We've enabled RIPE NCC members to do IPv6-traceroutes from all RIPE Atlas probes to IPv6 destinations. Until now they could get the raw analysis results (text/JSON representations of traceroute results) for analysis. In this article we present a first experimental analysis and visualisation of the …
• 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.
“Thank you for this, Emil and Alun! From looking at the map you provided, it would be great to see an additional anchor in Katthammarsvik. Do you think it's worth trying to add one there?”
Thanks for the suggestion. I think that depends on the physical (cables) and logical (routing) topology near Katthammarsvik in relation to the cable landing there. In a quick search I didn't find datacentres there, which makes me think it would not be too useful. Experts on the local Internet infrastructure would probably be able to answer if it would make sense or not.
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!
Showing 18 comment(s)