26 Aug 2020


Eurex Exchange Readiness Newsflash | Incident handling: Matching engine processing delay

Eurex Exchange Readiness Newsflash | Incident handling: Matching engine processing delay

Dear Eurex Participant,

While our constant effort is to keep the usual high availability rate of the Eurex T7 trading system, we want to support our trading participants to be prepared as best as possible for the rarely occurring incident cases. Therefore, we publish newsflash messages on a regular basis that explain the handling of various special incident cases or provide more general incident handling information. 

Today, we provide you with the information needed in case a delay in the matching engine processing takes place.

1.    Background information

Large processing delays in the T7 matching engine (caused e.g. by technical problems or unexpected extreme loads) may lead to the build-up of internally queued orders.

To avoid processing of old orders and to quickly recover from this delay situation, the affected products change to an internal “not tradeable” state. This rarely occurring kind of incident is automatically detected and for the relevant products the following actions are taken: 

  • All non-persistent orders and quotes are deleted. 
  • The product is temporarily set to an internal “not tradeable” state. Session data and listener broadcasts are sent. The product is not set to “Halt”. 
  • All transactions will be rejected except for order deletions, for a minimum time frame, which is currently configured to 10 seconds and until the delayed processing is resolved.
  • Once the situation is resolved, it will be communicated via session data and listener broadcasts.

2.    Best Practice

If an ETI trading session receives the message “Product_temporarily_not_tradeable”, submission of new orders should be avoided until the “Service Resumed” notification is received, since the new order flow will only exacerbate the solution of the delay problem and the orders will be rejected anyway. Deletion of non-persistent orders and quotes already took place, so any clean-up can be limited to the deletion of persistent orders, if necessary.

3.    Focus days in Simulation

This focus day scenario is provided to assist participants in testing the very rare event where massive processing delays occur on a partition. For further details please check the following documents on our website

  • Participant Simulation Guide

under the following path: Technology > T7 Trading architecture > Release 8.1 (or the latest release version) > Simulation

  • Simulation calendar

under the following path: Technology > Simulation calendar

The latest news on the development and the implementation of T7 on Eurex is available on our Implementation News page under the path: Technology > T7 Trading architecture > Implementation news

4.    Further information

For further information, please have a look at the “T7 Incident Handling Guide” (Chapter 3.6), under the following path: Technology > T7 Trading architecture > Release 8.1 (or the latest release version) > Production

If you have any further questions or comments please do not hesitate to contact your Key Account Manager or send an e-mail to

Kind regards,

Your Client Services Team

How to keep up with news? Get the latest Eurex updates fast and easy using: Eurex App, LinkedIn, YouTube or visit our website


All Trading Participants of Eurex Deutschland and Vendors

Target groups:

Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination


Your Key Account Manager or


Market Status


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.