Why is Apple Time Server wrong in Europe?

I am using Apple’s Europe time server on my Macs at home (time.europe.apple.com).


Normally, the time on my MacBook is within a second or so to the time shown on my bedside clock that uses the NPL radio time signal from Cumbria to set its accuracy (aka the 'Rugby signal')


However, today, the two clocks were two minutes apart - so the difference has jumped from a couple of seconds max to around 120.


As a check, I compared the clock with a GShock watch that I have, that also uses the NPL signal - and they were completely in sync. I then set the radio clock to match the Apple time, and when it re-synchronised with the NPL signal, it jumped back to the two minutes difference.


Does anyone have any idea why the two time signals have diverged so much? As I have two devices using the NPL radio signal, that’s the one I trust, so am pretty sure it is the Apple time server that is wrong.

MacBook

Posted on Mar 7, 2019 6:51 AM

Reply

Similar questions

13 replies

Mar 8, 2019 8:08 AM in response to Buster_From_Oak_Park

Please see - https://support.ntp.org/bin/view/Servers/RulesOfEngagement where it says -


As the load on the hosts supporting NTP primary (stratum 1) time service is heavy and always increasing, clients should avoid using the primary servers whenever possible. In most cases the accuracy of the NTP secondary (stratum 2) servers is only slightly degraded relative to the primary servers and, as a group, the secondary servers may be just as reliable.

Mar 8, 2019 10:36 AM in response to John Lockwood

Look! A butterfly!


Ok... while it was fascinating to watch that straw man float on by, it did nothing to answer the specific question begged. Let me rephrase the question : If the system is being taxed, why allow any general access ?


Follow up question : why is the information being published in public at all ?


Clear enough? It rings more than a little hollow that the sole means of solving an access problem is to be begging pretty please to stop it while distributing the access information to the public.

Mar 7, 2019 8:57 AM in response to Jonathan Ratty

Hi, Jonathan Ratty !


As an alternative you could use a much more stable, reliable source: The US Navy. They maintain a pair of atomic clocks which are ever-so-imaginatively named Tick and Tock. Replace your Apple time server information with:


tick.usno.navy.mil

tock.usno.navy.mil


Even over the internet to Europe it should be under a second in latency, so accurate enough for your needs.


I hope this helps you, and good luck !

Mar 8, 2019 3:23 AM in response to Jonathan Ratty

Firstly the individual Mac does not constantly run a sync to the (in your case) time.europe.apple.com server. So your Mac may have drifted since the last sync. As leyroydouglas mentions you can force an update via a terminal command, you can also force an update by turning network time sync off and then back on in the System Preference option. Syncs would normally occur at boot/login, I am not sure how often after that if you don't logout or reboot it would occur.


With regards to which server to use -


Typically operators of Stratum 0 or Stratum 1 servers prefer 'ordinary' users not to sync via their servers. These core time servers are intended for say Stratum 2 servers to sync to and then users to sync to the Stratum 2 servers. This is because if 1 billion people (not an exaggeration) were to all try to sync to the handful of Stratum 0 and 1 servers they would clearly be overloaded.


As dialabrain says a few milliseconds difference is not an issue to normal people. :)


In larger organisations it is more typical for say their Windows Active Directory Server to sync to (likely) stratum 2 server and then when client computers (Mac or Windows) are 'bound' to Active Directory they are automatically configured to sync to the Active Directory Server. This ensures that internally the client computers and server are in reasonably close synchronisation and avoids hundreds or thousands of clients are not all directly bombarding the major time servers.


Apple's OpenDirectory is supposed to do something similar but is sadly not enterprise grade anymore. :(


It is supposed to be possible to 'advertise' a network time server on your local network via DHCP using option code 42 but I am dubious that macOS obeys this. See - http://www.networksorcery.com/enp/protocol/bootp/option042.htm

Mar 8, 2019 8:01 AM in response to John Lockwood

If this is truly the case, then perhaps you could explain to the viewing audience why organizations like the US Navy (who, arguably, administer the most accurate Stratum 0 server on the planet) publish that server information in public. Logic would seem to say, if you are accurate, this information would be on a tightly controlled access, need-to-know basis to provide - at the very least - a basic means of controlling traffic. One would think the Stratum 0 servers would be on an IP and MAC address lockdown if nothing else.


After all - the US government (see: US Army) doesn't publish a publicly accessible map of the interior of Fort Knox, right?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Why is Apple Time Server wrong in Europe?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.