With the attempted coup in Turkey, reports went out about social media being throttled and/or blocked. We analysed data about this that we collected with RIPE Atlas and the Open Observatory of Network Interference (OONI).
I'm a system architect 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 visualization 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, soccer), and try to be a good parent.
Pages created by Emile Aben
I attended a conference on Broadband Services and Infrastructure Mapping, which I think had some interesting content for RIPE Labs readers.
RIPE Atlas collects a lot of measurements. But how much of the Internet are we actually measuring? We had a sense that with a limited amount of extra load on the system, we could dramatically increase the number of router IPs seen on a given day in RIPE Atlas - and that means measuring more of the Internet.
The Internet has a robust infrastructure that was designed to route around damage. But how well does it do this? We use RIPE Atlas to look at how large-scale disruptions in the Internet's core infrastructure affect end-to-end connectivity on the Internet.
When operators and researchers use data from BGP route collectors such as RIS and Route Views, it's not easy to tell if a path announced to a collector is an ISP's customer cone, an internal route, or one learned from peering or transit. In this post we look at what information we can currently get from BGP communities in RIS.