For the latest roadmap of CME Group technology initiatives:
See the Development Launch Schedule.
Additional Resources:
- Versions of BrokerTec notices dated March 23, 2023, and onward are available from the Notice Search page.
- Archived BrokerTec notices dated July 2019 through March 9, 2023, are available from the BrokerTec Support Portal, which requires a separate login.
Critical System Information
UpdateCME GC Allocator API Migration to Google Cloud - June 23
† Denotes update to the article
† The CME GC Allocator API is now available in Google Cloud, and effective Monday, June 23, the current URLs for on-prem CME GC Allocator API endpoints will be decommissioned in Production.
Details on CME GC Allocator API hosted on Google Cloud are below:
| GC Allocator API Endpoints | ||
|---|---|---|
| Environment | Current URL / IP | Google Cloud URL / IP |
| Production (via Internet) | https://api.gcallocator.cmegroup.com/ 205.209.196.176 | https://posttrade.api.cmegroup.com/gca/v2 208.112.128.6 |
| New Release (via Internet) | https://api.gcallocator-nr.cmegroup.com/ 164.74.123.38 | https://posttrade.api.uat.cmegroup.com/gca/v2 208.112.192.6 |
Customers are strongly encouraged to access the CME GC Allocator API over the Internet to leverage Google Cloud automated failover capabilities. Customers requiring access to the CME GC Allocator API over dedicated connectivity can find the required information in the Client Systems Wiki.
† Customers using the web-based CME GC Allocator appication will not be impacted by this change.
† Customers who access CME GC Allocator via third-party vendor or via the BrokerTec GFE GC Allocation tab logbook, should connect to the new endpoints prior to Monday, June 23, to ensure a seamless connection.
GET requests with "content-type" header set to "application/json" will be rejected with a 400 return code when connecting to theCME GC Allocator API - hosted by Google Cloud. To avoid this issue, please remove the "content-type" header from all GET requests targeting the CME GC Allocator API endpoints.
Due to a restriction within Google Apigee, query parameters with the same name cannot be repeated in a GET request. This restriction is in place to ensure predictable behavior and avoid potential ambiguity in how the API processes the request.
For example, the following previously supported request:
/trades/search?collateralStatus=NONE?collateralStatus=PARTIALmust now be submitted as two separate requests:
/trades/search?collateralStatus=NONE /trades/search?collateralStatus=PARTIAL
Clients can continue to use their existing OAuth API IDs to access the CME GC Allocator API in Google Cloud.
For BrokerTec GFE users: Following this change, BrokerTec GFE v11.2 and lower will no longer support allocating GC Repos via the 'GC Trades' tab. Please upgrade to the latest version (v11.5.1) available on the BrokerTec Support Portal if you are currently using GFE v11.2.
BrokerTec Chicago U.S. Treasury CLOB - Q3 2025
Effective Q3 2025, CME Group is launching BrokerTec Chicago, a secondary U.S. Treasury (UST) Actives Central Limit Order Book (CLOB) on CME Globex, operated by BrokerTec Americas LLC and located in the CME futures and options data center in Aurora, IL. BrokerTec Chicago is designed to enable clients to efficiently manage their cash vs. futures trading with greater precision. The products are tailored for cash vs. futures trading with tighter price and contract notional values aligning with futures, which differentiates this new venue from the existing BrokerTec U.S. Treasury Actives Market CLOB.
The new products offered with BrokerTec Chicago replicate the existing BrokerTec UST active instruments with similar contract size. The notional values for 1 lot size equivalents are $100k (5yr, 7yr, 10yr, 20yr, and 30yr) and $200k (2yr and 3yr) and the products have a price precision of 9 decimals (1/16 of a 32nd).
Clients with listed derivatives connectivity can access BrokerTec Chicago with existing cross-connects. Clients using BrokerTec Secaucus (GLink + EConnnect) connectivity can access BrokerTec Chicago, but require additional CME network and client-side configurations.
Trading hours for BrokerTec Chicago instruments are identical to the existing BrokerTec UST Actives instruments.
The connectivity details in the client impact assessment for BrokerTec Chicago have been updated.
| BrokerTec Chicago U.S. Treasury CLOB | ||||
|---|---|---|---|---|
| Product | MDP 3.0: tag 6937-Asset | iLink: tag 55-Symbol MDP 3.0 tag 1151 - Security Group | MDP 3.0: TAG 207-SecurityExchange | MARKET DATA CHANNEL MDP 3.0 TAG 1180 - APPLID |
| Chicago UST 2yr Bond | CB02 | CHBD | BTEC | 504 |
| Chicago UST 3yr Bond | CB03 | |||
| Chicago UST 5yr Bond | CB05 | |||
| Chicago UST 7yr Bond | CB07 | |||
| Chicago UST 10yr Bond | CB10 | |||
| Chicago UST 20yr Bond | CB20 | |||
| Chicago UST 30yr Bond | CB30 | |||
These BrokerTec Chicago U.S. Treasury CLOB products are currently available for customer testing for Order Entry, Market Data, and Straight Through Processing (CME STP) in New Release.
Product Changes
NewChange to Minimum Price Increment for European Union and Portuguese Cash Bonds on BrokerTec - July 6
Effective Sunday, July 6 (trade date Monday, July 7), the minimum price increment for the European Union and Portuguese Cash Bonds on BrokerTec will change as follows:
| Change to Minimum Price Increment for European Union and Portuguese Cash Bonds on BrokerTec | ||||
|---|---|---|---|---|
| Product | MDP 3.0: tag 6937-Asset | iLink: tag 55-SymbolMDP 3.0 tag 1151 -Security Group | Current tag 969-MinPriceIncrement | New tag 969-MinPriceIncrement |
| European Union Cash Bonds | EUBOND | EUCA | 0.01 | 0.001 for bonds maturing in 5 years or less, and 0.01 for bonds maturing in more than 5 years. |
| Portuguese Cash Bonds | PTBOND |
EUBD | 0.001 for bonds maturing in 2 years or less, and 0.01 for bonds maturing in more than 2 years. | 0.001 for bonds maturing in 5 years or less, and 0.01 for bonds maturing in more than 5 years. |
These changes will be made available for customer testing in New Release on Sunday, June 22.
RB Butterfly Spread Leg Convention Change - July 27
Effective Sunday, July 27 (for trade date Monday, July 28), the buy/sell convention of the RB Butterfly spread (SecuritySubType=RB) will change. This update will change the buy/sell direction of spreads from being relative to legs1 and 3 to being relative to leg2 of the spread, as outlined below:
| RB Butterfly Spread Leg Convention Change | |
|---|---|
| Current Leg Convention | New Leg Conventions |
| Buy Spread= Buy Leg1, Sell Leg2, Buy Leg3 | Buy Spread= Sell Leg1, Buy Leg2, Sell Leg3 |
| Sell Spread= Sell Leg1, Buy Leg2, Sell Leg3 | Sell Spread= Buy Leg1, Sell Leg2, Buy Leg3 |
| Spread Price= Leg1 Yield - 2 * Leg2 Yield + Leg3 Yield | Spread Price= - Leg1 Yield + 2 * Leg2 Yield - Leg3 Yield |
Please review the client impact assessment for detailed spread construction and pricing examples.
These changes will be available for customer testing in New Release on Monday, June 23.
Front-End Clients
Mandatory Upgrade: BrokerTec Sync Client 5.0 Upgrade - Now Available
This is a mandatory upgrade. BrokerTec Sync clients versions 4.x or older are no longer supported as of Monday, June 2.
The BrokerTec Sync client version 5.0.1 is now available to download on the BrokerTec Support portal. This new client contains security and stability updates.
Network Requirements
As our services migrate to Google Cloud, this new client version requires access to the following URLs over the public Internet from the BrokerTec Sync user’s workstation:
| BrokerTec Sync Portal | |
|---|---|
| Current URLs (Clients version 3.x/4.x) | New URLs (Client version 5.0+) |
| https://sync.brokertec.com https://paging.numecentcloud.com |
https://markets.api.cmegroup.com/brokertec/sync-portal https://paging.numecentcloud.com (no change) |
Installation Requirements
Please note that customers upgrading from a previous version of the BrokerTec Sync client will be prompted to reboot their workstation during the upgrade process. To minimize disruption, we strongly encourage customer support teams to schedule this upgrade at an appropriate time.
Any client inquiries for technical issues or production support should be directed to the CME Group Global Command Center (GCC) in the U.S. +1 800 438 8616, in Europe at +44 20 7623 4747, in Asia at +65 6532 5010 and in Japan at +81 3 6733 7559.
BrokerTec Global Front End Upgrade Client 11.6 - July 2025
In early July, there will be a new BrokerTec Global Front End (GFE) Client 11.6 software upgrade. Firms that need to package the BrokerTec GFE Client for distribution can download version 11.6 when it is available.
Customers using BrokerTec Sync will automatically be upgraded to the latest version.
The software release includes:
- BrokerTec Quote Integration with the U.S. and EU Repo CLOB to enable the sell-side to trade and manage orders between the two different market segments on a single screen. Enhancements in the Global Front End include a new Quote RFQ tab in Log Book to view, negotiate and respond to incoming request-for-quotes (RFQs)
- Support for Straight Through Processing (STP) in Google Cloud will be available in Q3 2025. For customers with BrokerTec GFE set up to consume STP via the Internet, please ensure the new endpoint (stpfix.api.cmegroup.com (208.112.128.43) on port 443) is accessible from trader’s workstations.
- Technical Enhancements aimed at improving application stability.
Any client inquiries for technical issues or production support should be directed to the CME Group Global Command Center (GCC) in the U.S. +1 800 438 8616, in Europe at +44 20 7623 4747, in Asia at +65 6532 5010 and in Japan at +81 3 6733 7559.
Post-Trade
CME STP FIX on Google Cloud - Production Internet Connectivity - Now Available
On Sunday, May 11 (trade date Monday, May 12), CME Group enabled the Production internet connectivity options for CME STP FIX API as part of a phased migration of CME Straight Through Processing APIs to Google Cloud.
CME STP FIX service will operate in two regions, the Eastern and Central United States.
Clients have two different options for internet connectivity to CME STP FIX on Google Cloud.
| CME STP FIX on Google Cloud - Production Internet Connectivity | ||
|---|---|---|
| Connectivity Option | CME STP FIX Hostname(s) | Usage |
| Managed | stpfix.api.cmegroup.com *[208.112.128.43] |
Clients only need to connect to a single Host for all STP data that they are entitled to. CME Group will manage regional connectivity. |
| Regional | 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 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. |
*Client systems are required to target the Hostname(s). IPs are provided for convenience of client side whitelisting.
CME STP FIX is accessible on port 443. Clients can use their existing API credentials.
CME STP FIX on Google Cloud is available in parallel to the current on-prem instance. Clients should ensure that they do not double-book trades if connecting in parallel to Google Cloud and on-prem instances.
View the client impact assessment for additional information.
Events and Announcements
BrokerTec and EBS Customer Disaster Recovery Exercises - July 19
The CME Group Disaster Recovery exercises allow you to verify your ability to transact on CME Globex DR systems. Two exercises for cash markets will be offered on the following dates:
- Saturday, July 19 - Europe Markets (BrokerTec and EBS)
Pre-registration is required for each individual participant to ensure access and support readiness. Registration is now open.
Test scripts are now available below:
