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
iLink and Drop Copy 4.0 for iLink Configuration File Updates - This Week
Effective this Sunday, June 8, the production config.xml files for iLink and Drop Copy for iLink will be updated to support the BrokerTec Chicago - U.S. Treasury Actives - CLOB on CME Globex.
The configuration information (i.e. market segments and IPs) will be added on the corresponding production config.xml files for:
- Market Segment Gateway (MSGW)
- Order Entry Service Gateway (OESGW)
- Drop Copy for Market Segment Gateway (DCMSGW)
Details on accessing the configuration files are available via the Client Systems Wiki.
| SFTP SITE: SFTPNG.CMEGROUP.COM | |||
|---|---|---|---|
| Market Segment Name | Market Segment ID | Configuration File SFTP Directory | File Name |
| BrokerTec Chicago MSGW for DC3 network connections | 48 | /MSGW/Production/Configuration | MSGW_Config.xml |
| BrokerTec Chicago MSGW for NY5 network connections | 48 | /MSGW/Production/Configuration | MSGW_NY5_Config_BrokerTecChicago.xml |
| BrokerTec Chicago OESGW for DC3 network connection | 14 | /MSGW/Production/Configuration/ | MSGW_config.xml |
| BrokerTec Chicago OESGW for NY5 network connection | 14 | /MSGW/Production/Configuration | MSGW_NY5_Config_BrokerTecChicago.xml |
| BrokerTec Chicago Drop Copy for DC3 network connection | 48 | /DCMSGW/Production/Configuration/ | DCMSGW_Config.xml AND DCMSGW_Config_BTEC.xml |
| BrokerTec Chicago Drop Copy for NY5 network connection | 48 | /DCMSGW/Production/Configuration | DCMSGW_NY5_Config_BrokerTecChicago.xml |
These changes are currently available in the corresponding config.xml files in New Release.
UpdateBrokerTec Chicago U.S. Treasury CLOB - Q3 2025
† Denotes update to the article
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 and Market Data in New Release.
† Straight Through Processing (CME STP) will be available for customer testing in New Release Sunday, June 8.
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.5.1 - Now Available
On Tuesday, May 13, a new BrokerTec Global Front End (GFE) Client 11.5.1 software upgrade was released. Firms that need to package the BrokerTec GFE Client for distribution can download and distribute version 11.5.1 once it is available.
Customers using BrokerTec Sync have begun automatic upgrades to the latest version starting May 13.
This update to the existing GFE 11.5 release includes the following:
- ICAP TIPS Matching - Improved support for ICAP TIPS matching, including:
- Ability to copy and paste positions into matching via Excel
- ‘My trades’ monitor available in matching window
- Trader protections from mid-level updates during matching:
- Orders are cancelled from lines with mid-level changes
- Mid-level changes are highlighted in orange for 20s
- Orders from prior matching sessions are persisted for ease of re-submission
- 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.
CME GC Allocator API Migration to Google Cloud - Now Available
The CME GC Allocator API is now available in Google Cloud.
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 |
The current URLs for CME GC Allocator API endpoints will be decommissioned in Q2 2025:
- New Release was decommissioned on April 12
- Production will be decommissioned on June 23
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.
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.
Announcements and Additional Resources
New CME Group Login Password Requirement - June 14
Security practices continue to be critically important across financial services. CME Group has consistently leveraged security best practices including password standards.
Effective Saturday, June 14, the minimum password length for new CME Group Login accounts will increase to 12 characters. This change will also be applied to any new passwords created for existing accounts.
CME Group Login provides access to CME Group applications, services and premium digital content.
For related inquiries, please contact EASE@cmegroup.com
BrokerTec and EBS Customer Disaster Recovery Exercises - June 14
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, June 14 - U.S. Markets (BrokerTec and EBS)
- 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:
- EBS Markets (on New York Matching engine)
- EBS Markets (on London Matching engine)
- BrokerTec Americas Markets (on New York Matching engine)
- BrokerTec EU/UK Markets (on London Matching engine)
Redesigned Request Center Within CME Customer Center - June 15
Effective Sunday, June 15, the Request Center within the CME Customer Center self-service functionality will feature a simplified, redesigned interface and streamlined navigation. For a clear and consistent experience across CME Group services, the Request Center will include updated terminology and instances of spelled out acronyms.
There will be no major functional updates to the user interface at this time and access will remain based on individual CME Group Login entitlements.
Currently, "Registered Entity" or "Administration Group" identifies a customer firm within the Request Center and the redesign will feature "Administration Group" for consistency.
Acronyms currently in the user interface will be spelled out, such as "Globex Firm ID," "Futures and Options" and "Order Entry" naming will identify the "iLink Sessions."
