CME STP FIX API on Google Cloud
This topic describes client impacts for CME STP FIX API on Google Cloud.
Contents
Revision History
Date | Description |
|---|---|
Tuesday, April 15, 2026 | Updated New Release and Production environment connectivity details; including internet, dedicated, on-prem options. |
Thursday, February 26, 2026 | Updated New Release environment connectivity information, including managed and regional connectivity types. |
Wednesday, January 28, 2026 | For Regional Connectivity: View connectivity configuration details for this service (CME Group Login required). |
Wednesday, January 21, 2026 | Added Certification environment Hostname and Port. |
Monday, December 8, 2025 | Updated Internet Connectivity with new IP Addresses, dedicated connectivity is available. |
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 available |
Sunday, May 11, 2025 | Production internet connectivity available |
To be announced | Production dedicated connectivity availability |
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. To initiate certification, client systems should connect to Hostname: autocertstpfix.api.uat.cmegroup.com and Port: 443. For questions, contact Certification Support for Electronic Trading (CSET).
Connectivity
This section outlines CME STP FIX connectivity on Google Cloud.
CME STP FIX on Google Cloud operates in two regions, Eastern and Central United States.
New Release Environment
View new release environment managed and regional connectivity details (hostnames, IPs and ports). CME Group Login is required.
Production Environment
CME STP FIX clients can access enhanced Production environment connectivity (see below table) via Google Cloud hosts, which operate concurrently with the existing on-prem hosts and deliver identical trade data. Clients are required to implement internal measures to preclude the duplicate booking of trades. This Google Cloud option offers multiple connectivity compared to the current on-prem connection.
Connectivity Type | Access Type | Connectivity Details CME Group Login is required to view. |
|---|---|---|
Internet connectivity | Public internet | |
Dedicated line - Managed connectivity | ||
Dedicated line - Regional connectivity |
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)