Direct answer: Where is CME Globex hosted?
CME Globex’s matching engine is still in Aurora, Illinois, in the facility CME originally called DC3, which CyrusOne renamed Aurora I after buying the building. CME sold the data center to CyrusOne in 2016 under a 15-year leaseback, which keeps Globex hosted there.
| Matching engine | Aurora, IL (CyrusOne Aurora I) |
| Physical co-location | CME GLink Aurora |
| Markets affected by cloud move | Listed futures and options |
| Not affected | EBS and BrokerTec |
| Chicago cloud migration | Begins late 2027, completes 2028 |
CME’s move to Google Cloud: what it means for connectivity
In June 2024, CME Group and Google Cloud announced a new private Google Cloud region and co-location facility in Aurora. CME’s current schedule has Globex production markets starting to move to that Chicago region in late 2027. Until the migrations finish in 2028, GLink Aurora remains the only physical co-location service and the fastest route to Chicago-hosted markets.
Two interim milestones matter for planning:
- Livestock futures and options move to a production environment in Google Cloud’s Dallas region in Q4 2026, then to the Chicago region in the second half of 2028.
- A production-like sandbox in the Dallas region went live on June 15, 2026 for clients to test connectivity and performance.
The new region will offer both self-managed co-location, similar to today, and Google’s managed infrastructure option, with equal network latency to the markets from either. Firms signing multi-year circuits into Aurora now should confirm how their routes will reach the new facility, and whether term commitments line up with the migration window.
Common routes into Aurora
- New Jersey to Aurora: links NY4/NY5 (Equinix, Secaucus), Nasdaq (Carteret) and NYSE (Mahwah) with CME. This is the most performance-sensitive corridor in U.S. markets.
- Chicago metro to Aurora: connects carrier hotels such as 350 E. Cermak, firm offices, and backup sites.
- Cloud to Aurora: supports hybrid designs that pair on-premises trading with cloud analytics, data or DR.
- International: London (LD4) and other global venues, usually via New Jersey or Chicago hubs.
Wireless vs. fiber on the Chicago–New Jersey corridor
Specialized microwave and millimeter-wave networks deliver the lowest latency on this route. They carry less bandwidth and can degrade in heavy weather. Fiber is slower but offers high capacity and consistent availability. Many firms run wireless for latency-critical order flow and fiber for market data, bulk traffic and failover.
What to define before requesting CME routes
- Exact endpoints: origin facility and suite, destination handoff, and who orders the cross-connects.
- Traffic type: order entry, market data, or both, plus bandwidth at peak market activity.
- Latency method: one-way or round-trip, measurement points, jitter tolerance.
- Diversity: whether primary and backup paths share conduit, towers, building entrances or equipment.
- Migration horizon: how the circuit will serve the Google Cloud region after 2027.
CME connectivity FAQ
Where is the CME Globex matching engine located?
In the CyrusOne Aurora I data center in Aurora, Illinois.
Is CME moving Globex to Google Cloud?
Yes. Production markets start moving to a private Google Cloud Chicago region in late 2027, and GLink Aurora remains the physical co-location service through the end of migrations in 2028.
Does the migration affect BrokerTec or EBS?
No. The move covers listed derivatives only.
What is the fastest route from New Jersey to CME?
Specialized wireless networks on the Chicago–New Jersey corridor. The right choice depends on bandwidth needs, weather tolerance and backup requirements.
Can SpartaLink compare multiple CME route providers?
Yes. SpartaLink is provider-neutral and compares wireless and fiber options side by side against your endpoints, performance targets and budget.
Share your origin, destination, bandwidth, latency objective and service date.
Discuss a CME Route →