Systemd-timesyncd uses SNTP. SNTP is designed for desktop or embedded systems for a reason. It's more a convenience of not having to set your clock, or not havi

Systemd-timesyncd uses SNTP. SNTP is designed for desktop or embedded systems for a reason. It's more a convenience of not having to set your clock, or not having much resources. Accuracy: 100ms, no clock slewing. Try to correlate your logs with that, or run any distributed applications. https://unix.stackexchange.com/questions/305643/ntpd-vs-systemd-timesyncd-how-to-achieve-reliable-ntp-syncing https://unix.stackexchange.com/questions/305643/ntpd-vs-syst... https://github.com/coreos/bugs/issues/391 https://github.com/coreos/bugs/issues/391 Talking about attack vectors: SNTP has no no authentication, so you can practically set the clock on a server, if you have sufficient network access. That's fine for me on my laptop, but I don't see much point favouring well established solutions for saving a couple of MB RAM on a server.