This topic describes client impacts for CME STP FIX API on Google Cloud.
Contents
| Table of Contents |
|---|
Revision History
Date | Description |
|---|---|
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. |
...
Date | Milestone |
|---|---|
Wednesday, January 8, 2025 | New Release |
Sunday, May 11, 2025 | Production internet connectivity available |
To be announced | Production Launchdedicated connectivity |
Onboarding
CME STP FIX on Google Cloud will not require separate or additional client onboarding.
...
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) |
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
In the production environment CME STP FIX will operate in two regions, Eastern and Central United States.
...
Clients have two different options of internet connectivity to CME STP FIX on Google Cloud.
Connectivity Option | URLAsset Class | Hostname | Port | Usage |
|---|---|---|---|---|
Managed | Option 1All | stpfix.api.cmegroup.com [208.112.128.43] | 443 | 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. |
Regional | Option 2All | stpfix-a.api.cmegroup.com [208.112.128.46] stpfix-b.api.cmegroup.com [208.112.128.45] | Clients can connect to both regions in parallel providing flexibility and redundancy. Clients can subscribe to same or different STP trade data across regions based on their entitlements. Sequences of messages are not guaranteed to be the same across regions. |
...
| Note |
|---|
Client systems are required to target the Hostname(s). IP’s are provided for convenience of local client side whitelisting. This will ensure that the server certificate name will match with client requests and client systems can rely on standard certificate validation. |
| Info |
|---|
CME STP FIX Host servers use certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required. |
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.
If clients cannot use a public DNS on their side, they should deploy a local DNS override (i.e. host-file entry). This will ensure that the server certificate name will match up with client requests and they can rely on standard certificate validation.
Connectivity Type | Asset Class | New Service URL (GC) - Region-a | New Service URL (GC) - Region-b | Usage | Port |
|---|---|---|---|---|---|
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) | Clients can connect to both regions in parallel providing flexibility and redundancy. Clients can subscribe to same or different STP trade data across regions based on their entitlements. Sequences of messages are not guaranteed to be the same across regions. | 443 |
Dedicated connectivity - BrokerTec FI clients | All | 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 | All | stpfix-ll-ebs-a.api.cmegroup.com (208.112.168.2) | stpfix-ll-ebs-b.api.cmegroup.com (208.112.152.2) |
Service URL's URLs use certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required.
...
There will be no changes to the CME STP FIX server and client message payload.
Automatic TCP/IP Disconnection
Client systems TCP/IP connectivity to Google Cloud Internet instances of CME STP FIX will be disconnected 24 hours from when the connection is established.
Dedicated connectivity clients are not expected to be affected by the 24 hour disconnect.
Regardless of the connectivity options used, Client systems are expected to reconnect, reestablish their FIX session and initiate a subscription when disconnected.
Google Cloud Regions and Resiliency
...