> On May 23, 2016, at 8:16 AM, Lorenzo Colitti <[email protected]> wrote:
> 
> Very nice. I wonder why www.facebook.com <http://www.facebook.com/> shows 
> much better IPv4 latency?

First guess is something about data center location. IPv6 works well for them 
on the UA west coast and measurement points in Australia and SE Asia, but IPv4 
is better in Europe and the US east coast. Now look at LinkedIn.

> On Mon, May 23, 2016 at 11:30 PM, Bajpai, Vaibhav 
> <[email protected] <mailto:[email protected]>> wrote:
> Dear v6-ops,
> 
> 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 <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 3320).
> 
> 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 :-)
> 
> Feedback most welcome!
> 
> Best, Vaibhav
> 
> ===================================
> Vaibhav Bajpai
> www.vaibhavbajpai.com <http://www.vaibhavbajpai.com/>
> 
> Room 91, Research I
> School of Engineering and Sciences
> Jacobs University Bremen, Germany
> ===================================
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to