Critical System Information

UpdatePersonally Identifiable Information (PII) Process Transition - November 22

† Denotes update to the article

To be enabled for trading, all BrokerTec EU and UK participants are required to submit Personally Identifiable Information (PII) for manual traders and operators of algorithmic trading systems, for the operator of the BrokerTec EU (CME Amsterdam B.V.) and UK (BrokerTec Europe Limited) trading venues, to meet MiFID II/MiFIR transaction reporting and record keeping requirements. Participants are currently able to maintain PII via the NEX Upload Facility (NUF).

†On Saturday, November 22, CME Group will replace the NUF process with the new PII process in the Request Center (ESS) within CME Customer Center.

The new PII process will offer participants improved visibility into each trader's PII status and allow for both individual PII maintenance and bulk uploads.

A new PII Manager role will be available in the Request Center and granted to current NUF users having an existing CME Group Login ID. User Administrators within each firm will manage the assignment of this new role to staff members, delegating PII maintenance responsibilities on behalf of their organization. It is required to create a CME Group Login with multifactor authentication to be granted the new PII Manager role.

Existing valid PII records will be transferred to the new PII process, where they will be accessible for the PII Manager to maintain using the new PII process.

Additional details will be announced in future notices. Please contact Global Account Management with questions or comments.

All personal information provided by customers is used, distributed, and maintained in accordance with CME Group’s Privacy Notice.

Front-End Clients

Mandatory Upgrade: BrokerTec Sync Client 5.0 Upgrade - Now Overdue

This is a mandatory upgrade. BrokerTec Sync client 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 (Client 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.

Post-Trade

CME STP FIX on Google Cloud - Production Internet Connectivity - Now Available

Production internet connectivity options for CME STP FIX API are now available 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.

A required message recovery certification is now available for CME STP FIX on Google Cloud. Please contact Certification Support for Electronic Trading (CSET) with any questions in the U.S. at +1 312 930 2322, in Europe at +44 20 3379 3803 or in Asia at +65 6593 5593.

View the client impact assessment for additional information.