Speculation about Russia disconnecting or being disconnected from the wider Internet abounds. In this article, we look at the connectivity of the Russian Internet to the wider Internet and how this evolved around the Russian invasion into Ukraine and sanctions related around that.
Based in Amsterdam, NL
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.
Links & Social
We are looking closely at what RIPE Atlas and RIPE RIS have to tell us about the state of the Ukrainian Internet. Initial observations indicate that Internet infrastructure in the country is continuing to function as the conflict unfolds.
We created a data aggregate we call 'minRTT' that gives the minimum latency into each ASN (and IXP!) from RIPE Atlas for a given day. This allows us to visualise network deployments and can help with insights into structural latency problems for a network. We build a few visualisations on top of th…
On 23 March 2021, LINX London experienced an outage. As this is one of the very large Internet Exchange Points, this is an interesting case to study in more depth in order to see what we can learn about Internet robustness.
In this post we introduce a wiki to document RIPE Atlas measurements better. We use the measurements we created to track RPKI Repository Performance to show how this is useful.
Over the past months we've been looking at our Routing Information Service (RIS) and thinking about how to make it best fit for purpose. Ahead of our upcoming RIPE NCC Open House on RIS, this post raises a set of open questions to our community aimed at starting a conversation about how we can keep…
We are getting ready to start allocating from 2a10::/12, a new block of IPv6 addresses. In this process we did a couple of 'pre-flight' checks to check the usability of address space in this /12 block.
The events season has started! This article is an invitation to people from across many communities, whatever your role or level of experience, to come and participate in workshops, conferences, camps, lectures, festivals, and more.
In 2021, reports emerged that hosts in Mexico were unable to reach whatsapp.net. It was determined that middleboxes were to blame, intercepting the queries to the root instance hosted in China and sending a bogus reply. This article investigates the prevalence of middleboxes using RIPE Atlas probes.
Following the Facebook outage that took place on 4 October, we saw people looking to BGPlay to get a better view of what went on. Here's a look at what the RIPEstat visualisation has to show us about the event in question.
...or, how RIPE Atlas measurement data just got a little bit more complex. Some people say IPv6 is "96 more bits, no magic". And while this is true for most network operators, if you're a RIPE Atlas system programmer, you can run into interesting situations. In this article, we described how link-l…
When withdrawing an IP prefix from the Internet, an origin network sends BGP withdraw messages, which are expected to propagate to all BGP routers that hold an entry for that IP prefix in their routing table. Yet network operators occasionally report issues where routers maintain routes to IP prefi…