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/ripe-atlas@ripe.net/
[atlas] 1msec RTT to ipv6.google.com?
- Previous message (by thread): [atlas] 1msec RTT to ipv6.google.com?
- Next message (by thread): [atlas] 1msec RTT to ipv6.google.com?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jen Linkova
furry13 at gmail.com
Tue Jul 21 13:31:33 CEST 2015
On Tue, Jul 21, 2015 at 12:33 PM, Roman Mamedov <rm at romanrm.net> wrote: > On Tue, 21 Jul 2015 09:37:13 +0000 > "Abreu, Alexandre, Vodafone Portugal" <alexandre.abreu at vodafone.com> wrote: > >> Based on your feedback I've built a probe with the IP address instead of the hostname and I now get "normal" results. There's something weird about the DNS resolution that is leading to these results. > > Read about: https://peering.google.com/about/ggc.html > > Your probe may have resolved ipv6.google.com to the IP of your ISP's Google > Global Cache mirror, hence the very low ping. Does not look like that as the address is 2a00:1450:4003:806::200e which is Google VIP in Europe. -- SY, Jen Linkova aka Furry
- Previous message (by thread): [atlas] 1msec RTT to ipv6.google.com?
- Next message (by thread): [atlas] 1msec RTT to ipv6.google.com?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]