This same NTP server is a virtual machine hosted in Azure and remained the entire year with fixed score at 20, but since day 22 the score began to be reduced due to the high offset.
Due to the behavior of the monitoring station graph, the score appears to be gradually reduced until the NTP service resynchronizes the time with the time source, as if something were causing the clock to be delayed in a short period of time.
I’m using three distinct stratum 1 time sources.
The test result made from another server using the ntpdate -q command shows an offset of -0.034593.
I also use a DNS and HTTP services monitoring application called Uptimerobot, which has shown a considerable increase in latency of requests in recent days.
Could anyone tell me what I can do to try to solve this? I haven’t made any modifications to the server recently.