Recommended Free Tools
To verify NTP, check both whether the system clock is synchronized and which time source it is using. A running or enabled time service alone does not prove synchronization. Use commands for the time-sync service active on your system: systemd-timesyncd or chrony on Linux, or W32Time on Windows.
What to check in an NTP status result
Look for two kinds of evidence: an explicit synchronization state and a current server or peer. A service can be active while it has no usable time source or has not synchronized. The exact fields vary by operating-system version and active time daemon.
- Synchronization state: Does the system report that its clock is synchronized?
- Source: Which server or peer is supplying time, and is it expected for this computer?
- Service state: Is the relevant time service enabled or running? This is useful context, but it is not proof of synchronization.
Check NTP status on Linux with systemd-timesyncd
On a systemd-based Linux host using systemd-timesyncd, run:
timedatectl status
timedatectl timesync-statusIn timedatectl status, check the System clock synchronized and NTP service fields when available. The synchronization field reports whether the clock is synchronized; the NTP service field indicates service state. They answer different questions.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- Stratum 1 NTP with GPS Source
- Embedded View-only Webserver with Status & Graphs
- Admin Console via USB and SSH
- JSON Encoded Raw Data for Custom Integration
- I/O Connector
timedatectl timesync-status provides details about systemd-timesyncd, including the server in use where the system and version expose it. Ubuntu documents output that can include a message such as Status: "Synchronized to time server …"; treat that as an example, not a guaranteed label on every distribution or release. For scripts, timedatectl show provides machine-readable status properties, but not every property is necessarily populated on every host. See the systemd timedatectl manual and Ubuntu’s timesyncd documentation.
Check NTP status on Linux with chrony
If the host uses chrony, run its monitoring client:
Rank #2
- Stratum 1 NTP with GPS Source
- Embedded View-only Webserver with Status & Graphs
- Admin Console via USB and SSH
- Optional Dual Redundant Power Inputs - DC & PoE
- JSON Encoded Raw Data for Custom Integration
chronyc tracking
chronyc sources -vchronyc tracking reports tracking information, including leap status. In chronyc sources -v, look for a selected source, commonly marked with *. Confirm that the selected source is one you expect. The daemon is chronyd; seeing it running does not establish that chrony has selected a useful source. AWS’s Linux troubleshooting guidance also uses these commands to check synchronization: Amazon EC2 time configuration and troubleshooting.
Chrony’s FAQ recommends configuring at least three time servers for reliable operation. This is project guidance, not a universal minimum for every small network or time-sync implementation. See the chrony FAQ.
Rank #3
- 1. GPS Satellite Time Synchronization: This NTP server receives global time signals from GPS satellites, ensuring nanosecond-level time synchronization accuracy, providing high reliability for your network equipment.
- 2. High-Precision NTP Service: Provides SNTP/NTP time synchronization with Daylight Saving Time (DST) support for finance, communications, and government.
- 3. Low Latency and High Performance: Optimized design with ultra-low network latency, ensuring multi-device sync accuracy to the millisecond level, ideal for applications where time precision is critical.
- 4.Flexible Dual-Power Deployment: Supports either AC power (wide voltage input 110V-264V) or standard PoE (IEEE 802.3af/at).
- 5. Easy-to-Use Web Management Interface: Supports easy installation and remote management. The intuitive interface makes it easy to monitor device status, configure settings, and maintain the system — ideal for IT administrators and technical teams.
Check NTP status on Windows with W32Time
Open Command Prompt and run:
w32tm /query /status
w32tm /query /source
w32tm /query /peers/status shows W32Time status, /source identifies the current time source, and /peers reports peer information. To inspect runtime settings, use w32tm /query /configuration. Microsoft describes w32tm as its preferred command-line tool for monitoring and troubleshooting W32Time; see Windows Time Service Tools and Settings.
Judge the reported source against how the computer is managed. A domain-joined Windows computer commonly synchronizes through the domain hierarchy, so an internal domain controller may be the correct source rather than a public NTP server. The expected source depends on the computer’s domain role and policy. Check status, peers, and configuration before changing policy or setting a public server manually.
Rank #4
- GPS based PTP and NTP Server
- Network Time Server
- Stratum 1 Time Source
- Includes GPS Patch Antenna and Power Supply
What to do if NTP is not synchronized
- Identify the active implementation. Determine whether the Linux system uses systemd-timesyncd, chrony, or another time daemon; on Windows, check W32Time. Do not infer synchronization from a generic service-active indicator.
- Inspect its source or peers. Use the commands for that implementation above. Check whether a source is selected and whether it is the one expected for the machine or network.
- Check the configured server and name resolution. Verify the configured server name and whether the system can resolve it in its DNS environment.
- Review service logs and network reachability. Follow the documentation for the active implementation and environment. A failed ICMP ping to AWS’s link-local time endpoint does not, by itself, prove that its time service is unavailable.
- Account for management policy. On Windows, confirm whether domain policy or the domain hierarchy determines the source before changing configuration.
A correct next step depends on the active service, configured peers, network and DNS setup, and (for Windows) domain policy. Avoid reconfiguring the host until you know which service is responsible and what source it is meant to use.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.macOS status checks
The commands above are not universal macOS instructions. Chrony’s project lists macOS as a supported platform, but that does not establish commands for checking the status of Apple’s built-in time client. Use Apple-specific documentation for the macOS version and time service in question rather than assuming Linux commands apply.
Quick Recap
Best Value
- Up to 6000 visits per second
- Local area network synchronization timing accuracy: 0.5-2ms
- Support GPS, Beidou, GLONASS, QZSS NTP v2 (RFC 1119), NTP v3 (RFC 1305), NTP v4 (RFC5905)
- Internally integrated high- timing GNSS satellite receiver
- SNTP v3 (RFC 1769), SNTP v4 (RFC 2030)
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
