Find
14 Feb 2019

Eurex

Enhancement of the Excessive System Usage concept: Introduction of a new limit type

The Excessive System Usage Fee (ESU) concept is designed to protect the T7 trading system from excessive system usage. With the introduced amendments to the T7 trading system architecture in the last two years, Eurex Exchange achieved a reduction in the median latency, but more important, the variance of the latency dropped dramatically, leading to more deterministic and resilient system behaviour.

It is in the interest of all of its market participants, that Eurex Exchange is therefore taking further steps to solidify these achievements and disincentive behaviour that may be detrimental for market and system structure at a cost of excessive system usage.

Thus, Eurex Exchange will enhance the ESU concept with a new, third limit type, which will count against all transactions which do not lead to a market data update and against all order modifications which result in an order deletion without a trade.

A testing phase for the ESU concept including the third limit type will start on 1 March 2019. On 1 April 2019, the ESU fee including the new limit type will be effective. This circular provides a brief description of the new ESU limit type and further relevant information.

Furthermore, some other minor amendments to the Price Lists to the Connection Agreement and to the Provider Connection Agreement and to the GTC to the Connection Agreement of Eurex Frankfurt AG will be effective as of 1 April 2019.

Market Status

XEUR

The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.

Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message. 

We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.

An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.