GPS time and UTC are different scales, and NTP does not remove that distinction. A GPS receiver supplies a highly stable reference; NTP distributes time from that reference (or another source) through a server hierarchy. To display civil time correctly, the receiver, NTP daemon, operating system and applications must apply the relevant leap-second information and use a consistent policy—either an explicit UTC leap or a documented leap smear.
What must be synchronized: GPS time, UTC and TAI
UTC is the civil time scale used by national laboratories and time services. It is based on atomic time but is occasionally adjusted with a leap second so that civil time remains close to Earth rotation. A leap second changes the relationship between a clock reading and UTC; it does not change the physical frequency of the clock’s oscillator.
As an Amazon Associate I earn from qualifying purchases.
GPS time is a separate, continuous scale. It is syntonic with International Atomic Time (TAI) and has a fixed offset of −19 seconds from TAI. The Network Time Foundation’s “The NTP Timescale and Leap Seconds” reference, last updated October 2, 2026, puts it this way: “The GPS timescale is syntonic with TAI, but at a fixed time offset of -19 s from TAI, apparently because the final system design review was in 1980.” GPS therefore does not automatically equal the UTC shown on a phone or wall clock. A receiver normally uses current leap-second information to convert its GPS reading into UTC for external output.
The number of seconds between GPS time and UTC is not a permanent constant: it changes when UTC gains a leap second. A receiver that reports only a continuous GPS count, without applying the applicable leap history, can be precise yet still label civil time incorrectly.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
How NTP turns a reference into network time
Network Time Protocol (NTP) distributes time; it does not require every computer to have its own atomic or satellite reference. A primary server obtains time from a reference clock, radio signal, laboratory service or GPS receiver. Secondary servers synchronize to those primaries, and workstations, applications and other devices synchronize to the secondary servers.
A GPS timing receiver with a pulse-per-second (PPS) output is one possible local reference. The PPS edge gives the server a precise timing event, while the receiver’s serial or network message supplies the corresponding date and time. Reference-clock software must understand that receiver’s data, associate the PPS edge with the correct second, and convert GPS time to UTC when required. NTP then advertises the result to the rest of the network.
This hierarchy means that seeing satellites somewhere on a site is not enough to guarantee correct timestamps. The whole chain matters: antenna reception, receiver firmware, PPS wiring, driver, NTP daemon, operating-system clock discipline, upstream configuration and the policy used by clients.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat happens when UTC receives a leap second
Advance notice is essential
NTP needs to know about a pending leap before the event. The NTP 4.2.8 documentation says leap information can arrive through IERS bulletins, national time-and-frequency signals, GPS signals, NTP packets or a leap-seconds file. A reference clock can pass the announcement to a primary server, which can propagate it through the NTP subnet. Support varies by reference clock and driver, so an NTP server being synchronized does not by itself prove that it has received a valid leap announcement.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
The NTP 4.2.8 implementation documentation used here was last updated November 23, 2022. Its behavior should not be assumed for every later daemon, operating system or clock driver; administrators should verify the documentation and configuration for the exact software in use.
Applying the change
With precision-time kernel support enabled, NTP can arm the kernel to apply the announced leap at the end of the relevant UTC day. Without that support, the documented fallback adjusts clock behavior so that one second is effectively repeated or stalled. The visible result depends on the operating system and implementation, but the important requirement is that all cooperating systems know whether they are representing the UTC leap directly.
A leap second is not a reason to reset a server’s clock manually. Manual corrections can create a larger discontinuity, confuse applications and leave the NTP state inconsistent. Let the configured time service receive the announcement and perform the supported transition.
Leap step versus leap smear
| Policy | What the clock does | When it fits | Main risk |
|---|---|---|---|
| Explicit UTC leap | Represents the leap at the specified instant, using kernel or daemon support. | Systems whose timestamps must track UTC directly and can coordinate the event. | Different operating systems and drivers may implement the transition differently if not tested and configured together. |
| Leap smear | Spreads the adjustment over a time window instead of inserting an abrupt leap second. | Environments that control all participating clocks and can document a common smear schedule. | During the window, smeared time temporarily differs from unsmeared UTC; mixed timestamps can disagree. |
The NTP leap-smear REFID proposal describes indicating in an NTP packet that the supplied time already contains smear correction. A smeared clock is not simply “wrong”; it follows a different time policy during the interval. The operational error occurs when one system assumes unsmeared UTC and another supplies smeared time without accounting for the difference.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Choose one policy for systems that exchange timestamps, logs, certificates, transactions or telemetry. Record the policy in operational documentation, monitoring and data schemas. Do not place a smeared server beside an unsmeared server in the same pool unless clients can identify and handle the distinction.
Setting up an ordinary workstation or server
- Use a maintained NTP service. Configure the operating system’s supported time-synchronization service or an administrator-approved NTP daemon rather than relying on ad-hoc scripts.
- Select trustworthy upstreams. Use multiple reachable sources where practical, and check that they follow the same leap policy. A source that is reachable but has stale leap data can still produce a bad civil-time result.
- Keep leap data current. Permit the daemon to receive leap information through its configured NTP sources, reference clock or leap-seconds file. Confirm that file updates are part of normal system maintenance.
- Verify status before an event. Check which source is selected, whether the clock is synchronized, whether a leap is pending, and whether the kernel or daemon reports leap-processing support. Exact command names and status fields differ by operating system and NTP implementation.
- Check application assumptions. Logging, databases, distributed systems and monitoring may assume UTC, a monotonic clock or a smear policy. Use a monotonic clock for elapsed-time measurement; use synchronized wall time for timestamps that must be compared across machines.
- Observe the transition. During a scheduled leap, monitor offsets, source changes, daemon messages and application errors. Do not manually step clocks unless the vendor’s documented recovery procedure requires it.
The available documentation describes the mechanisms, not identical behavior on every current operating system. Treat version, kernel support and driver behavior as configuration items to verify, not as universal guarantees.
Building a local GPS-backed NTP server
A local GPS reference can reduce dependence on an external network path, but it adds hardware and integration work. The evidence supports the category of a GPS receiver with PPS output; it does not establish accuracy, reliability or suitability for any particular current model.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Check these requirements first
- PPS interface: Confirm that the receiver exposes a usable pulse and that the server’s hardware and operating system can timestamp it.
- Driver compatibility: Verify that the NTP reference-clock driver supports the receiver’s message format and PPS device.
- Leap notification: Establish how the receiver reports pending leap information and how that information reaches the NTP daemon.
- Antenna installation: Provide a suitable view of the sky, stable power and a protected cable run. GPS visibility alone does not validate the time conversion.
- Fallback sources: Decide what happens if the antenna, receiver or PPS input fails. A local server should not silently serve stale time.
Understand the conversion path
The receiver’s continuous GPS scale must be interpreted with the current leap-second relationship before the server presents UTC to clients. The PPS signal improves the timing of the second boundary; it does not, by itself, tell software how many leap seconds separate GPS and UTC. That information must come from the receiver, NTP signaling or a maintained leap-seconds file.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Network NTP or local GPS: choosing the architecture
| Consideration | Network NTP | Local GPS reference |
|---|---|---|
| Reference location | Upstream time service reached over the network. | Receiver and antenna installed at the site. |
| Dependency | Network reachability and confidence in upstream operators. | Power, antenna reception, PPS wiring and local driver support. |
| Leap information | Arrives through NTP packets or the service’s maintained data. | May arrive from GPS signals, NTP and/or a leap-seconds file; the driver must pass it correctly. |
| Operational effort | Lower hardware burden, but requires source selection and monitoring. | More installation and troubleshooting, with a locally independent reference. |
| Failure mode | Loss or corruption of upstream connectivity. | Loss of satellite reception, receiver, PPS, antenna or driver. |
Neither architecture eliminates leap-second planning. A local receiver still has to convert GPS time to UTC, and a network server still has to apply the announced leap according to its kernel and daemon support.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why a synchronized clock can still misread old timestamps
Current synchronization answers “what time is it now?” It does not automatically reconstruct the exact UTC meaning of every historical timestamp. NTP’s timescale reference warns that interpreting an old epoch can require the number of leap seconds that had occurred since that event. A present-day offset between GPS, TAI and UTC is insufficient when the record spans earlier leap-second changes.
For historical data, preserve the original time scale and conversion metadata. Identify whether a value was recorded as UTC, GPS time, TAI, Unix-style seconds, local civil time or a smeared scale. Apply the leap-second history appropriate to the timestamp’s date, and document whether the producer represented the leap itself or skipped, repeated or smeared it.
Troubleshooting leap-second and GPS/NTP errors
The clock is stable but the displayed date is off
Check whether the receiver is exposing GPS time as if it were UTC. Confirm the current GPS-to-UTC leap offset and the conversion performed by the reference-clock software. A stable oscillator cannot correct a scale-conversion mistake.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Servers disagree only around the leap event
Compare their policies. One may be smearing while another is applying the explicit UTC leap. Inspect NTP status, packet indicators and daemon logs, then place communicating systems on a documented common policy.
The server never announces the pending leap
Check the upstream source, GPS message fields, leap-seconds file age, driver capabilities and whether the daemon is configured to accept leap information. NTP 4.2.8 documentation notes that support differs among reference clocks and drivers.
Historical records differ by one or more seconds
Determine the source time scale and the leap history used during conversion. Do not “fix” old data by applying only today’s GPS-to-UTC offset; that can produce a different error for each historical period.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How often do leap seconds occur?
The Network Time Foundation reference gives about eighteen months as a rough historical interval, while emphasizing that actual intervals vary. This is context, not a schedule or prediction. No future leap-second event should be inferred from that average; rely on an official announcement and correctly distributed leap information.
Operational checklist
- Document whether each service uses explicit UTC leaps or a smear.
- Keep NTP software, operating-system support and leap-second data maintained.
- Verify the selected source and pending-leap state, not merely a “synchronized” status.
- For GPS, test PPS, driver compatibility, date messages and leap notification separately.
- Use monotonic clocks for durations and synchronized wall clocks for cross-system timestamps.
- Store the original time scale and conversion rules with historical data.
- Monitor for stale sources, policy mismatches and sudden offset changes around announced events.
Frequently Asked Questions
Does GPS account for leap seconds?
GPS maintains its own continuous time scale. A receiver or reference-clock driver must use applicable leap-second information to convert that scale to UTC before presenting civil time.
Can I mix leap-smear and normal NTP servers?
Only if clients understand the difference. During a smear, the supplied time temporarily diverges from unsmeared UTC, so mixed timestamps can disagree.
Is a GPS receiver required for NTP?
No. NTP can obtain time from network or other reference sources. GPS with PPS is one possible local input for a primary server.
Quick Recap
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.
