How to Achieve Sub-Microsecond Accuracy Over Wide Area Networks

Blog · WAN timing

How to Achieve Sub-Microsecond Accuracy Over Wide Area Networks

Distributing precision time over a wide area network — between data centres, regions, or continents — is fundamentally harder than distributing it across a single LAN. What the techniques actually look like in 2026.

Lasse Johnsen
Lasse JohnsenCo-founder & CTO, TimeBeat
9 min read
WANLong-haulPTP

TL;DR

  • PTP assumes symmetric forward and reverse path delays. Across a LAN this is roughly true; across a WAN it isn't.
  • Three approaches: lucky packet filtering, bidirectional symmetric fibre engineering, or White Rabbit.
  • Each is appropriate for different deployment models. The right answer depends on what infrastructure the operator controls and how tight the precision requirement is.

Why WAN timing is hard

PTP measures the round-trip delay between two clocks and assumes the forward and reverse paths have equal one-way delays. The slave then computes its offset from the master as half the round-trip time minus the measured one-way component. This works on a LAN where the forward and reverse paths are identical (same fibre, same switches, same direction). It doesn't work on a WAN where the forward and reverse paths can be routed through different equipment with different queueing characteristics, different optical regeneration, and different physical fibre runs.

The result is that naive PTP across a WAN delivers precision in the tens or hundreds of microseconds rather than the sub-microsecond precision the protocol can deliver on a LAN. The error is not random — it's a systematic offset half the size of the path asymmetry, and the protocol cannot detect or correct for it without external information about the path.

What works

Lucky packet filtering uses statistical methods to extract precision time from a noisy WAN PTP stream by selecting the packets with the lowest jitter and weighting them more heavily. The intuition is that the fastest packets approximate the true minimum network delay; the slower packets are dominated by transient queueing and contribute noise. For shared WAN links this can deliver microsecond-class precision where naive PTP would deliver tens of microseconds.

Bidirectional symmetric fibre engineering pins the forward and reverse PTP paths to the same physical fibre, eliminating the asymmetry by construction. This requires the operator to control the fibre infrastructure end to end and to engineer the timing path as a dedicated route rather than relying on shared transport. Where this is feasible, it delivers sub-microsecond precision across hundreds of kilometres.

White Rabbit is the third option and the most precise. It runs on operator-controlled fibre with bidirectional symmetric paths and uses fibre-distributed phase locking back to a master reference. White Rabbit delivers continuous sub-nanosecond precision over hundreds of kilometres — the precision tier above what conventional PTP can achieve. The cost is fibre infrastructure and White Rabbit-capable hardware at every node.

Which approach for which deployment

Lucky packet filtering is the right answer when you don't control the WAN infrastructure (timing across a third-party transport network). Bidirectional symmetric fibre is the right answer when you do control it and microsecond precision is enough. White Rabbit is the right answer when you control the fibre and need sub-nanosecond precision.

Where TimeBeat fits

TimeBeat hardware supports all three approaches. The Open Time Appliance grandmaster can act as a lucky-packet-filtering PTP source for shared WAN deployments. The Open Time Node WR delivers White Rabbit for operators with controlled fibre. And the Sync Insight platform provides the observability needed to characterise asymmetric delay across long-haul deployments and to monitor precision continuously. For operators trying to extend a precision timing fabric across a WAN boundary, the conversation usually starts with which infrastructure the operator controls.

Frequently asked questions

Why doesn't PTP work cleanly over a WAN?+
Because PTP assumes symmetric forward and reverse path delays, and WAN paths are typically asymmetric — different routing, different queueing, different physical fibre. The slave's offset estimate is wrong by half the asymmetry, and the protocol can't detect or correct it without external information about the path.
What is lucky packet filtering?+
A statistical technique for extracting precision time from a noisy WAN PTP stream by selecting the packets with the lowest jitter and ignoring the rest. The intuition is that the fastest packets approximate the true minimum network delay; the slower packets are dominated by transient queueing. Used when the operator doesn't control the WAN infrastructure end to end.
How accurate can WAN timing get?+
Depends on the technique. Lucky packet filtering across a shared WAN: low microseconds, sometimes sub-microsecond. Bidirectional symmetric fibre engineering with conventional PTP: sub-microsecond across hundreds of kilometres. White Rabbit on operator-controlled fibre: continuous sub-nanosecond.

Talk to us

Got a time-sync question like this in your network?

Book a 30-minute call with a Timebeat engineer — we will tell you which products fit, what the install looks like and what it would cost.