* Steve Meuse ([email protected]) wrote: > It's likely a reverse DNS error. If you look at the latency, it's within > range of the previous hops.
Still curious that the systems (IPv6 addresses) are changing too.. It's
not like it's the same route but just different rDNS results. It's also
quite a bit of latency between he.net and Comcast. Also seeing ~20%
packet loss to systems in Comcast and ~15% packet loss end-to-end.
Certainly seems like there's something unhappy there, but I'll just keep
an eye on it.
Thanks!
Stephen
signature.asc
Description: Digital signature
