ISV & Service Provider Support

Service Provider

Our Service Providers (SPs) offer connectivity infrastructure to the electronic trading system of the Deutsche Börse. Registered members of the Deutsche Börse can use a Service Provider to connect to our Trading and Clearing platforms T7 and C7.

How to become a Service Provider?   

To become a Eurex Service Provider, please contact our Onboarding Team to start the onboarding process. 

  • Please send an email to:
  • Fill in necessary documents (provided by onboarding Team):
    • Declaration of interest to become a Service Provider
    • Service Provider Connection Agreement
    • Market Data Dissemination Agreement 
    • Affiliates form (in case, you are connecting only affiliates) 


Netted and Unnetted Market Data differ basically by the dept of the orderbook (where unnetted Market Data EMDI/EOBI provide access to order book market dept, netted Market Data don’t).

An overview of the connection fees is provided via: Fees for Eurex Exchange connections.

Yes, Service Providers can only connect members of the Eurex.

In this case, two documents are required: 

  • Proof of the affiliate relation of the two companies 
  • Affiliates form contact onboarding team or you (Key Account Manager)

*Affiliates: are given when the term “control” is fulfilled, either by the possession of at least 50% of shares or if the power of direction by the management structure can be proven by contract or otherwise.

In general, Service Providers are providing connectivity to multiple Trading Participants. If only one line is in place, the risk is too high that in case of a technical or physical issue, multiple clients are cut off from their daily trading business.

To grant and maintain high standards of trading security and quality, a second line is in place as a backup connection. Service Provider need to ensure that both lines are in the same member LAN/Subinstallation. There is an exemption to the redundancy requirement, and this is when only offering connectivity to affiliate firms.

We do not offer a specific DR pricing scheme. All connections are usable for production and simulation (with the exception of software vendor connections) and are charged according to our pricing list regardless of whether they are used. There are no exceptions to the redundancy requirement. Our Disaster Recovery concept is available under the following path:  

Eurex > Support > Initiatives & Releases > T7 Release 12.0 > System Documentation > Network Access > T7 Disaster Recovery Concept 

Yes, a physical crossconnect or leased line can  accommodate a Eurex and Xetra MIC. For this setup, two contracts need to be signed independently (one for Eurex, one for Xetra). From a technical perspective, Xetra and Eurex use separate network and separate channels, but these can be on the same physical line with the exemption of 10 GB connections, in which case only one market (Xetra or Eurex) and only one service (market data or transaction services) is possible per physical 10 GB crossconnect. 


In case of any questions, please contact us at

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.