twtpe3-2kg9ezv has been reporting -100 for almost a week now. Is this (time2.google.com) server no longer active?
No, it just can’t reach your server for whatever reason. It seems to be able to reach some other NTP servers just fine, but not all.
1 Like
I understand. It’s screwing up the graph unfortunately.
Why would it the only one not being able my server for days not w?
Well, there will indeed be a “dotted line” at the -100 line for that monitor’s plots. But apart from that, it doesn’t really screw up the graph. The displayed score scale is always from -100 to 20, even if all the scores of all the monitors are at 20.
I’ll also mention for completeness that this monitor’s score will not affect your server’s overall score.
2 Likes
@theking2 a github issue to have the graph not show outliers from the “candidate” pool would be appreciated; if I am understanding your report correctly. Sign in to GitHub · GitHub
1 Like
Incidently the situation has not changed. twtpe3-2kg9ezv is listed under candidates with a score of -100. I know it should not concern me but doens´t this mean there a systematic problem? I understand the server itself has a score of 20 but what is wrong with monitoring if a candiate with a score of -100 (ignore the ntp) for such a long time without being dismissed as a practical candidate?
btw: Ignore clear outliers on rendering the graph · Issue #279 · abh/ntppool · GitHub
Can you show us the page of the server what you are talking about?
This one . The -100 are visible as the dotted line at the bottom
Long explaination short answer: Who / what select the candidates?. The process that selects the candidates is flawed.
Every monitor is candidate unless promoted to the limited set of testing or active. To be candidate a monitor is not selected, the other two kind are selected when their measurement quality is good enough.
That clears it up than. Googles ntp server is a monitor, can potentially monitor our servers (candidate) but currently is not as there is something in the path between googles ntp monitor and our servers.
It probably is this forever, for whatever reason. But currenty there is no process in place the will stop the combination of monitor server and pool server to appear even when they cannot “see” each other
I think seeing the black holes in the Internet is even good thing. One person, one day, may act on that.
See this description of the different monitor states, and transitions between them.
That monitor in TW has been unreachable to my server forever but as mantioned by @avij , this doesn’t affect overall score of your / my server:
Thanks!. Yes it has no effect.
I believed however that -100 is a sentry with a special meaning. Other than -97.3
Thanks! Yes I have memorized that. To explain: the socres of condidates have no effect the pooled server
1 Like
Can you clarify one thing, maybe for the future generations..
What makes you think this monitor is Google’s NTP server? I don’t think Google has any NTP servers or pool monitors in the NTP pool.
1 Like
FWIW: the scores from this monitor to my servers in NL (2 x IPv4 and 3 x IPv6) are all 19.9 and 20.
So it appears to be functional, at least for a part of the pool.
1 Like
Cool thanks for checking. Btw I don’t recall why I assume it was googles. Must have popped up as a Test/Candidate for a pooled google ntp.
Even in TW 
the local network toward twtpe3-2kg9ezv is still interesting… Two TW servers for example:
20 vs. -98.8…
2 Likes