Hi Peter, Surprisingly (at least to me) I have both GTT (hop 6-7) and NTT (hops 9-10) in my traceroute: traceroute to ntplax7.ntppool.net (207.171.3.17), 64 hops max 1 192.168.133.254 (192.168.133.254) 0.092ms 0.077ms 0.090ms 2 212.92.16.198 (gw-198-16.92.212.GYR.rev.HU.AHRT.HU) 4.847ms 7.171ms 2.582ms 3 212.92.0.241 (212.92.0.241) 0.485ms 0.502ms 0.515ms 4 87.245.242.202 (ae1-201.RT.DPX.BUD.HU.retn.net) 0.662ms 0.564ms 0.600ms 5 87.245.234.49 (et102-6.RT.IRX.FKT.DE.retn.net) 18.076ms 18.181ms 18.147ms 6 77.67.123.221 (ae5.cr9-fra2.ip4.gtt.net) 19.110ms 18.359ms 18.230ms 7 89.149.130.9 (et-8-1-0.cr2-lax2.ip4.gtt.net) 171.485ms 172.907ms 171.623ms 8 199.229.230.234 (te7-2.r02.lax2.phyber.com) 166.303ms 169.642ms 169.117ms 9 129.250.3.189 (ae-5.sayonara-jared.r23.lsanca07.us.bb.gin.ntt.net) 177.720ms 177.759ms 177.877ms 10 129.250.4.107 (ae-2.sayonara-jared.r01.lsanca07.us.bb.gin.ntt.net) 171.867ms 172.043ms 171.826ms 11 198.172.90.74 (te7-1.r01.lax2.phyber.com) 175.069ms 175.245ms 175.127ms 12 207.171.30.62 (te7-4.r02.lax2.phyber.com) 171.802ms 171.762ms 171.651ms 13 207.171.3.17 (ntplax7.ntppool.net) 172.361ms !* 172.345ms !* 172.283ms !*
Even more surprisingly: - hop 8 is a phyber.com node: te7-2.r02.lax2.phyber.com. Isn't Phyber the provider of the monitoring station? Anyway, I've just set up cron jobs to record traceroute outputs of both directions. Let's see if I find any changes in routes related matching to score drops. Actually running the same traceroute several times after each other, I could barely see the same output beyond et102-6.RT.IRX.FKT.DE.retn.net I understand that it is dynamic, but the traceroute from the monitoring server to my host seems to much more stable. Regards, Zsolt On 25 February 2017 at 15:44, Peter <[email protected]> wrote: > Hi Zsolt, > > It's interesting because I did a traceroute from my network (since my > recent improvement) and NTT is now gone: > > traceroute to ntplax7.ntppool.net (207.171.3.17), 30 hops max, 60 byte > packets > 1 82-70-138-65.dsl.in-addr.zen.co.uk (82.70.138.65) 0.490 ms 0.534 ms > 0.670 ms > 2 losubs.subs.dsl4.wh-man.zen.net.uk (62.3.83.6) 13.756 ms 14.752 ms > 15.580 ms > 3 ae1-120.cr2.wh-man.zen.net.uk (62.3.86.9) 15.958 ms 16.536 ms > 17.133 > ms > 4 ae2-117.cr1-man1.ip4.gtt.net (77.67.66.101) 44.214 ms 18.331 ms > 44.120 ms > 5 et-3-1-0.cr2-lax2.ip4.gtt.net (141.136.110.17) 160.481 ms 161.020 ms > 162.505 ms > 6 te7-2.r02.lax2.phyber.com (199.229.230.234) 182.805 ms 172.934 ms > 173.232 ms > 7 ntplax7.ntppool.net (207.171.3.17) 168.871 ms !X 167.289 ms !X > 167.810 ms !X > > Although the return still does go via NTT > https://trace.ntppool.org/traceroute/82.70.138.66 > > The change from NTT to GTT does seem to coincide with the improvement in > stability. So, they do seem to be a common factor. > > > Best regards, > > > > Peter. > > > On 24 February 2017 at 07:59, Zsolt Zsiros <[email protected]> wrote: > > > Hi Peter, > > > > The dark clouds of "Internet weather" just came over to Mid-Europe: > > http://www.pool.ntp.org/scores/212.92.16.193 > > This server is half ms away from the Budapest Internet Exchange. > > > > NTT is also involved: > > https://trace.ntppool.org/traceroute/212.92.16.193 > > > > Regards, > > Zsolt > > > > > > On 23 February 2017 at 23:44, Peter <[email protected]> wrote: > > > > > Can I ask my European fellow home connection folk that posted here to > > check > > > their graphs. Mine looks suspiciously more stable since midnight today > > > (Thursday) > > > > > > http://www.pool.ntp.org/scores/82.70.138.66 > > > > > > I'll need to see how it pans out, but certainly looks like there was a > > very > > > very sudden change somewhere. > > > > > > > > _______________________________________________ > > pool mailing list > > [email protected] > > http://lists.ntp.org/listinfo/pool > > > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool > _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
