top of page

NTP or PTP: which time protocol does your network need?

6 hours ago
2 min read

Every network needs a clock that all systems rely on. Servers, firewalls, cameras, PLCs, and wall clocks must maintain the same time; otherwise, log files will be incorrect, processes will fall out of sync, and it will be impossible to determine retrospectively what happened when. Two protocols exist for this time distribution: NTP and PTP. In this article, you will read about the difference and how to choose.

What is NTP?

NTP (Network Time Protocol) is the standard protocol for time synchronization in IT networks. Virtually every operating system, switch, and network camera supports it. A device periodically requests the time from an NTP server and corrects its own clock, taking into account the latency over the network.

In a well-configured local network with its own time server, an accuracy of about a millisecond or better is common. Via the internet, with public time servers, the deviation is larger and less predictable. For most office, hospital, and school networks, NTP is more than sufficient.

What is PTP?

PTP (Precision Time Protocol, IEEE 1588) is designed for applications where a millisecond is too coarse. Because timestamps are set in the network hardware rather than in the software, accuracy well below a microsecond is achievable. However, the network must cooperate for this to work: switches that support PTP (as a boundary clock or transparent clock) remove the unpredictable delay from the network path.

PTP has profiles for specific sectors, such as power grids and substations, telecommunications, and broadcast and audio-over-IP. The profile determines, among other things, how often messages are sent and which network settings apply.

The difference in one overview

  • Accuracy: NTP on the local network approximately one millisecond or better; PTP with hardware timestamps well under a microsecond.

  • Network: NTP works on any existing network; PTP requires PTP-compatible switches for the highest accuracy.

  • Support: NTP is found in virtually all equipment; PTP primarily in industrial, telecom, and broadcast equipment.

  • Application: NTP for IT, logging, security, and clocking; PTP for automation, energy, telecom, broadcast, and trading platforms.

Which one do you need?

Choose NTP if you want servers, workstations, network equipment, cameras, and wall clocks to run synchronously and make log files reliable. This applies to most organizations.

Choose PTP if the equipment itself requires microsecond accuracy: protection relays in substations, mobile networks, audio and video studios with AES67 or SMPTE ST 2110, measurement systems, or high-speed trading environments.

In practice, it is often both. A modern time server supplies NTP to the office network and PTP to the systems that need it, from the same time source.

The time source counts just as much.

A protocol divides time but does not create it. A professional time server retrieves the time from satellite signals (GNSS, such as GPS and Galileo) or another independent reference, and maintains it using a stable oscillator in the event of failure. Also view our NTP and PTP time servers .

Need advice?

BerdoTime supplies NTP servers and PTP grandmasters from Mobatime and advises on accuracy, redundancy, and network architecture. Call 085-4000265 or email info@berdo.nl .

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
Network clocks
DTS new photo.jpeg
data network ntp server
bottom of page