What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Prepare for the end of routine leap seconds as a time-policy and data-integrity project, not as a single patch. Inventory every clock source, select one documented synchronization policy for each trust domain, separate monotonic timing from UTC display time, and test the complete path into your database and analytics systems. PostgreSQL can store UTC-based instants, but it does not represent a strict leap-second label such as 23:59:60; systems that need exact ordering or traceability must retain sequence and source-clock data in addition to a normalized timestamp.
What the end of leap seconds actually means
UTC currently uses leap seconds to keep the difference between Earth-rotation time (UT1) and UTC within plus or minus 0.9 seconds. In the traditional positive-leap sequence, the final minute is represented as 23:59:59, 23:59:60, then 00:00:00. The National Institute of Standards and Technology (NIST) documents this purpose and sequence.
In 2022, the General Conference on Weights and Measures (CGPM) adopted a decision, recognized in International Telecommunication Union (ITU) material, to increase the maximum permitted UT1−UTC difference in or before 2035 and end routine leap-second insertion over the longer term. The sources available for this guide do not specify one final deployment date, a universal replacement time scale, or a complete operational schedule. Treat the change as an evolving standards and implementation issue: follow IERS, ITU, NIST, operating-system, database and timing-vendor advisories as details mature.
Free tools Windows power users keep installed
One-click scans. No signup required.
“End of leap seconds” therefore does not mean that UTC, time zones or daylight-saving rules disappear. It means that UTC will eventually be allowed to drift farther from UT1 instead of being corrected by regular one-second insertions. Civil-time conversion will still depend on current IANA time-zone data, including political changes to daylight-saving rules.
#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.
Why infrastructure teams should care now
Data logging, telecommunications and time-distribution services are among the systems NIST identifies as vulnerable to leap-second behavior. Digital systems cannot simultaneously guarantee a time scale that is monotonic, smoothly varying and traceable to UTC through a leap event. A platform may stop or repeat a second, skip a second if a negative adjustment is ever required, or smear the adjustment by changing its clock frequency.
Most servers and end-user devices rely on the Network Time Protocol (NTP) to stay synchronized, according to the ITU’s 2023 discussion of time synchronization in data centres. A local policy decision can therefore affect application timestamps, certificate validation, schedulers, queues, leases, backups, observability and cross-system event ordering even when the application never mentions leap seconds.
Typical clock behaviors
| Behavior | What applications may observe | Main risk |
|---|---|---|
| Stepped positive adjustment | The clock repeats or jumps at the correction boundary. | Two events can share a wall timestamp, and elapsed-time calculations can become negative or too short. |
Frozen or repeated 23:59:59 |
Several records appear to arrive in the same displayed second. | Ordering by timestamp alone is ambiguous. |
| Negative-leap-like skip | A nominal second is absent. | Validation, rate windows and scheduled jobs may assume a label that never occurs. |
| Smear | The clock frequency changes over a defined window, so no single second is repeated. | Two sources can disagree during the window even though both are operating as designed. |
Start with a complete time-dependency inventory
Do not limit the inventory to machines running an NTP daemon. Record every component that creates, transports, transforms or compares time.
- NTP clients, servers and pools, including their configured strata and fallback sources.
- Precision Time Protocol (PTP) clients, grandmasters, boundary clocks and transparent clocks.
- Global Navigation Satellite System (GNSS) receivers and any local oscillator or holdover equipment.
- Hypervisors, virtual-machine tools, container hosts and guest time-synchronization settings.
- Cloud-provider time services, managed database services and hosted queues.
- Network appliances, storage systems, hardware-security modules, firmware and embedded controllers.
- Operating-system clock APIs used by applications, schedulers, logging agents and monitoring systems.
- Certificates, authentication tokens, backup catalogs, data pipelines and analytics jobs that compare timestamps.
For each source, capture the protocol, configured peers, expected accuracy, whether it exposes leap indicators, whether it steps or slews, whether it smears, its behavior during holdover, and the owner responsible for changing it. Map those facts to trust domains such as a data centre, an edge site, a cluster or a regulated environment.
Choose one time policy for each trust domain
A documented policy is more important than selecting a fashionable protocol. Ordinary applications generally work with NTP. ITU guidance describes PTP as the choice for demanding distributed-storage and telecommunications systems that require much tighter uncertainty. A domain may contain both protocols for different purposes, but calculations that compare their timestamps must account for the difference.
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.
| Requirement | Usual fit | Questions to answer |
|---|---|---|
| General server and application time | NTP with a clearly documented step or smear policy | Which sources are authoritative? How are leap indicators handled? What is the holdover limit? |
| Tightly coordinated distributed storage or telecom equipment | PTP, normally with a controlled grandmaster and network design | What uncertainty is required? Is UTC or another traceable scale required? What happens when the grandmaster fails? |
| Scientific or traceability-sensitive records | A source and schema that preserve provenance, potentially including GNSS and a traceable reference scale | Can the original protocol timestamp, source identity and correction history be retained? |
Never silently mix a smeared source with a stepped UTC source in one calculation domain. During a smear, two otherwise healthy hosts can differ by a fraction of a second or more depending on the window and implementation. If they participate in the same ordering, lease, quorum or deduplication decision, either align their policy or make the time-domain boundary explicit.
Use the right clock for the right job
Separate elapsed-time measurement from civil-time labeling in code and infrastructure design.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Monotonic clock: use for durations, timeout deadlines, lease expiry, retries, exponential backoff, scheduler intervals and performance measurements. A monotonic source is allowed to be unrelated to UTC; its job is to move forward consistently.
- UTC wall clock: use for audit timestamps, external APIs, human-readable logs and records that must be correlated with other systems. Store the source and synchronization status when those facts affect interpretation.
- Local civil time: derive only for presentation or business rules that explicitly require a named time zone. Resolve the time zone with current IANA data rather than hard-coding offsets.
Do not compute a duration by subtracting two wall-clock timestamps that straddle a correction. Have the producer measure elapsed time with its monotonic clock and transmit that duration, or transmit a start event, end event and sequence identifiers so consumers can reconstruct the interval without assuming wall-clock continuity.
Monitor behavior, not just clock offset
An offset dashboard can look healthy while a source changes policy or enters holdover. Alert and retain history for:
- Stratum and selected-source changes.
- Leap indicators and announced correction state.
- Offset, frequency correction and rate-of-change of both values.
- Holdover duration, oscillator status and loss of GNSS or upstream references.
- Disagreement between independent sources, including a stepped source versus a smear source.
- Clock corrections applied by the operating system, hypervisor or time daemon.
Keep an audit trail of corrections with host identity, source, old and new clock readings, reason, daemon version and operator or automation identity. This record is often more useful than a single “synchronized” status when investigating an event that occurred near a correction.
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.
Patch and rehearse through normal change control
Keep operating systems, hypervisors, NTP and PTP daemons, firmware and database components on supported releases through normal vendor channels. A patch is not a substitute for a policy: verify what the updated component does with leap indicators, stepping, slewing, smearing and holdover.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsBuild a staging rehearsal that can replay the behaviors your production policy must tolerate. Use an isolated clock domain; never alter production time to conduct the test.
- Record the baseline source, stratum, offset, frequency correction and application behavior.
- Inject a stepped positive-leap scenario and verify clock APIs, logs, queues, schedulers, certificates and database writes.
- Replay a repeated or frozen
23:59:59implementation and check whether event ordering relies on a unique wall timestamp. - Replay a negative-leap-like skipped second, even though the eventual policy and occurrence schedule are not yet specified.
- Apply the exact smear profile selected for the trust domain and measure disagreement with any independent source.
- Disconnect the preferred source, observe failover and holdover, then restore it and verify that correction is gradual or stepped according to policy.
- Restore backups and replay messages containing both raw and normalized timestamps to confirm historical reproducibility.
How PostgreSQL represents time
PostgreSQL stores time-zone-aware values internally in UTC and uses IANA time-zone data for civil-time conversion. Its documented seconds range is 0 through 59, and PostgreSQL does not use UTC in the strict leap-second sense because leap seconds are not handled. Consequently, a timestamp or timestamptz value should not be assumed to faithfully encode 23:59:60.
The end of routine leap seconds does not remove the need to update IANA time-zone data. Daylight-saving and political time-zone changes remain separate from leap-second policy.
A resilient event-record design
For systems in which ordering, legal traceability or scientific interpretation matters, store more than one time field.
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
| Field | Purpose | Design note |
|---|---|---|
| Normalized UTC instant | Indexing, joins and ordinary reporting | Use an unambiguous value accepted by the database; document the normalization rule. |
| Event sequence or ingestion ID | Total ordering when wall times tie | Generate it at the producer or ingestion boundary and make it durable. |
| Original source timestamp | Forensic, legal or scientific traceability | Retain the original representation, including a leap label if the protocol supplied one. |
| Source and clock metadata | Interpretation of the timestamp | Record source identity, synchronization status, policy (step or smear) and, where useful, correction state. |
| Monotonic duration or counter | Elapsed-time analysis | Capture at the producer; do not infer it by subtracting corrected wall times. |
An ingestion ID is not a replacement for the event’s source time. It establishes the order observed by the ingest path, while the original timestamp explains when the producer believed the event occurred. Keeping both allows an investigation to distinguish source-clock behavior from transport delay.
Decide how to handle 23:59:60 input
RFC 3339 permits a seconds value of 60 for an actual leap second, but many database and parsing paths do not. Treat it as an explicit validation case and choose one policy per interface:
- Reject: return a clear validation error and require the sender to correct or resubmit the record.
- Normalize with a flag: map the value to the representable instant your system uses, while storing a boolean or enumerated field that records the original leap label.
- Preserve raw input: store the original string alongside a normalized value and sequence, which is useful when exact protocol evidence must survive.
Document the policy in the API contract, parser tests, data-retention rules and downstream analytics. Do not let different services silently choose different normalizations.
Database queries and application code to review
- Find code that orders events only by a wall-clock column; add a sequence or ingestion key as a secondary order.
- Find duration expressions that subtract two timestamps; replace them with monotonic measurements or explicit producer-provided durations.
- Review uniqueness constraints that include a timestamp but no event identifier.
- Check windowed aggregation, rate limiting, retry and deduplication logic for assumptions that every second label occurs exactly once.
- Review partitioning and retention jobs that calculate boundaries from corrected wall time.
- Test parsers, serializers and validation libraries with
23:59:60, repeated23:59:59and a skipped second. - Verify that replicas, change-data-capture streams, message queues and analytics stores preserve sequence and source metadata.
Test the complete path, not only the clock daemon
NIST notes that repeated timestamps make event ordering and interval calculations ambiguous. Your assertions should therefore use sequence IDs or monotonic measurements rather than wall time alone.
| Scenario | What to test | Passing evidence |
|---|---|---|
| Stepped positive leap | Kernel clock, time daemon, application logs, database writes and queue ordering | No negative durations; tied wall times are ordered by sequence. |
Repeated or frozen 23:59:59 |
Unique constraints, sort keys, deduplication and alert grouping | Records remain distinct and reproducibly ordered. |
| Negative-leap-like skip | Parsers, schedulers, rate windows and reporting boundaries | No assumption that the omitted label must exist. |
| Selected smear | Cross-host comparisons, quorum, leases, certificates and external integrations | All participants use the documented policy or reject incompatible sources. |
| Mixed-source disagreement | Source-selection logic and monitoring alerts | The disagreement is detected, attributed and escalated. |
| Secondary-source failover | Holdover, source restoration and correction behavior | Applications remain safe within the declared uncertainty. |
| Restore and replay | Raw timestamps, normalized values, sequence IDs and analytics outputs | Historical events can be reconstructed without losing the original label. |
Choose an architecture by uncertainty and traceability
There is no universal “best” source. Compare designs against the requirements of each trust domain.
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.
| Decision axis | Questions | Why it matters |
|---|---|---|
| Required uncertainty | Are milliseconds sufficient, or are microsecond/nanosecond-class results required? | It determines whether ordinary NTP is adequate or a PTP design is justified. |
| Reference scale | Must records be traceable to UTC, or is another reference such as TAI required? | It affects source selection, metadata and conversion rules. |
| Smear tolerance | Can applications accept a gradually adjusted clock? | A smear can avoid a visible step but creates a deliberate offset from a stepped source during the window. |
| Failure and holdover | How long can the source be unavailable, and what uncertainty is acceptable? | Redundancy and oscillator quality matter as much as nominal accuracy. |
| Database representation | Can the database represent the protocol’s leap label? | If not, raw values and explicit normalization metadata are required. |
| Historical reproducibility | Can you recreate the source state and correction policy for an old event? | Source identity, policy and correction logs make audits defensible. |
When dedicated timing hardware is justified
A controlled NTP server can give a team a defined source and policy instead of depending on an uncontrolled collection of upstream services. Tighter uncertainty requirements may justify PTP grandmasters, GNSS timing and engineered holdover. These are architecture choices, not automatic requirements for every application. Specify accuracy, traceability, redundancy, network topology and failure behavior before selecting equipment or consulting services.
There is no universal migration-cost statistic in the available standards material, and no complete vendor-by-vendor release calendar for the eventual post-2035 realization. Budget discovery, staging, testing and operational work from your inventory rather than applying a generic number.
Common failure modes and their fixes
Ordering by timestamp alone
Symptom: records appear out of order or two records collide at a unique timestamp. Fix: add a producer sequence, ingestion ID or another deterministic tie-breaker and test repeated-second behavior.
Subtracting corrected wall times
Symptom: a timeout, lease or latency becomes negative or unexpectedly long. Fix: use a monotonic clock for elapsed time and transmit the measured duration where it is needed.
Mixing smear and step policies
Symptom: healthy hosts disagree during a correction and distributed decisions fail. Fix: align the policy within the calculation domain or isolate and label the domains.
Assuming PostgreSQL stores every UTC label
Symptom: a parser rejects 23:59:60 or silently changes it. Fix: define reject, normalize-with-flag or raw-preservation behavior and retain the original source value when required.
Updating time-zone rules but not source policy
Symptom: civil-time displays are correct while event ordering or elapsed-time logic remains wrong. Fix: treat IANA updates and leap-policy engineering as separate work streams.
Recommended Free Tools
Testing only the operating-system clock
Symptom: the daemon passes a test but queues, backups or analytics fail in production. Fix: replay scenarios through the full path from source to database, messages, logs, schedulers, certificates, backups and reports.
Quick Recap
A practical implementation sequence
- Map dependencies: produce the source, consumer, policy and owner inventory for every trust domain.
- Classify requirements: record required uncertainty, reference scale, smear tolerance, holdover and audit obligations.
- Standardize policy: document the selected NTP or PTP behavior, source hierarchy, failover and correction rules.
- Refactor timing code: move elapsed-time logic to monotonic clocks and add sequence and provenance fields to event records.
- Harden database interfaces: define the handling of leap labels, preserve raw inputs where needed and update parser contracts.
- Instrument and alert: monitor source changes, leap indicators, frequency, holdover, disagreement and correction history.
- Rehearse in isolation: run positive, repeated-second, skipped-second, smear, disagreement and failover scenarios end to end.
- Review evidence and advisories: keep the runbook current as IERS, ITU, NIST, operating-system, database and timing-vendor guidance becomes more specific.
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.
