Clock Sync Report
Live data pulled from CoreScope. Clock offset is calculated by comparing the timestamp embedded in each repeater's advert packet against the time the observer received it.
Why Clock Sync Matters
Packet Deduplication
MeshCore uses timestamps to deduplicate packets seen by multiple observers. If a repeater's clock is off by more than a few seconds, packets it relays may be incorrectly flagged as duplicates and dropped — silently reducing mesh reliability.
Accurate Network Maps
CoreScope and MeshMapper use timestamps to build timeline-accurate views of network activity. Drifted clocks cause packets to appear out of order or at the wrong time, making it hard to debug routing issues or understand network behavior.
Advert Timing
Repeaters broadcast adverts on a schedule. A badly drifted clock can cause advert intervals to appear irregular to other nodes, affecting how the mesh builds its routing tables and neighbor lists.
Signature Validation
MeshCore advert packets include a signed timestamp. Large clock drift can cause signature validation to fail on receiving nodes, causing valid packets to be rejected as potentially replayed or tampered.
clock sync. After syncing, the repeater should disappear from this list within one advert cycle (~240 minutes). We recommend syncing your repeater's clock any time you physically access it for maintenance.