This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[mat-wg] v4 versus v6 -- who connects faster?
- Previous message (by thread): [mat-wg] New on RIPE Labs: There Is Gold in This Stream - Sifting Through Used RIPE Atlas Traceroute Results
- Next message (by thread): [mat-wg] New on RIPE Labs: New RIPE Atlas APIs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bajpai, Vaibhav
v.bajpai at jacobs-university.de
Mon May 23 11:21:24 CEST 2016
Hello, -- sorry for cross-posting Here [a] is a toy v6 service I came up with during the RIPE Atlas hackathon over this weekend. Thought I share this along: [a] http://goo.gl/hbzbwD You enter a dual-stacked website (ALEXA top 10K) and it shows you the difference in TCP connect times over v4 and v6 as seen by all dual-stacked RIPE Atlas probes (~1.3K probes). You can also filter the visualisation from a specific origin-AS. This additional filter can be useful to view performance towards a website from a specific origin-AS (say DTAG). Disclaimer: This is an outcome of a 1.5d long hackathon project. As such, the codebase is possibly inundated with bugs. Please don’t see it as a production service :-) Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================
- Previous message (by thread): [mat-wg] New on RIPE Labs: There Is Gold in This Stream - Sifting Through Used RIPE Atlas Traceroute Results
- Next message (by thread): [mat-wg] New on RIPE Labs: New RIPE Atlas APIs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]