Articles
Likes on articles
Stephen is a principal engineer in the Office of the CTO at Fastly, where he spends his time trying to figure out what the Internet is. He obtained his PhD in Internet routing scalability from the University of Glasgow in 2012.
Website: https://sdstrowes.co.uk/
• 8 min read
As part of our ongoing efforts to chart the rise and rise of IPv6, we’ve been looking into the difference between average IPv6 capability per country over a few days in June 2020 versus the most recent similar averages for 2021.
• 7 min read
We've been using Google's BigQuery platform for ongoing operational tasks and research questions, and we've got a little more experience under our belts. We're improving the ways we expose public data on the platform.
• 11 min read
In prior work, we've studied IPv4 allocation patterns in domestic ISPs. Time has passed, and IPv6 adoption has continued, so in this article we review our current observations on IPv4 and IPv6 assignment practices.
• 15 min read
In February this year, we opened up applications to host RIPE Atlas software probes. After spending a few months diligently measuring the Internet, how are they doing?
• 5 min read
Google BigQuery is a data warehousing platform with an SQL query interface on top. This is a powerful tool that allows us to rapidly filter, query, and process RIPE Atlas measurement results, improving our ability to explore this dataset. We are now making RIPE Atlas measurement results publicly av…
• 13 min read
In August 2011, we wrote about IPv4 and IPv6 prefix lengths visible in BGP. It's time for an update!
• 10 min read
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.
• 10 min read
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.
• 2 min read
A few months ago we started offering daily archives of public RIPE Atlas measurements. We're happy to announce that this service is here to stay!
• 6 min read
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.
Hey! The difference is that the .bz2 is a dump of measurement results, but /api/v2/measurements/traceroute/ gives you measurement metadata. The json returned from the API call you provided includes 'result' fields, each of which refers to the measurement IDs with the actual results. If you want, you can run through those pointers and pull down the measurement results manually to get at the result data we're putting into the .bz2 archives. Note also that the output of that API call is paginated; use option "page_size=500" (the maximum) to reduce the number of pages you have to loop over. Hope that helps!
“So, historic data older than one month will be lost (or made unuvailable publically) forever?”
Hi Alexander! Measurement data -- all of it -- is always available via the API. The archives discussed here are a convenience method, offering data from recent public measurements in bulk form. In the future, we may modify this service to hold data for longer or to provide samples of older data, in the same location. If so, we'll be sure to announce it.
“Hi, all. Is there a recommendation (RFC or something) that ISPs follow for allow or not allow and propagate longer than /24 prefixes?”
Hi Alan! I'm not personally aware of a document, only the common convention that has been accepted for many years. Many documents refer to the current practice, including https://www.ripe.net/publications/docs/ripe-399 (from 2006) and https://tools.ietf.org/html/rfc4116 (from 2005). A more recent look at how far /24s propagate on the v4 Internet was published here: https://labs.ripe.net/Members/stephen_strowes/bgp-even-more-specifics-in-2017 In practice, the convention exists to avoid bumping into routing table limits too soon; even natural growth rates using the current conventions can catch networks unawares; for example, https://arstechnica.com/information-technology/2014/08/internet-routers-hitting-512k-limit-some-become-unreliable/
“Do you mean 6rd seriously? We live in year 2017 and you are using a technique for lazy people.”
Hi Thomas; we tend to take the view that reachability via an ISP-provisioned and managed transition mechanism is better than no reachability. Anything that brings more IPv6 to the internet is good.
Of course, the IPv6 world offers much finer granularity. A /32 ought to give folks 2^16 globally routable prefixes, so a maximum y-resolution of 65,536 pixels. x-resolution only relies on how patient the artist is!
Showing 5 comment(s)