Finding out what the time is, is something we all take for granted. Clocks are everywhere and a glance at a wristwatch, clock tower, computer screen or even a microwave will tell us what the time is. However, telling the time has not always been that easy.

Clocks didn’t arrive until the middle ages and their accuracy was incredibly poor. True time telling accuracy didn’t arrive until after the arrival of the electronic clock in the nineteenth century. However, many of the modern technologies and applications that we take for granted in the modern world such as satellite navigation, air traffic control and internet trading require a precision and accuracy that far exceeds an electronic clock.

Atomic clocks are by far the most accurate time telling devices. They are so accurate that the world’s global timescale that is based on them (Coordinated Universal Time) has to be occasionally adjusted to account for the slowing of the Earth’s rotation. These adjustments take the form of additional seconds known as leap seconds.

Atomic clock accuracy is so precise that not even a second of time is lost in over a million years whilst an electronic clock by comparison will lose a second in a week.

But is this accuracy really necessary? When you look at technologies such as global positioning then the answer is yes. Satellite navigation systems like GPS work by triangulating time signals generated by atomic clocks onboard the satellites. As these signals are transmitted at the speed of light they travel nearly 100,000 k m each second. Any inaccuracy in the clock by even a thousandth of a second could see the positioning information out by miles.

Computer networks that have to communicate with each other across the globe have to ensure they are running not just accurate time but also are synchronised with each other. Any transactions conducted on networks without synchronisation can result in all sorts of errors.

Fort his reason computer networks use NTP (Network Time Protocol) and network time servers often referred to as an NTP server. These devices receive a timing signal from an atomic clock and distribute it amongst a network in doing so a network is ensured to be as accurate and precise as possible.

Most people have vaguely heard of the atomic clock and presume they know what one is but very few people know just how important atomic clocks are for the running of our day to day lives in the twenty first century.

There are so many technologies that are reliant on atomic clocks and without many of the tasks we take for granted would be impossible. Air traffic control, satellite navigation and internet trading are just a few of the applications that are reliant on the ultra precise chronometry of an atomic clock.

Exactly what an atomic clock is, is often misunderstood. In simple terms an atomic clock is a device that uses the oscillations of atoms at different energy states to count ticks between seconds. Currently caesium is the preferred atom because it has over 9 billion ticks every second and because these oscillations never change it makes them a highly accurate method of keeping time.

Atomic clocks despite what many people claim are only ever found in large scale physics laboratories such as NPL (UK National Physical Laboratory) and NIST (US National Institute of Standards and Time). Often people suggest they have an atomic clock that controls their computer network or that they have an atomic clock on their wall. This is not true and what people are referring to is that they have a clock or time server that receives the time from an atomic clock.

Devices like the NTP time server often receive atomic clock signals form places such as NIST or NPL via long wave radio. Another method for receiving time from atomic clocks is using the GPS network (Global Positioning System).

The GPS network and satellite navigation are in fact a good example of why atomic clock synchonization is much needed with such high level of accuracy. Modern atomic clocks such as those found at NIST, NPL and inside orbiting GPS satellites are accurate to within a second every 100 million years or so. This accuracy is crucial when you examine how something like a cars GPS satellite navigation system works.

A GPS system works by triangulating the time signals sent from three or more separate GPS satellites and their onboard atomic clocks. Because these signals travel at the speed of light (nearly 100,000km a second) an inaccuracy of even one whole millisecond could put the navigational information out by 100 kilometres.

This high level of accuracy is also required for technologies such as air traffic control ensuring our crowded skies remain safe and is even critical for many Internet transactions such as trading in derivatives where the value can rise and fall every second.

NTP homepage-  The home for the NTP Project who provides support and additional development resources for the Official Reference Implementation of NTP.

NTP Project support pages

THE NTP pool – list of public servers

NPL – The National Physical Laboratory in the UK who control the MSF radio signal.

The University of Delaware and David Mills’ information page, Professor Mills is the original inventor and developer of NTP

David Mills’ list of Public NTP Time Servers a list of public NTP servers

National Institute of Standards and Technology (NIST) who operate the USA’s WWVB radio signal

Europe’s largest supplier of NTP server related products.

Galleon UK – NTP server products for the UK

NTP Time Server .com  – one of the largest time and frequency suppliers in the United States

NTP – Wikipedia article on NTP

NTP server checker – free tool to ensure time server accuracy

Time synchronisation can be crucial for many computer networks. Correct synchronisation can protect a system from all sorts of security threats it will also ensure that the network is accurate and reliable but are dedicated NTP time server systems really necessary or can a network be run securely without a network time server?

Here are five questions to ask yourself to see if your network needs to be adequately synchronised.

1.  Does your network conduct time sensitive transactions across the internet?

If yes then accurate network time synchronisation is essential. Time is the only point of reference a computer has to identify two events so when it comes to a transaction across the internet such as sending an email, if it comes from an unsynchronised network, it may arrive before it was technically sent. This may lead to the email not being received as a computer cannot handle negative values when it comes to time.

2. Do you store valuable data?

