TL;DR
- ▸MiFID II, FINRA Rule 613 and equivalent national regulations all require timestamps traceable to UTC. "Traceable" is a precise technical term — not a marketing slogan.
- ▸NTP from the public internet does not qualify for traceability. PTP from a hardware grandmaster locked to GNSS does.
- ▸The precision floor has steadily tightened. Each revision of financial regulation has tightened the precision floor; competitive operational reality usually leads regulation by 12-24 months.
Traceability is the load-bearing word
MiFID II Article 50 / RTS 25, FINRA Rule 613 / Consolidated Audit Trail, and equivalent national regulations all require timestamps traceable to UTC. The phrase "traceable" is a precise technical concept, not a marketing slogan — it means the firm's local clock must be synchronised to a reference clock whose time is in turn synchronised to a national metrology institute, with a documented and verifiable chain of synchronisation between every layer.
This rules out a few patterns that occasionally show up in compliance discussions. NTP from the public internet is not adequate for traceability under MiFID II, even if the achieved accuracy nominally fits the budget — the public NTP infrastructure is not formally traceable to a national metrology institute, and the firm cannot produce documentation of the synchronisation chain on demand. Likewise, a corporate NTP server pulled from random pool servers is not adequate. The traceability chain has to terminate at a primary reference time clock on the firm's premises, normally a GNSS-disciplined hardware grandmaster.
Why PTP is the only credible answer
From the primary reference clock, the synchronisation chain to the trading systems must be documented and bounded. PTP is essentially the only protocol that can deliver microsecond-class traceability to UTC across an enterprise network in a way the firm can actually evidence to a regulator. The combination of hardware timestamping, boundary clocks at every hop, and BMCA failover gives the firm a deterministic chain from grandmaster to slave that the regulator can verify.
NTP simply cannot do this. Software timestamping introduces variable delays that swamp microsecond-level measurements; the public NTP infrastructure has no formal traceability chain; and NTP's failover model doesn't give the firm the deterministic behaviour a regulator expects. Every regulated trading venue we've worked with runs PTP for HFT timestamping for these reasons. There are no exceptions in our customer base.
Why the precision floor keeps tightening
Each successive revision of financial regulation has tightened the precision floor. MiFID II's 100-microsecond budget for HFT was tight in 2018; the operational reality in 2026 is that competitive trading venues run sub-microsecond precision throughout, and the market expectation is that the next wave of regulation will follow the operational floor downward. Competitive operational practice usually leads regulation by 12-24 months.
This matters for procurement decisions today. A timing infrastructure specified to meet the current regulatory minimum will be obsolete within the next deployment cycle as the floor tightens. The right approach is to specify one tier above the current minimum so the deployment doesn't need to be re-architected the next time the regulator catches up to where the operational floor already is.
Where TimeBeat fits
TimeBeat builds the open-standard PTP grandmasters and audit-defensible Sync Insight observability platform that regulated investment firms use to meet MiFID II / FINRA / equivalent traceability requirements. Our customers include market makers, trading venues, prime brokers and clearing houses across European and US markets. The conversation about how to specify a compliant timing fabric for a new venue or how to upgrade an existing one is one we have with customers regularly — talk to the engineering team if it's relevant.
Frequently asked questions
What does "traceable to UTC" actually require?+
Can I use NTP for MiFID II compliance?+
How precise do MiFID II HFT timestamps need to be?+
Will the precision floor tighten further?+
Related reading
Blog · Compliance
MiFID II Article 50 and FINRA Rule 613: What Clock Synchronisation Actually Demands
MiFID II RTS 25, FINRA's Consolidated Audit Trail and SEC Rule 613 all demand traceable, microsecond-grade clock synchronisation from regulated trading venues. What the rules actually say, what they don't, and what a compliant timing fabric looks like in practice.
Blog · Finance
High-Frequency Trading: Speed, Fairness and Nanosecond Precision
Why HFT firms are pushing the precision floor of clock synchronisation into single-digit nanoseconds, what venue parity actually means at that precision, and where the next competitive frontier lives.
Blog · Protocols
Precision Time Protocol vs NTP: When Each Belongs in Production
The honest engineering comparison between Precision Time Protocol and NTP — what each protocol can actually deliver, where the boundary lives, and how to choose between them without falling for either side's marketing.