The Eurex Repo F7 production environment will be updated to F7 Release 4.5 on Saturday, 25 April 2026.
On the evening of 25 April 2026, Eurex Repo will announce the completion of the update via Implementation News. After the update, the production system will be technically available in unattended mode (no technical support).
With the start of the business day on Monday, 27 April 2026, the software version for Repo F7 production will be 004.560.000.
As F7 Release 4.5 is only an optional API upgrade, acceptable version numbers for API clients are “4.4” and “4.5”.
F7 Release 4.5 includes GUI enhancements, optional F7 API changes and a F7 FIX Gateway upgrades with the following changes:
TLSv1.3 Support, decommissioning of TLSv1.2 support
With F7 Release 4.5 Repo F7 will only support TLSv1.3.
Starting from the following decommissioning dates, any attempts to connect with TLSv1.2 will be rejected.
TLSv1.3 supported ciphers
The following ciphers are supported by Repo F7 services with TLSv1.3:
More publications about the TLS change can be found on the Eurex website www.eurex.com under:
F7 GUI users are strongly recommended to clear the browser cache after the release introduction to ensure that the newly introduced GUI functionalities behave correctly.
Details on the various enhancements and features are described in the “F7 4.5 Release Notes" which has been published in the Member Section under the following path: Resources > Eurex Repo > System Documentation > Release 4.5
The following documents are also available under the above-mentioned path:
If you have questions or require further information, please contact repo.sales@eurex.com.
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.