Time server – Using NTP for Synchronisation

A time server is a generic term for a device that receives and distributes time.  Time servers are available across the Internet or dedicated devices can be bought that offer higher accuracy and more security.

Whilst many manufacturers produce time server devices and other synchronisation tools they all have one thing in common in that they all utilise Network Time Protocol (NTP).

Whilst NTP is not the only time synchronisation software available it is used in the vast majority of synchronisation tools with some 99% of time synchronisation being conducted using NTP. NTP is a protocol used by everyone from NASA to NASDAQ and owes much of its dominance or the time synchronisation market to the dedicated team that continue to update, upgrade and develop NTP (many of whom do not get paid).

NTP is in fact almost as old as the Internet itself having been unveiled as early as 1979. It was developed by Professor David Mills and his team from Delaware University who continue to update and develop it alongside hundreds of dedicated hobbyists referred to as the Internet timekeepers.

NTP is now on version 4 and versions of NTP are included as standard with most operating systems allowing any Windows or Linux computer to run as a time server. However, for those serious about time synchronisation or wanting to keep a network secure there is no real substitute than a dedicated time server that can distribute time sent directly from an atomic clock using NTP.

Time server – Synchronisation Methods

A time server is an essential piece of equipment responsible for ensuring all devices on a computer network are running the same time. Most time servers are dedicated devices that receive a time signal, normally UTC (Coordinated Universal Time), and distribute it to all devices on a network.

Most time servers use the Internet protocol NTP (Network Time Protocol) to synchronise all devices and are often referred to as NTP servers. NTP distributes a single time source throughout the network which is normally a UTC source (Coordinated Universal Time).

There are several places a time server can receive a time signal from. The internet is an obvious source for many although online time sources are not very accurate, can be too far away to give any useful precision, and more importantly are not secure being as they are external to the firewall.

As a dedicated time server is an external device they are extremely secure and impossible for malicious users to tamper with. Dedicated time server can receive a time signal from two sources the GPS network (Global Positioning System) , a highly accurate method and available everywhere on the globe with a good view of the sky; or the specialist long wave radio transmissions broadcast by national physics laboratories.

In Europe the two main radio transmissions are the UK’s MSF signal broadcast by NPL (National Physical Laboratory) in Cumbria, England and the German DCF-77 broadcast near Frankfurt.

These long wave signals are also highly accurate and can be picked up in most neighbouring countries too. The USA has a similar system called WWVB,  transmitted by the National Institute for Standards and Technology (NIST) from Boulder, Colorado.

Time Server – Suppliers

Here is a list of links to  some of the most reputable time server manufacturers and suppliers from all over the world by country of origin.

UK
France
Germany
Italy
Spain
Poland
North America
Middle East

Time Server – FAQS

What is a time server?

A time server is a hardware device that distributes a single time source amongst a network to ensure all computers and devices are synchronised

What is NTP?

Network Time Protocol is a set of software instructions designed to distribute time across computers. NTP uses a complex algorithm to work out d inaccuracies and compensates for them by advancing or retarding the system clock.

What is UTC?

Coordinated Universal Time (UTC) is the offical global timescale. It is used by computer networks throughout the world. It is based on the time told by atomic clocks but compensates for the slowing of the Earth’s rotation by adding Leap Seconds, this also keeps it inline with GMT (Greenwich Meantime) sometimes referred to as UT1.

How does a time server receive UTC?

UTC can be received by either tuning in to a national time and frequency broadcast on long-wave administered by national physics laboratories, although not every country has one. Alternatively as GPS satellites (Global Positioning System) all carry an onboard atomic clock which transmits timing information this can be used also as a timing source for network time servers.

Can’t I use the Internet as a timing source?

You can, and there are many sources of UTC time on the Internet but very few offer any useful accuracy and for those that do the distance away can cause a drop-off in precision. More importantly, Internet time sources are exterior to your firewall and therefore a port needs to be left open to ensure communication, this can be taken advantage of by malicious users. Also Internet timing sources can’t be authenticated; authentication is a security measure that ensures that a timing reference is what it says it is.

Which method is best for me a radio referenced time server or one that utilises the GPS network?

This depends on location. While GPS signals are available everywhere on the planet the antennas do have to have a clear view of the sky to receive the signal, alternatively radio transmissions are limited in their availability although where available the signals can be received indoors.

How accurate are time servers?

