While we strive to maintain the high availability of the T7 trading system for the markets Deutsche Börse Xetra and Deutsche Börse Frankfurt, we want to ensure our Trading Participants are well prepared for the rarely occurring incidents.
Along with the T7 Emergency Playbook, we publish Newsflash messages on a regular basis to summarize the handling of various special incidents or provide more general incident handling information. This Newsflash briefly outlines the scenario of a combined PS gateway/matching engine failover and provides relevant best practice guidance.
1. Background information
When a combined PS Gateway/Matcher process is in place, the failure of the PS Gateway implies the simultaneous failure of the Matching Engine and vice versa.
To achieve the necessary throughput and latency requirements, the T7 combined PS Gateway/Matching Engine handles all incoming orders and the state of the orders in non-persistent memory. The actions prior to a failure of the combined PS Gateway/Matching Engine may have triggered a preliminary acknowledgement to the trading participant but may not have been persisted.
A PS Gateway/Matching Engine failover is not transparent but always implies a Market Reset and that active sessions connected to that combined PS Gateway/Matching Engine will be disconnected. In case the primary PS Gateway/Matching Engine fails, the secondary component will take over by loading the persistent orders from the persistency layer and trading continues after a Market Reset - all non-persistent orders and quotes are deleted. After a timeout of 30 seconds (configurable) order maintenance will become available on the now active combined PS Gateway/Matching Engine.
2. Best Practice
If an active HF session is disconnected for any reason, the participant application should first try to reconnect to the same PS Gateway/Matching Engine. In case of a failed connection attempt, it should then try to connect to the backup PS Gateway/Matching Engine. The session login response (or reject) will inform about the status of the PS Gateway/Matcher process.
For more information on how to handle a matching engine and gateway failover and failure incident, please see the following document on our Deutsche Börse Cash Market website www.cashmarket.deutsche-boerse.com:
under the following path: Data & Tech > Release 14.0 (or latest release version) > Production
3. Focus Day in Simulation
A technical focus day scenario is provided in simulation environments to assist participants in testing the rare event of a matching engine failover followed by a partition failure.
For more details, please check the following documents on our Deutsche Börse Cash Market website:
under the path: Data & Tech > Release 14.0 (or latest release version) > Simulation
under the path: Data & Tech > Simulation Calendar
With the next focus day on 14 April 2026 we encourage participants to test their processes during a Matching Engine Failover followed by a Partition Failure scenario in the simulation environments.
On this day, we will also send a test text message and e-mail to simulate our emergency communication procedures.
If you have any further questions or comments please do not hesitate to contact Cash Market Operations via tel. +49-69-211-1 14 00 or cmmarketcontrol@deutsche-boerse.com.
Kind regards,
Your Client Services Team
Further information
Market Status XETR ⓘ
XETR
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 webpage under Data & Tech > Information Channels > Emergency procedures. 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.