You are here: Home > Publications > RIPE Labs > Stephen Strowes

Stephen Strowes

14 Dec, 2016 04:37 PM
Comparing Virtual and Metal RIPE Atlas Anchors by Stephen Strowes — last modified 04 Jul, 2018 02:55 PM

Our VM pilot allows us an opportunity to run a like-for-like comparison between two RIPE Atlas anchors. We're grateful for the support from DigitalOcean, who are running two machines (one metal, one virtual) from the same geographical location.

IPv6 Launchiversary: the View from RIPE Atlas and K-root by Stephen Strowes — last modified 25 May, 2020 09:56 AM

IPv6 growth continues apace; content networks regularly measure more than 20% of their requests as taking place over IPv6 today. However, deployment has not been uniform. In this article, we review growth from the perspective of RIPE Atlas data since the launch event.

Current Network Connectivity from Puerto Rico by Stephen Strowes — last modified 05 Oct, 2017 04:04 PM

Hurricanes Irma and Maria struck massive damage across the Caribbean this year. In disaster recovery situations, the Internet is critical communications infrastructure. In this article, we look at the observable network effects on Puerto Rico in the aftermath of hurricane Maria.

Echoes by Stephen Strowes — last modified 28 Aug, 2017 01:11 PM

Recently, we spotted a network bug that had precisely the opposite of the intended effect.

BGP Even-More Specifics in 2017 by Stephen Strowes — last modified 10 Jul, 2017 02:09 PM

Since October 2014, we have been advertising two IPv4 /25s and two IPv4 /28s, to better understand how far they propagate across the network. In this article, we review how things have (or have not) changed over the years.

Talking Traffic at TMA 2017 by Stephen Strowes — last modified 30 Jun, 2017 02:08 PM

Last week, the Network Traffic, Measurement and Analysis Conference (TMA) took place in Maynooth, Ireland. A full week was scheduled, featuring a PhD school across Monday and Tuesday, the Mobile Network Measurements (MNM) workshop on Tuesday, and the main conference from Wednesday to Friday. We were there! Here's our summary of the week.

Reviewing the 2016 Leap Second by Stephen Strowes — last modified 16 Jan, 2017 10:44 AM

Last month we covered the 2015 leap second ahead of the insertion of a leap second at the very end of 2016. As stated previously, leap seconds can trigger poorly-tested code paths; leap second handling always unearths bugs and issues. This one was no exception!

Preparing for the 2016 Leap Second by Stephen Strowes — last modified 16 Jan, 2017 10:45 AM

On 31 December this year, we're scheduled for another leap second. There are many stories about what leap seconds can do to infrastructure and applications, and rituals are built up around them. Such rituals stem from reality: leap seconds trigger poorly-tested code paths and run contrary to assumptions that system time always runs in one direction. It's useful to be aware of how your infrastructure handles leap seconds and how NTP servers handle them, so you can plan around the event. Here, we look at some of the NTP measurements the RIPE Atlas platform took around the last leap second, and approaches for handling them.