<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>Hi,<div><br></div><div>I didn't observe this exact thing, but I've seen some weird traceroute outputs on a Windows box behind a Comtrend ADSL router. The PTRs returned were completely wrong and I think there were some other issues too.</div><div>Once we replaced the CPE everything went back to normal, so I'd check that first, maybe it's doing something funny to the IPv6 traffic.<br><br>Best regards<div>Tom� Hetmer</div><br><br><div>> From: alexandre.abreu@vodafone.com<br>> To: ripe-atlas@ripe.net<br>> Date: Tue, 21 Jul 2015 08:51:41 +0000<br>> Subject: [atlas] 1msec RTT to ipv6.google.com?<br>> <br>> Hi all<br>> <br>> Anyone had any issues with wrong RTTs on IPv6 probes? I've setup a ping probe (ID#2143865) to ipv6.google.com and it's consistently giving 1msec RTT on the seismograph and the json file. It is physically impossible. This is the RTT I get on the CPE the probe is connected to:<br>> <br>> SEQ HOST SIZE TTL TIME STATUS <br>> 0 2a00:1450:4003:806::200e 56 59 12ms echo reply <br>> 1 2a00:1450:4003:806::200e 56 59 12ms echo reply <br>> 2 2a00:1450:4003:806::200e 56 59 12ms echo reply <br>> 3 2a00:1450:4003:806::200e 56 59 12ms echo reply <br>> 4 2a00:1450:4003:806::200e 56 59 12ms echo reply <br>> 5 2a00:1450:4003:806::200e 56 59 12ms echo reply <br>> <br>> Regards,<br>> Alexandre Abreu<br>> <br></div></div> </div></body> </html>