A lot of 'channel down.' message at around 09:30 UTC+8

Y_Intercept

Hi LSEG,

We are using Real-Time Direct with C# SDK. We receive a lot of these messages from Refinitiv at ~09:30 UTC+8:

2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000001.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000002.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000006.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000008.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000009.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000011.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000012.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000016.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000019.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000021.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000025.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000027.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000028.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9675 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 000029.ZK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2537.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2538.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2539.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2540.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2542.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2543.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2545.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2546.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2547.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2548.TW, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2550.HK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2555.HK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2556.HK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 257720.KQ, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2579.T, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2585.T, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2587.T, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2588.HK, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2590.T, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 
2024-12-05 09:30:42.9878 | 40 | INFO | PriceDataMsgConsumer           | Refinitiv StatusMsg: Name: 2602.T, ServiceName: hEDD, State: Open / Suspect / None / 'channel down.' 

We are aware that 09:30 are busy hours as it is market open in China, but we does not expect it to impact Japan/TW too. What is the usual cause of this?

Gurpreet

Hello @Y_Intercept,

Channel down is sent out by the API when it gets disconnected from the market data infrastructure. This disconnect can happen due to the network issues, or due to problems on the market data side.

If the issue is in the MD infrastructure, your administrator would be able to see the server logs and point out the reason for disconnect. More likely, this was a network contention issue, and your network admin should help troubleshoot it.