Colleagues, I was getting excited again about my score - it actually peaked at 0.9 earlier today:
http://www.pool.ntp.org/scores/89.101.218.6 However, I am noticing that the monitoring algorithm takes away much faster than it adds with each missed probe. So it doesn't look like I am going back to the active pool unless the routing changes from what has been since 17th February: Traceroute to 89.101.218.6 1 ge1-10.hr02.lax2.phyber.com (207.171.3.1) AS7012 0.360 0.506 0.493 2 te7-4.r01.lax2.phyber.com (207.171.30.61) AS7012 0.455 0.448 0.698 3 xe-0-1-0-30.r01.lsanca07.us.bb.gin.ntt.net (198.172.90.73) AS2914 0.940 0.925 0.914 4 ae-3.r23.lsanca07.us.bb.gin.ntt.net (129.250.4.106) AS2914 0.654 0.623 0.847 5 ae-12.r22.snjsca04.us.bb.gin.ntt.net (129.250.4.150) AS2914 8.368 11.314 8.361 6 ae-40.r02.snjsca04.us.bb.gin.ntt.net (129.250.3.121) AS2914 13.714 10.809 11.508 7 * * * 8 us-nyc03a-rd1-ae12-0.aorta.net (84.116.135.122) AS6830 174.564 174.565 171.631 9 * * * 10 ie-dub01a-ra4-ae1-0.aorta.net (84.116.137.73) AS6830 167.806 168.919 164.823 11 nl-ams04a-rb1-xe-0-0-1-0.aorta.net (84.116.134.145) AS6830 163.496 165.884 162.947 12 at-vie01a-rd1-xe-3-2-0.aorta.net (84.116.134.234) AS6830 200.391 177.621 177.155 13 (84.116.134.206) AS6830 166.951 170.474 169.802 14 ie-dinc-ram-a-ae1-0.aorta.net (84.116.238.49) AS6830 171.882 171.913 168.898 So NTT.NET is still in the route between the monitoring server and my server. There was lots of talk about central and decentralised monitoring in the last days - it is not clear to me what the way to move forward is from these discussions. Thank you, Ron -----Original Message----- From: pool [mailto:[email protected]] On Behalf Of Peter Sent: 25 February 2017 14:45 To: pool Subject: Re: [Pool] Decentralised monitoring? - Was: Why is my server score suddenly so poor? 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
