Cryptographically prove your clocks were synced to UTC — at any point in history.
Signed
Every second
Traceable
To national UTC
Tamper-evident
Cryptographic log
Offline
Verifiable
Regulators don’t want logs — they want proof. UTC Verification signs the state of every clock in your network with a continuous chain of cryptographic attestations traceable back to a national UTC source. When an auditor asks “can you prove this timestamp was within 100 µs of UTC at the moment of the trade?” — you hand them a signed receipt, and the conversation is over. It’s the compliance layer that turns timing from a thing you hope is working into a thing you can prove was working.
What it does
Every host’s clock state is signed once per second (configurable) and anchored to the previous attestation in a tamper-evident chain.
The attestation chain is rooted in a national UTC reference (NPL, NIST, PTB or similar). Auditors can trace any timestamp back to the source and verify it independently.
Query any historical timestamp and get back a signed receipt: the clock state, the UTC reference at that moment, and the cryptographic chain that proves it.
Attestations are chained — breaking one breaks the whole sequence, and the break is detectable by anyone holding the chain.
Recipients can verify attestations without calling back to TimeBeat or your servers. The chain is self-contained and portable.
One-click MiFID II, CAT, FINRA and MAS evidence packs. Signed, timestamped, ready to send.
How it works
Step 1
TimeBeat continuously ingests a reference timestamp from a traceable UTC source (national lab or equivalent).
Step 2
Every host’s clock state — offset, path delay, GNSS quality, holdover status — is signed and chained with a cryptographic hash of the previous state.
Step 3
Querying any past timestamp returns a signed receipt containing the clock state, the UTC reference, and the full cryptographic chain back to the source.
Where it lives
01
Demonstrate that HFT timestamps were within 100 µs of UTC throughout the trading day — cryptographically, not just in a log file.
02
Hand an auditor a signed receipt instead of a spreadsheet. Every timestamp traces to UTC, every chain is tamper-evident.
03
Cryptographic proof of clock state for forensic timelines, evidence handling and event ordering across distributed systems.
04
One attestation chain satisfies multiple regulators (ESMA, SEC, MAS, HKFSC, ASIC) — no per-regulator reporting gymnastics.
Hardware pairs
The capabilities of UTC Verification pair naturally with these products. Deploy together for the fullest experience.
Standards & compatibility
Also in the platform
Book a demo
Thirty minutes with a TimeBeat engineer. We’ll show you live dashboards, answer your architectural questions, and map the platform to the problem you’re actually trying to solve.
Further reading
Pillar guide
What a grandmaster actually does, how to choose one, and the three things that separate a grandmaster you can trust from one that quietly drifts.
Cluster
Choosing the right oscillator class — the drift numbers that matter and the deployment scenarios where each is correct.
Interactive tool
Model the regulatory and operational cost of a GNSS disruption for your industry and oscillator class.
Library
Guides, blogs and case studies for teams evaluating or deploying this solution.
Why a single-grandmaster deployment is a DORA Article 11 problem, what A/B/C redundancy looks like in a single rack unit, and how the Open Time Appliance Shelf turns three independent Rubidium Black+ grandmasters — with independent GNSS antennas — into the default finance-venue topology for 2026 and beyond.
A speculative question, not a product pitch: imagine if every machine could hand anyone independently verifiable proof of what its clock was doing at any moment in history. Would it matter? Who would benefit, what might it cost us, and would the world actually be better for it? An exploration of the idea of cryptographic UTC attestation.
DORA Article 11 requires documented ICT business continuity, and a single-unit grandmaster topology does not satisfy it. The structural reasons, the specific evidence regulators are beginning to ask for, and what a compliant replacement topology looks like in 1RU.
The difference between observability and attestation — why the direction of travel in ESMA, FCA and SEC guidance is making log-file compliance structurally insufficient, and what independent verifiability means in practice for a regulator's audit team.
The EU's Digital Operational Resilience Act extends MiFID II's clock synchronisation requirements into operational resilience territory. What DORA actually demands of timing infrastructure, and how to build a resilient timing fabric that survives the kinds of failures the regulation is now scrutinising.
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.
