Mifid2 timestamps for SIs

There are a number of places in the new guidelines that increase the rigor required for timestamping data. One key part covers SI’s (systematic internalizers) who operate kind-of like private exchanges. TimeKeeper’s ability to produce traceable audit and to use multiple sources is designed for precisely this kind of application. Moreover, the inclusion of the…

Red Hat patches for the Leap Second

There will be a leap second June 30 2015 at midnight UCT. FSMLabs has tested TimeKeeper on Red Hat Linux and found that TimeKeeper handles the leap second properly. TimeKeeper avoids using the mechanism for managing the leap second that is sometimes built into Linux. By default TimeKeeper “slews” on the leap second to allow…

Comparing NTP and PTP

Summary: 1. TimeKeeper synchronized clocks can be accurate to within 100 nanoseconds using either Network Time Protocol (NTP) or 1EEE 1588 Precise Time Protocol (PTP). 2. Most non-TimeKeeper implementations of NTP (such as NTPd or Chrony) are usually no better than 1millisecond in accuracy – this includes many GPS based NTP network clocks. 3. There…

Satellite (GPS) time and MiFID II requirements

Although we’re just technologists here, and not experts on European Union Regulatory Law, MiFID II is very specific: Operators of trading venues and their members or participants shall synchronise the business clocks they use to record the date and time of any reportable event with the Coordinated Universal Time (UTC) issued and maintained by the…

TimeKeeper Certified on RedHat Enterprise Linux 8

August 27, 2020 TimeKeeper software has been certified by Redhat for RedHat Enterprise Linux 8. TimeKeeper software supports a wide range of Linux, Microsoft Windows, and Solaris operating systems and has been operating on RHEL 8 in production since the summer of 2019.  This certification validates TimeKeeper as meeting RedHat standards for enterprise systems use…