Data loss is another ramification of not having a synchronised network. When a computer stores data it is stamped with the time. If that time is from an unsynchronised machine on a network then a computer may consider the data already saved or it may overwrite new data with older versions.

3. Is security important to your business and network?

Keeping a network secure is essential if you have any sensitive data on the machines. Malicious users have a myriad of ways of gaining access to computer networks and using the chaos caused by an unsynchronised network is one method they frequently take advantage of. Not having a synchronised network may mean it is impossible to identify if your network has been hacked into too as all records left on log files are time reliant too.

UTC – Coordinated Universal Time (from the French: Universel Temps Coordonné) is a global timescale based on Greenwich Meantime (GMT – from the Greenwich Meridian line where the sun is above at 12 noon). But accounts for the natural slowing of the Earth’s rotation. It is used globally in commerce, computer networks via a NTP server, air-traffic control and the World’s stock exchanges to name but a few of its applications.

UTC is really the only solution for time synchronisation needs. While it is just as possible to synchronise a computer network with an NTP server to a time other than UTC it is pointless. As UTC is utilised by computer networks all across the globe by using a UTC time source that means your network can synchronise with every other network in the world that is synchronised to UTC.

UTC is most commonly received from across the Internet, however, this can only be recommended for small network users where either accuracy or security is an issue. An Internet based UTC source is external to the firewall so will leave a potential hole for malicious users to exploit.

Two secure methods of receiving UTC are commonly available. These are either the GPS network (Global Positioning System) or specialist radio transmission broadcast on long wave from several of the world’s national physics laboratories. The two methods have both advantages and disadvantages which need to be ascertained before a method is selected.

A radio transmission such as the UK’s MSF, the German DCF-77 or the USA’s WWVB signal are vulnerable to local topography although many of these signals can be picked up indoors. Whilst not every country transmits a UTC radio signal around the neighbouring countries that do it is possible to still receive it.

GPS on the other hand is available literally anywhere on the globe. The signal comes directly from above and as long as the antenna has a good clear view of the sky it can be received anywhere. However, as the antenna has to be on a roof looking up this can have logistical problems (particularly for very tall buildings).

Specialist dedicated network time servers are available that can actually receive both methods of UTC but whether using GPS or a radio transmissions synchronisation of a network to within a few milliseconds is possible.

We may think of their being only one time and therefore one timescale. Sure, we’re all aware of time zones where the clock has to be pushed back an hour but we all obey the same time surely?

Well actually we don’t. There are numerous different timescales all developed for different reasons are too numerous to mention them all but it wasn’t until the nineteenth century that the idea of a single timescale, used y everybody came into effect.

It was the advent of the railway that provoked the first national timescale in the UK (Railway time) before then people would use noon as a basis for time and set their clocks to it. It rarely mattered if your watch was five minutes faster than your neighbours but the invention of the trains and the railway timetable soon changed all that.

The railway timetable was only useful if people all used the same time scale. A train leaving at 10.am would be missed if a watch was five minutes slow so synchronisation of time became a new obsession.

Following railway time a more global timescale was developed GMT (Greenwich Meantime) which was based on the Sun’s position at noon which fell over the Greenwich Meridian line (0 degrees longitude). It was decided during a world conference in 1884 that a single world meridian should replace the numerous one’s already in existence. London was perhaps the most successful city in the world so it was decided the best place for it.

GMT allowed the entire world to synchronise to the same time and while nations altered their clocks to adjust for time-zones their time was always based on GMT.

GMT proved a successful development and remained the world’s global timescale until the 1970’s. By then that atomic clock had been developed and it was discovered in the use of these devices that Earth’s rotation wasn’t a reliable measure to base our time on as it actually alters day by day (albeit by fractions of a second).

Because of this a new timescale was developed called UTC (Coordinated Universal Time). UTC is based on GMT but allows for the slowing of the Earth’s rotation by adding additional ‘Leap Seconds’ to ensure that Noon remains on the Greenwich Meridian.

UTC is now used all over the World and is essential for applications such as air traffic control, satellite navigation and the Internet. In fact computer networks across the globe are synchronised to UTC using NTP time servers (Network Time Protocol). UTC is governed by a constellation of atomic clocks controlled by national physics laboratories such as NIST (National Institute of Standards and Time) and the UK’s NPL.

3. Security Breaches:

When networks are not synchronised log files are not recorded properly or in the right order which means that hackers and malicious users can breach security unnoticed. Many security software programs are also reliant on timestamps with anti-virus updates failing to happen or scheduled tasks falling behind. If your network controls time-sensitive transactions then this can even result in fraud if there is a lack of synchronisation.

4. Legal Vulnerability:

Time is not just used by computers to order events it is used in the legal world too. Contracts, receipts, proof-of-purchase are all reliant on time. If a network is not synchronised then it becomes difficult to prove when transactions actually took place and it will prove difficult to audit them. Furthermore, when it comes to serious matters such as fraud or other criminality a dedicated NTP server or other network time server device synchronised to UTC is legally auditable, its time can not be argued with!

5. Company Credibility:

Succumbing to any of these potential hazards can not just have devastating effects on your own business but also that of your clients and suppliers too. And the business grapevine being what it is any potential failing on your part will soon become common knowledge amongst your competitors, customers and suppliers and be seen as bad business practices.

