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.
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.
Since we started providing the certification service on 1 January 2011, many LIRs made use of the service. In this article you can see some graphs showing the number of certificates in place today, as well as certified address space.
It is often claimed that the Internet Routing Registry is not accurate and complete enough. Is this really the case? In this article we are looking at how many organisations that receive an Autonomous System Number from the RIPE NCC use the RIPE Routing Registry.