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

Y_Intercept
Newcomer
in EMA
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?
Tagged:
0
Best Answer
-
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.
2
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