ntp0 slow?

Has anyone else noticed that ntp0.zen.co.uk is a little over a second slow atm?

time.windows.com is spot on.

Not a big deal but I've just got meself a radio controlled watch and am going around checking everything at the mo'

just over 1 second... wouldn't bother me as long as its not more than 10 seconds out.

Blackmesa8

In the UK it would be a good move to use uk.pool.ntp.org ...

Thanks for that, my new watch and my PC are now in sync

This probably isn't a big deal to most people but I suffer from OCD and accurate time is one of my little foibles

Out of interest, how do you know that ntp0 is slow and that it's not time.windows.com that's fast ?

Remember a man with one watch knows the time. A man with two isn't quite so sure ...

Well my watch syncs with the time signal from Mainflingen in Germany, other radio controlled clocks around my house sync with the MSF signal from Anthorn and they all agreed. Just for good measure I checked with the BT talking clock as well

OCD is a curse at times

Don't worry on the OCD front. My wife and I love clocks. At one point in time I had 26 different time sources to adjust at the GMT/BST change over. I also used to try to keep them all reasonably close too. Now that we have kids we spend too much time tidying up after them to worry about how accurate our clocks are :-)

ntp0.zen.co.uk is giving the correct time now.

Not sure if it's been adjusted by somebody or just corrected itself but it is, at least by me, much appreciated

We made no changes. All our investigations showed that NTP0 was giving out the correct time. We cross checked it against many other NTP time sources and it was within milliseconds of their time. There was also nothing in it's logs indicating that it had drifted in any manner.

Hmm, something curious has gone on.

Whilst looking at one of our servers that wasn't syncing to ntp0, but to pool.ntp.org it had inserted a leap second last night at 23:59:60. Ntp0 however didn't. When I fixed the config on the server to sync to both pool.ntp.org (this time a different server) and ntp0.zen.co.uk it showed both as being 1 second offset from its time.

It would look like our server had seen a spurious leap second from 20six.co.uk.

On mentioning this to our Principal Engineer who also keeps an ear to the ground on time issues, he located the IERS document :

IERS Bulletin C

Which states that there would be no positive leap second at the end of June 2008 - so the leap second that we'd seen was indeed spurious. That is rather concerning as how far round has that error propgated ?