Eurex
1. Introduction
The Executive Board of Eurex Frankfurt AG (EFAG) decided on changes to the General Terms and Conditions to the Agreement on the technical connection and the utilization of the Exchange-EDP of Eurex Deutschland (hereafter: GTC Connection Agreement) and to the General Terms and Conditions to the Agreement on the technical connection of a Multi-Member-System Provider to the Exchange-EDP Eurex® (hereafter: GTC Provider Connection Agreement). These include the following:
A. Increase the connectivity limit for 10Gbit/s Order Entry connections and 10Gbit/s Market Data connections, as well as adjustments to the calculation method in the case of fully occupied access points.
B. Harmonization of potential enforcement measures in the event of limit violations of connection and load limits.
C. Reference adjustment regarding the Price List to Connection Agreement, Provider Connection Agreement and STPIP and QTPIP Connection Agreement in the GTC Provider Connection Agreement.
These amendments will become effective on 19 August 2022.
2. Required action
The amendments as specified in the attachments are deemed to have been approved if the Trading Participant does not lodge objections with Eurex Frankfurt AG within six (6) weeks of notification of the amendments.
3. Details
A. Adjustment of the connectivity limits
Regarding the increase and adjustments of the connectivity limits, EFAG is adding clarifications to the GTC Connection Agreement and to the GTC Provider Connection Agreement as follows:
Amended regulation | Clarification | |
§ 1 | Definition of the network sides (A and B) for the purpose of routing the EFAG infrastructure | |
§ 3 | Limit increase to 6 10Gbit/s order entry connections per access point and 40 10Gbit/s market data connections, as well as clarification of the calculation method in the case of fully occupied access points |
EFAG will only accept customer orders for new lines that would breach the current limit starting 5 August 2022.
B. Harmonization of measures in case of limit violations
EFAG standardizes the potential measures in the event of limit violations in § 3 (5) GTC Connection Agreement and § 3 (12) GTC Provider Connection Agreement and provides for a temporary closure of the port of the connection that causes the limit violation. Corresponding measures will be communicated to the contracting party in advance; this can only be omitted in exceptional situations if there is an immediate risk to the integrity and functionality of the Exchange EDP.
C. Reference adjustment in the GTC Provider Connection Agreement
EFAG adds a reference to the Price List to Connection Agreement, Provider Connection Agreement and STPIP and QTPIP Connection Agreement in § 5 (2) of the GTC Provider Connection Agreement.
Attachments:
Further information
Recipients: | All Trading Participants of Eurex Deutschland and Vendors | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Contact: | client.services@eurex.com | |
Web: | www.eurex.com | |
Authorized by: | Jonas Ullmann |
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.
