In the wake of a recently completed infrastructure move, there currently still are some kinks that need ironing out, such as this one.
I.e., you are not alone with this issue, others experience it as well, see log of one of my monitors below.
Also check the graph on number of checks executed by monitors per second. If you go to the weekly view, you’ll see that it was much more stable, and that there were more checks (around 14000/s).
I believe Ask is already aware of this, else this thread will make him aware (he asked for feedback if things are amiss despite all the care taken during the move).
On one of my monitors:
Apr 28 18:05:47 vps-par4 ntppool-agent[17824]: level=WARN msg="local-check failure" env=prod ip_version=v6 server=uklon5-ntp-002.aaplimg.com ip=2a01:b740:a16:4000::31 err="network: i/o timeout" trace_id=95c50f2ca4b84a7158ecc124509d55e7 span_id=84aab6b6749cfc93
Apr 28 18:06:23 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"
Apr 28 18:07:01 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"
Apr 28 18:07:41 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"
Apr 28 18:08:25 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"
Apr 28 18:08:59 vps-par4 ntppool-agent[17824]: level=WARN msg="local-check failure" env=prod ip_version=v6 server=time.nist.gov ip=2610:20:6f97:97::4 err="offset too large: -16.846172ms" trace_id=0fd0f94d5c17799c8bc3036c11043544 span_id=1cc1cc813f717ea4
Apr 28 18:09:10 vps-par4 ntppool-agent[17824]: level=WARN msg="local-check failure" env=prod ip_version=v6 server=uklon5-ntp-002.aaplimg.com ip=2a01:b740:a16:4000::31 err="network: i/o timeout" trace_id=0fd0f94d5c17799c8bc3036c11043544 span_id=1cc1cc813f717ea4
Apr 28 18:09:40 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"
Apr 28 18:10:52 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"
Apr 28 18:12:01 vps-par4 ntppool-agent[17824]: level=ERROR msg="batch processing" env=prod ip_version=v6 monitor_ip= err="SubmitResults: deadline_exceeded: Post \"https://api.mon.ntppool.dev/monitor.v2.MonitorService/SubmitResults\": net/http: timeout awaiting response headers"