Running a synchronised network adhering to UTC is not difficult. Many network administrators think that synchronisation just means an occasional time request to an online NTP time source; however, doing so will leave a system just as vulnerable to fraud and malicious users as having no synchronisation. This is because to use an Internet time source would require leaving a permanent port open in the firewall.

The solution is to use a dedicated NTP time server that receives a UTC time source from either a radio transmission (broadcast by national physics laboratories) or the GPS network (Global Positioning System). These are secure and can keep a network running to within a few milliseconds of UTC.

Most businesses these days rely on a computer network. Computers in most organisations conduct thousands of tasks a second, from controlling production lines; ordering stock; preparing financial records and communicating with computers on other networks – often from the other side of the world.

Computers use just one thing to keep track of all these tasks: time. Timestamps are the computers only reference for when an event or task occurs in relation to other events. They receive time in the form of timestamps and they measure time in periods of milliseconds (thousandth of a second) as they may conduct hundreds of processes each second.

A global timescale known as UTC (Coordinated Universal Time) has been developed to ensure computers from different organisations all over the world can synchronise together. So what happens if the clocks on computers don’t coincide with each other or with UTC?

The consequences of running a network with computers that are not synchronised can be disastrous. Here are five reasons why all businesses need adequate network synchronisation using a NTP server (Network Time Protocol) or other network time server device.

1. Tasks fail to happen:

When computers are running at different times, events on different machines can fail to happen as often a PC may assume an event on another machines has already happened if the time for that event has passed according to its own clock. And what is worse, when one task fails it has a knock-on effect with other tasks failing to happen and in turn causing further tasks to fail.

2. Loss of Data:

When tasks fail to happen it soon gets noticed but when networks are not synchronised data that is meant to be kept can quite easily be lost and it can go unnoticed for quite a while. Data can be lost because storage as and retrieval is also reliant on time stamps.

The atomic clock is the culmination of mankind’s obsession of telling accurate time. Before the atomic clock and the nanosecond accuracy they, employ time scales were based on the celestial bodies.

However, thanks to the development of the atomic clock it has now been realised that even the Earth in its rotation is not as accurate a measure of time as the atomic clock as it loses or gains a fraction of a second each day.

Because of the need to have a timescale based somewhat on the Earth’s rotation (astronomy and farming being two reasons) a timescale that is kept by atomic clocks but adjusted for any slowing (or acceleration) in the Earth’s spin. This timescale is known as UTC (Coordinated Universal Time) as employed across the globe ensuring commerce and trade utilise the same time.

Computer networks use network time servers to synchronise to UTC time. Many people refer to these time server devices as atomic clocks but that is inaccurate. Atomic clocks are extremely expensive and highly sensitive pieces of equipment and are only usually to be found in universities or national physics laboratories.

Fortunately national physics laboratories like NIST (National Institute for Standards and Time – USA) and NPL (National Physical Laboratory – UK) broadcast the time signal from their atomic clocks. Alternatively the GPS network is another good source of accurate time as each GPS satellite has onboard its own atomic clock.

The network time server receives the time from an atomic clock and distributes it using a protocol such as NTP (Network Time Protocol) ensuring the computer network is synchronised to the same time.

Because network time servers are controlled by atomic clocks they can keep incredibly accurate time; not losing a second in hundreds if not thousands of years. This ensures that the computer network is both secure and unsusceptible to timing errors as all machines will have the exact same time.

The atomic clock is the culmination of mankind’s ability to keep time that has spanned several millennia. Humans have always been preoccupied with keeping track of time ever since early man noticed the regularity of the celestial bodies.

The sun, moon, stars and planets soon became the basis for out timescales with periods of time such as years, months, days and hours based solely on the regulation of the Earth’s rotation.

This worked for thousands of years as a reliable guide to how much time has past but over the last few centuries humans have strode to find even more reliable methods for keeping track of time. Whilst the Sun and celestial bodies were an affective way sundials didn’t work on cloudy days and as the days and night s altered during the year only noon (when the sun is at its highest) could be reasonably relied upon.

The first foray into an accurate timepiece that was not reliant on celestial bodies and was not a simple time (such as a candle taper or water clock) but actually told time over a prolonged period was the mechanical clock.

These first devices dating as far back as the twelfth century were crude mechanisms using a verge and foliot escapement (a gear and lever) to control the ticks of the clock. After a few centuries and a myriad of designs the mechanical clock took its next step forward with the pendulum. The pendulum gave clocks their first true accuracy as it controlled with more precision the ticks of the clock.

However, it wasn’t until the twentieth century when clocks entered the electronic age did they become truly accurate. The digital and electronic clock had its ticks controlled by using the oscillation of a quartz crystal (its changed energy state when a current is based through) which proved so accurate that rarely a second a week was lost.

The development of atomic clocks in the 1950’s used the oscillation of a single atom which generates over 9 billion ticks a second and can maintain precise time for millions of years without losing a second. These clocks now form the basis of our timescales with the entire world synchronised to them using NTP servers, ensuring wholly accurate and reliable time.