Feed Connectivity Requirements

Gig-Shaped feeds are available to participants who meet the minimum bandwidth requirements to Cboe via cross-connect, dedicated circuit, or a supported carrier.

Participants with sufficient connectivity may choose to take both the A and B feeds from Cboe’s primary datacenter and arbitrate the feeds to recover lost data. Alternatively, participants may choose to arbitrate feeds from both datacenters. It should be noted that feeds from the secondary datacenter will have additional latency for those connected with Cboe in the primary datacenter due to proximity and business continuity processing.

Multicast Top real-time events are delivered using a published range of multicast addresses divided by symbol range units. Dropped messages can be requested using a TCP/IP connection to one of Cboe’s Multicast Top Gap Request Proxy ( GRP) servers with replayed messages being delivered on a separate set of multicast ranges reserved for packet retransmission. Intraday, a spin of current top of book may be requested from a Spin Server.

The following diagram is a logical representation Multicast Top feed message flow between Cboe and a participant feed handler that is listening to the A and B instances of two units: