CME STP FIX API on Google Cloud
This topic describes client impacts for CME STP FIX API on Google Cloud.
Contents
- 1 Revision History
- 2 Key Events and Dates
- 3 Onboarding
- 4 Authorization and Entitlement
- 5 Testing and Certification
- 6 Connectivity
- 6.1 New Release Environment
- 6.2 Production Environment
- 6.2.1 Internet Connectivity
- 6.2.2 Dedicated Line Connectivity
- 6.2.2.1 Managed Connectivity
- 6.2.2.2 Regional Connectivity
- 7 CME STP FIX API Differences
- 8 Google Cloud Regions and Resiliency
- 9 Contact Information
Revision History
Date | Description |
|---|---|
Wednesday, November 18, 2025 | Updated Internet Connectivity with new IP Addresses. |
Wednesday, September 15, 2025 | Added requirement to use Transport Layer Security (TLS) 1.2 with Server Name Indication (SNI) |
Tuesday, September 2, 2025 | Updated Testing and Certification, CME STP FIX on Google Cloud message recovery testing is required. |
Monday, June 23, 2025 | Updated production dedicated line connectivity |
Wednesday, May 7, 2025 | Updated production internet connectivity |
Monday, January 6, 2025 | Product Launch date updated - to be announced |
Wednesday, November 20, 2024 | Initial publication of client impact topic. |
Key Events and Dates
Date | Milestone |
|---|---|
Wednesday, January 8, 2025 | New Release |
Sunday, May 11, 2025 | Production internet connectivity available |
To be announced | Production dedicated connectivity |
Onboarding
CME STP FIX on Google Cloud will not require separate or additional client onboarding.
Authorization and Entitlement
Clients can continue using existing CME STP FIX API IDs.
Entitlements will be handled internally by CME Group, clients do not need to make any changes.
Testing and Certification
CME STP FIX on Google Cloud message recovery certification is required. For questions, please contact Certification Support for Electronic Trading (CSET).
Connectivity
This section outlines CME STP FIX connectivity on Google Cloud.
New Release Environment
Connectivity Type | Asset Class | Current Hostname | New Hostname (GC) | Port |
|---|---|---|---|---|
Internet (only) The hostname uses certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required. | All | fixstpnr.cmegroup.com | stpfix.api.uat.cmegroup.com | 443 |
Production Environment
This section describes enhanced connectivity options for CME STP FIX on Google Cloud compared to the current connectivity. These additional CME STP FIX hosts on Google Cloud will be available in parallel to current On-Prem host. During the parallel period, the same trade data will be available on both current and new service hosts. Clients should take steps to avoid double booking trades within their systems.
In the Production environment CME STP FIX will operate in two regions, Eastern and Central United States.
Internet Connectivity
Clients have two different internet connectivity options for CME STP FIX on Google Cloud.
To ensure that server certificate names match client requests, CME STP FIX host servers use certificates signed by a trusted Certificate Authority (CA). Client systems rely on standard certificate validation and additional certificates are not required.
The hostnames are publicly discoverable on the internet. Client systems must target the hostnames (below). IPs are provided for local/client-side whitelisting.
Connectivity Option | Hostname | IP Addresses | Port | Asset Class
| Usage | |
|---|---|---|---|---|---|---|
Current | New (effective December 7, 2025) | |||||
Managed | stpfix.api.cmegroup.com | 208.112.128.43 | Managed hostname will resolve to one of the following IPs:
| 443 | All
| Clients only need to connect to a single service URL for all STP data that they are entitled to. CME Group will manage regional connectivity. In the event of regional failover, customers should account for the propagation time of DNS Updates, when the IP’s are switched to different regions. |
Regional | stpfix-a.api.cmegroup.com | 208.112.128.46 | 208.112.129.136 | 443 | All | Clients can connect to both regions in parallel providing flexibility and redundancy. Clients can subscribe to the same or different STP trade data across regions based on their entitlements. Sequences of messages are not guaranteed to be the same across regions. |
stpfix-b.api.cmegroup.com | 208.112.128.45 | 208.112.129.100 | ||||
Dedicated Line Connectivity
Clients who are on one of the specific Production Connectivity Options offered by CME Group can use CME STP FIX on their connectivity option using the below server destinations and options.
CME STP FIX host servers use certificates signed by an official trusted Certificate Authority (CA). Client systems establishing TCP/IP connections should use Transport Layer Security (TLS) 1.2. Clients should use the hostnames with Server Name Indication (SNI) extension during TLS handshake to ensure they can start and keep a session to CME STP FIX.
Dedicated connectivity options below are provided for Client Network Readiness. CME STP FIX Dedicated connectivity availability will be announced in future notices.
Managed Connectivity
With Managed Connectivity option, Clients only need to connect to a single Publicly resolvable service host for all STP data that they are entitled to. CME Group will manage regional connectivity.
Connectivity Type | Asset Class | Hostname | Port | Usage |
|---|---|---|---|---|
Dedicated connectivity - Futures and Options clients | All | stpfix-ll-fo-api.cmegroup.com [208.112.160.2] and [208.112.144.2] | 443 | Clients only need to connect to a single Publicly resolvable service host for all STP data that they are entitled to. CME Group will manage regional connectivity. In the event of regional switch, clients FIX Session will be disconnected. Client systems are expected to reestablish their FIX Session, recover missing trades and continue Subscription for real-time trades. Trade data available to client systems depends only on the entitlements of the API ID used to establish the FIX Session and not limited by connectivity option. |
Dedicated connectivity - BrokerTec FI clients | stpfix-ll-btec.api.cmegroup.com [208.112.164.2] and [208.112.148.2] | |||
Dedicated connectivity - EBS FX clients | stpfix-ll-ebs.api.cmegroup.com [208.112.168.2] and [208.112.152.2] |
Client systems are required to target the hostname(s). IPs are provided for convenience of local client side whitelisting purpose only.
This will ensure that the server certificate name will match with client requests and client systems can rely on standard certificate validation.
Regional Connectivity
With Regional Connectivity option, clients can connect to both regions in parallel or switch connections between regions individually, providing flexibility and redundancy.
Connectivity Type | Asset Class | Hostname (GC) - Region-a | Hostname (GC) - Region-b | Port | Usage |
|---|---|---|---|---|---|
Dedicated connectivity - Futures and Options clients | All | stpfix-ll-fo-a.api.cmegroup.com [208.112.160.2] | stpfix-ll-fo-b.api.cmegroup.com [208.112.144.2] | 443 | Clients can connect to both regions in parallel or switch connections between regions individually, providing flexibility and redundancy. Clients can subscribe to same or different STP trade data across regions based on their entitlements. Clients systems should handle duplicate messages if they subscribe to same trade data between regions. Sequences of messages are not guaranteed to be the same across regions. Trade data available to client systems depends only on the entitlements of the API ID used to establish the FIX Session and not limited by connectivity option. In the event of regional failure, clients FIX Session will be disconnected. Client systems are expected to reestablish their FIX Session, recover missing trades and continue Subscription for real-time trades from the different region. |
Dedicated connectivity - BrokerTec FI clients | stpfix-ll-btec-a.api.cmegroup.com [208.112.164.2] | stpfix-ll-btec-b.api.cmegroup.com [208.112.148.2] | |||
Dedicated connectivity - EBS FX clients | stpfix-ll-ebs-a.api.cmegroup.com [208.112.168.2] | stpfix-ll-ebs-b.api.cmegroup.com [208.112.152.2] |
Client systems are required to target the hostname(s). IPs are provided for convenience of whitelisting or for local client side DNS lookup.
This will ensure that the server certificate name will match with client requests and client systems can rely on standard certificate validation.
CME STP FIX API Differences
There will be no changes to the CME STP FIX server and client message payload.
Google Cloud Regions and Resiliency
CME STP FIX requires clients to reset both outbound and inbound sequence number on establishing a FIX session using tag 141-ResetSeqNumFlag="Y" on their logon request.
When client systems detect a lost connection or session that is established with CME STP FIX, they are expected to login to reestablish the session and restart a new subscription.
Please see more details in CME STP FIX Session Layer topic.
Contact Information
For technical development support, contact Certification Support for Electronic Trading (CSET).
For production requests, contact the Global Command Center (GCC).
For all other inquiries, contact Global Account Management (GAM).
How was your Client Systems Wiki Experience? Submit Feedback
Copyright © 2024 CME Group Inc. All rights reserved.