I have found a few examples and "explanations" but in the cases of the examples I have seen by other people, like:
https://serverfault.com/questions/733005/what-does-having-mean-in-the-command-traceroute-and-how-can-you-cope-wit It is not with every site and it is mostly with one hop. I my case it is with all sites and once the packets reach the web (from hop 5 to 30), from wherever I connect to the Internet. Why would that happen and why would that -consistently- "happen" to me? $ traceroute google.com traceroute to google.com (172.217.0.174), 30 hops max, 60 byte packets 1 _gateway (199.83.128.1) 6.687 ms 6.660 ms 6.683 ms 2 199.83.240.2 (199.83.240.2) 6.101 ms 6.622 ms 6.610 ms 3 ad.nypl.org (199.254.254.1) 6.600 ms 6.588 ms 6.577 ms 4 199.254.252.1 (199.254.252.1) 6.566 ms 6.590 ms 6.738 ms 5 * * * . . . 30 * * * $ traceroute microsoft.com traceroute to microsoft.com (20.81.111.85), 30 hops max, 60 byte packets 1 _gateway (199.83.128.1) 12.353 ms 12.319 ms 12.306 ms 2 199.83.240.2 (199.83.240.2) 11.803 ms 12.281 ms 12.268 ms 3 ad.nypl.org (199.254.254.1) 12.256 ms 12.244 ms 12.231 ms 4 199.254.252.1 (199.254.252.1) 12.255 ms 12.243 ms 12.511 ms 5 * * * . . . 30 * * * $ traceroute debian.org traceroute to debian.org (149.20.4.15), 30 hops max, 60 byte packets 1 _gateway (199.83.128.1) 16.821 ms 17.804 ms 17.784 ms 2 199.83.240.2 (199.83.240.2) 4.739 ms 5.086 ms 5.070 ms 3 ad.nypl.org (199.254.254.1) 5.054 ms 5.389 ms 5.023 ms 4 199.254.252.1 (199.254.252.1) 6.805 ms 6.282 ms 6.773 ms 5 * * * . . . 30 * * * lbrtchx