A radio referenced network time server can provide UTC time to an accuracy of 100 microseconds, while the GPS network can fare even better with accuracies of a few milliseconds reasonably possible.

Time Server – The need for a reliable time source

A time server is a necessary part of any computer network. Time servers receive an authoritative time source that they then distribute amongst all devices on a network. Most time servers use a protocol such as NTP (Network Time Protocol) to distribute the single time source to all devices.

The accuracy of a time server depends entirely on the accuracy of the time source that it uses. Most networks require a UTC time source (coordinated universal time). UTC is a global timescale based on International atomic clock time (TAI) and used throughout the globe. Utilising UTC means that a computer network can be synchronised to the exact same time as a network on the other side of the globe allowing precise communications and time sensitive transactions to take place.

A time server can receive a UTC time source from only three places: the Internet, via a radio transmission or the GPS network.

The internet is by far the most commonly used source of UTC time. There are over a thousand time servers all claiming to relay UTC time. However, in surveys, less than half of these internet time sources are accurate and those that are, can be too far away to provide and real use as a timing source.

Using an internet timing source will also leave a computer network vulnerable. The hole left in the firewall to access the timing source can be used by malicious users and the built-in security method of NTP, authentication, can not ne utilised from across the Internet.

Fortunately, the two other methods of receiving UTC time offer both secure and reliable methods of receiving UTC time. The GPS network is available anywhere where there is a clear view of the sky whilst although not every country has a national time and frequency transmission, these longwave signals can be picked up by a radio referenced network time server from within a building.

Radio referenced time servers explained.

Atomic clocks use an atomic resonance frequency standard as their timekeeping element and are by far the most accurate chronometers possible with the latest Strontium based atomic clocks boasting a precision of a less than a second lost in several hundred million years.

The clocks maintain a continuous and stable time scale called International Atomic Time (TAI). However, for civil time, another time scale, Coordinated Universal Time (UTC)which  is derived from TAI, but synchronized using leap seconds to UTC, to keep it based on the rotation of the Earth.

UTC is a global timescale that is commonly used to synchronise the clocks on computer networks allowing machines from across the globe to communicate together and conduct time sensitive applications.

Unfortunately atomic clocks are highly expensive pieces of equipment and are generally only to be found in high technology physics laboratories or onboard satellites. However, several national physics laboratories broadcast the time told by their atomic clocks via a long wave radio transmission.

These signals are commonly picked up and utilized by radio controlled wall and desk clocks and by NTP time servers (Network Time Protocol).

The transmissions from the national standards agencies maintain an accuracy of 10-9 seconds per day (approximately 1 part in 1014). MSF is the signal broadcast by National Physical Laboratory in, Anthorn, Cumbria. Other countries boast their own signals the most common being the DCF77 transmission broadcast from Mainflingen near Frankfurt, Germany and the USA’s WWVB signal broadcast from Fort Collins, Colorado.

All these times signals work in a similar way. At the start of each second the strength of the signal is either reduced by between 6 and 10 dB

Types of Dedicated Time Server

Dedicated time servers are used despite the numerous Internet time sources available. The advantages of a dedicated time server is that the device is behind a firewall so preventing any security issues, dedicated time servers can also guarantee accuracy that is just not possible over the Internet.

The dedicated time server checks the time stamp from the UTC source (Coordinated Universal Time) and uses the information to calculate if the network clocks are drifting and adds or subtracts a second to match. The time server will do this at set intervals. Most time servers utilise NTP (network time protocol) although other protocols do exist NTP is by far the most widespread.

For NTP to distribute the time it first needs a timing source and this is where the differences in dedicated time servers come in. As UTC is based on the time told by atomic clocks, it is an atomic clocks that is the source for a time servers timing reference. Atomic clocks are extremely expensive, large, and require a multitude of maintenance engineers. For this reason they are only to be found in large scale physics laboratories.

However, the time from an atomic clock can still be utilised by using either a radio clock attached to a time server or a GPS clock. A radio clock is just a simple radio receiver that picks-up the long-wave signal broadcast by several national physics laboratories. This UTC signal is not available everywhere and the broadcast can be blocked by buildings, mountains and bad weather etc.

The other type of dedicated time server utilise the signals sent by the GPS satellites (global positioning system). These signals are available literally everywhere on the globe although the only downside is that a GPS antenna needs to have a clear view of the sky and therefore ideally needs to be situated on a roof which can cause some problems if the server room is along way from the top of the building.

