Slide 6
Slide 6 text
Business Clocks – What requirements will apply with MiFID II?
5
Gateway-to-gateway
latency1
Max. divergence
from UTC
Granularity of
timestamp
Trading venues
>= 1 ms2 1ms 1ms or better
< 1 ms2 100 µs 1µs or better
HFTs - 100 µs 1µs or better
Voice trading - 1s 1s or better
RFQ - 1s 1s or better
Negotiated
Transactions
- 1s 1s or better
Other trading activity - 1ms 1ms or better
¹ Gateway-to-gateway latency shall be the time measured from the moment a message is received by an outer gateway of the trading venue’s system, sent through the order submission
protocol, processed by the matching engine, and then sent back until an acknowledgement is sent from the gateway.
2 Measured at the 99th percentile of all orders advertised through the system according to CP ‘Guidelines on transaction reporting, reference data, order record keeping and clock
synchronization’ published on 23 December 2015
None of the information contained in this presentation constitutes investment advice. The content on this presentation is solely for information and
does not constitute an offer to sell or a solicitation of an offer to purchase any contract, share or other financial instrument.
Reference time: 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)
Level of accuracy: Applicable for operators of trading venues and their members
1
2
µs = microsecond, ms = millisecond, s = second