MiFID II 100 microsecond time sync on Windows with TimeKeeper and Mellanox

Accurate time on Microsoft Windows is easy to achieve when using TimeKeeper software and Mellanox ConnectX network adaptors. The most stringent of the MiFID II clock synchronization requirements of 100 microseconds can be met without changes in infrastructure, exotic protocols (such as PTP) or dedicated hardware. Many TimeKeeper customers operate clocks with a better than…

FINRA moves towards tighter timing requirements

“Of the five commenters that supported tightening clock synchronization requirements at least to some extent, all agreed that a millisecond standard is necessary given the speed of trading in today’s markets. For example, according to FSMLabs, FINRA’s proposal is “timely and necessary” because “[w]ide use of electronic trading systems and proliferation of trading venues make…

MiFID II Guidelines on Timestamping

ESMA guidelines issued at the end of 2015 clarify timestamp regulation in ways that make a lot of sense. The most immediately notable point was to reinforce earlier statements that GPS is an acceptable “traceable” source of time per MiFIR RTS 25. A number of parties had been insisting otherwise the face of common sense…

Windows 10 high accuracy timestamping

With TimeKeeper’s high quality multi-source Time Client, Windows 10 operates at the high levels of timestamp accuracy needed for: MiFID II and other regulatory compliance automated trading in general enterprise data analysis and big data Real-Time broadcast and control. Accuracy to within 10s of microseconds is no problem with either PTP 1588 or NTP time…

MiFID II record keeping stresses timestamps

Algorithmic trading: Algorithmic trading records must be stored on an approved form accurate, time-sequenced records of all orders—whether placed, executed or cancelled. This rule applies not just to algorithmic trading, but to all trades; firms must keep for five years all the relevant data relating to all orders and transactions, whether for their own account…

The NTPd packet-o-death exploits

When we began implementing the NTP protocol from scratch we found that after 30 years of sometimes smart and sometimes not-so-smart development, there were a number of security issues that we needed to address. Some of these are identified by Boston University researchers in their recent note on NTPd exploits. TimeKeeper is not vulnerable to…

MiFID2 and the fragility of time protocols

TimeKeeper incorporates a defense-in-depth design to protect it from deliberate security attacks and errors due to equipment failure or misconfiguration. This engineering approach was born out of a conviction that precise time synchronization would become a business and regulatory imperative. Recent disclosures of still more security problems in the NTPd implementation of NTP show how…