Heartbeat Messages

The Sequenced Unit Header with a count field set to 0 will be used for Heartbeat messages. During trading hours Heartbeat messages will be sent from the GRP and all multicast addresses if no data has been delivered within 1 second. Heartbeat messages never increment the sequence number for a unit, but can be used to detect gaps on the real-time multicast channels during low update rate periods.

Heartbeat messages on the real-time multicast addresses during trading hours will have a Hdr Sequence value equal to the sequence of the next sequenced message to be sent for the unit. Heartbeats on gap multicast addresses will always have the Hdr Sequence field set to 0. All Heartbeat messages sent to and from the GRP are considered un-sequenced and should have sequence and unit fields set to 0.

Outside of trading hours Cboe sends Heartbeat messages on all real-time and gap channels with a sequence of 0 to help users validate multicast connectivity. Heartbeat messages may not be sent from 12:00 a.m. - 1:00 a.m. ET or during maintenance windows.

Cboe expects Heartbeat messages to be sent to the GRP and Spin Servers on live connections no less than every 5 seconds. Failure to receive 2 consecutive Heartbeat messages will result in the GRP or Spin Servers terminating the client connection.