It seems to constantly reporting a score of -0.1, but on pool.ntp.org: Statistics for 126.96.36.199 the recentmedian score is
fine with ~20, the legacy score shows quite often different values. This
is an IP address which has a long history of often being difficult to
reach from the previous monitoring system. It seems that some of my ISPs
transit carriers are doing some filtering / DDoS protection. This can be
seen with around half of the scores in “testing” being negativ.
Could it be, that the score in the json output still does use “old” (or
even stale) data? The IP 188.8.131.52 had a too low score since 13th
March 2023, so before the new monitoring system went into operation.
How odd! Skimming the code I think I see the bug, maybe, but I don’t understand how it ever worked – many of the relevant bits are ~10 years old. I’ll see if I can fix it this weekend. A github issue referencing this thread would be welcome.
Thanks @fab23 – it should be fixed now (on the beta site and production site both).
The old monitoring system created a history with a NULL monitor_id for the scorer. What happened was that you before got the last value from the old scorer (until that expired into the archive history which isn’t currently available through the API). I fixed it so if you don’t specify a monitor_id it’ll choose the ‘recent median’ scorer.