linux-audit explains "One of the better examples is networks relying on the authentication protocol Kerberos. If your system time is not correct, you may not be able to authenticate. This is because granted tickets have a built-in protection against timing attacks. While you may not be an attacker, the system will refuse to work when it finds requests being from the past or future."
which I knew. Nothing nefarious here.
This site lists a set of daemon woes that could shut timesync down:
False tickers, stratum 13, 'unreliable sources', and 'time out of sync.'
Doesn't tell me much, though.
What shut down systemd-timesyncd.service?
It wasn't me or sudo I know that.
Do these things fall out of whack sometime? edit: spelled daemon wrong