Google time server issue (ntp)

[sl8]

I just found that one of my machines that used Google's time server ( time.google.com ) was getting the wrong date and time. Every time I synced, it reset the date to 2016. I changed the ntp server setting on my machine to one of the pool.ntp.org servers and it works fine (I would normally use those servers by preference, not sure why I had used Google's for this machine).

I'm not sure why "2016", seems like an unusual year to revert to. Researched a bit, found that 2016 was the year that Google first made that server available to the public, so that might be related. When they made the server public, they did warn that some computers might not like how they handle leap seconds (leap smear). Don't know if that was related my issue or not.

Long story short, if you notice one of your devices' time is way off, might want check to see if it's using Google's time server.

[cos dem]

1. Could be in the GPS receiver that feeds it.

I’ve seen multiple receivers have problems at different “magic” dates due to rollover insidee the receiver, or in the signal itself. For example: https://www.orolia.com/will-your-network-time-servers-be-affected-by-the-september-2022-delayed-gps-rollover/

[sl8]

3. Interesting, thanks. nt

[liberaltrucker]

2. I use time.gov

Never had a problem.