Some dedicated time servers can actually receive both signals; the radio and GPS. In doing so they can continue receiving time signals even if one signal fails or gets temporarily blocked.

Probably the most inexpensive time servers in the World!

Galleon Systems and their The NTS 4000 MSF S and the NTS 4000 GPS S are possibly the two least expensive time servers available anywhere.

They are simple to use NTP time servers receiving accurate time from the a radio time signal (MSF) or the GPS network and using NTP can provide this synchronised time via a Ethernet port to any computer, server, switch, etc that conforms to the Network Time Protocol V3. And unbelievably they can process 1,000 NTP requests per minute.

The identical looking units are attractive pieces of kit too:

Time Servers – Using the MSF Broadcast

Time servers are essential in keeping computer networks synchronised without them many time sensitive transactions would be impossible to conduct. Time servers work by receiving a signal timing reference and distribute it to all devices on a network using the protocol NTP (Network Time Protocol). The time signal used by most time servers comes from a UTC (Coordinated Universal Time) source. UTC is based on the time told by atomic clocks and is used globally, allowing computers from across the world to be synchronized to the same time reference.

There are three methods that time servers can receive the UTC signal from. Firstly, the internet, although unsecured and without any guarantees of accuracy Internet time references are only suitable for networks where precision and security are not a concern.

The second method is via the GPS network which is available everywhere but only where an antenna has a clear view of the sky.

The third and simplest method to receive an accurate and secure UTC time reference is to use the national time and frequency broadcasts. In the UK the National Physical Laboratory transmits the British signal from Anthorn in Cumbria. This signal, known as MSF, can be received in most places in the UK although local topography can interfere with the transmission.

To receive the MSF broadcast a radio referenced NTP time server is required. This will receive the radio transmission via 65 kHz in long wave and distribute it amongst the network.
A radio based NTP server usually consists of a rack-mountable time server, and an antenna, consisting of a ferrite bar inside a plastic enclosure, which receives the radio time and frequency broadcast. The antenna should always be mounted horizontally at a right angle toward the transmission for optimum signal strength.

Similar national timing transmissions are broadcast from other countries in the US the signal is referred to as WWVB and is broadcast by the NIST (National Institute for Standards and Technology) in Fort Collins, Colorado, other systems are broadcast in Frankfurt, Germany (DCF-77), Japan (JJY) and France ( TDF).

Using A Time Server to Maintain Precise Time on Your Computer

Computer networks rely on timekeeping for nearly all their applications, from sending an email to saving data, a timestamp is necessary for computer to keep track. All routers and switches need to run at the same rate, out of sync devices can lead to data being lost and even entire connections.

All PC’s and networking devices use clocks to maintain an internal system time. These clocks, called Real Time Clock chips (RTC) provide time and date information. The chips are battery backed so that even during power outages, they can maintain time.

However, personal computers are not designed to be perfect clocks, their design has been optimized for mass production and low-cost rather than maintaining accurate time. However, these internal clocks are prone to drift and although for many application this can be quite adequate, often machines need to work together on a network and if the computers drift at different rates the computers will become out of sync with each other and problems can arise particularly with time sensitive transactions.

For some transactions it is necessary for computers to be perfectly synchronised, even a few seconds difference between machines can have serious effects, such as finding an airline ticket you had booked had been sold moments later to another customer or you could draw your savings out of a cash machine and when your account is empty you could quickly going to another machine and withdraw it all again.

Time servers are like other computer servers in the sense they are usually located on a network. A time server gathers timing information, usually from an external hardware source and then synchronises the network to that time.

Most time servers use NTP (Network Time Protocol) which is one of the Internet’s oldest protocols still used, invented by Dr David Mills from the University of Delaware, it has been in utilized since 1985. NTP is a protocol designed to synchronize the clocks on computers and networks across the Internet or Local Area Networks (LANs).

NTP utilises an external timing reference and then synchronises all devices on the network to that time.

Often time servers are synchronised to a UTC (Coordinated Universal time) source which is the global standard time scale and allows computers all over the world to synchronised to exactly the same time. This has obvious importance in industries where exact timing is crucial such as the stock exchange or airline industry.

There are various sources that a time server can use as a timing reference. The Internet is an obvious source, however, internet timing references from the Internet such as nist.gov and windows.time can not be authenticated, leaving the time server and therefore the network vulnerable to security threats.