In the last week we've been seeing very unusual (at least for us) behavior on the .NET realtime API. Every morning for the last week we have received flapping disconnect and reconnect messages 2-3 seconds apart (OnFeedStateChanged saying IDN_RDF state is FeedState.Down, followed a few seconds later by IDN_RDF state is Up). This has occurred at least once every day since Monday, always between 10:20 AM and 11:40 AM ET. The last two days (Wednesday and Thursday) it occurred at exactly 10:59:19 ET, even more strangely.
Odd thing is that the feed seemed perfectly healthy before receiving those feed status down messages (see below log extract). Any idea what could be causing this all of a sudden?
4/25/2019 10:59:16 AM - Update messages per sec: 1072
4/25/2019 10:59:16 AM - Field updates per sec: 3440
4/25/2019 10:59:17 AM - Update messages per sec: 881
4/25/2019 10:59:17 AM - Field updates per sec: 2787
4/25/2019 10:59:18 AM - Update messages per sec: 1035
4/25/2019 10:59:18 AM - Field updates per sec: 3303
4/25/2019 10:59:19 AM: Reuters Feed IDN_RDF State is now Down
4/25/2019 10:59:19 AM: Reuters Feed ELEKTRON_CON State is now Down
4/25/2019 10:59:19 AM - Update messages per sec: 1492
4/25/2019 10:59:19 AM - Field updates per sec: 4793
4/25/2019 10:59:20 AM - Update messages per sec: 0
4/25/2019 10:59:20 AM - Field updates per sec: 0
4/25/2019 10:59:21 AM - Update messages per sec: 0
4/25/2019 10:59:21 AM - Field updates per sec: 0
4/25/2019 10:59:21 AM: Reuters Feed IDN_RDF State is now Up
4/25/2019 10:59:21 AM: Reuters Feed ELEKTRON_CON State is now Up
4/25/2019 10:59:22 AM - Update messages per sec: 156
4/25/2019 10:59:22 AM - Field updates per sec: 1241
Given that you seem to be receiving streaming updates up until you get the feed status down message, and how quickly the feed is reported up after being reported down, I don't believe this can be caused by anything happening on the machine running Eikon. I also don't believe this is a result of the comms failure. I think most likely the feed status changes are generated and sent to you by distributor server known as ADS, which is part of TREP infrastructure in Refinitiv datacenter that delivers streaming data to your Eikon terminal.
Since the issue doesn't seem to have any impact, I suggest you ignore it. One or two seconds of lost updates doesn't count as impact, as Eikon over the Internet cannot provide the quality of service where you can rely on receiving every update. For such quality of service you would need a much more expensive solution.
This said, if you'd like to have this investigated, you need to open a service case with Refinitiv Helpdesk. Refinitiv Support can take a look at the logs on the ADS your Eikon was connected to at the time the issue occurred. If my hypothesis is correct, this should help determine why ADS briefly reported the source feeds down.