I am a feed provider and 4 days ago started receiving random Error code 1 and Error code 10 issues with disconnects. There hasn't seemed to be any pattern to these errors (day, night, overnights). My feed provides redundancy in this area of NYS, however I've noticed my "listeners" have dwindled over this period, most likely due to the frustration with random disconnects. I am using Proscan Source Clent, with a BCD536HP and WiFi dongle connection. Prior to becoming a new feed provider, I was using ProScan Web Server for my own use away from home (or upstairs lounging on the sofa) with no issues, no errors for 3 months since install. My provider is Spectrum, and I am consistently in the 350-390 mbps range on speedtests.
I searched here on RR for any feedback/solutions. Despite getting a few hits, I have not found any resolution to the issue in any of the threads I was able to pull up. I've decided to do my own sleuthing. Bob @ProScan did provide some good details in a couple of the threads on potential sources of the errors. He mentioned more than once utilizing PingPlotter to help identify the source of the errors. Never heard of it, decided to download it. Turns out, the program is quite intuitive with a very helpful online tutorial.
My preliminary findings are captured in the snapshots below. Using Broadcastify as the target IP, it appears that there is a severe latency issue on hop #6, which is a Charter (Spectrum) IP (identified as COUDERSPORTBB-2 using WHOIS.com). Now, knowing that there have been Spectrum outage issues very recently, not to mention the Amazon Cloud outage, I am not sure if I am going to take it further at this point, rather a wait and see approach. So far my router (hop#1) connection shows no issues, nor do any of the other hops (why does it take 19 hops to get there??). More importantly, it shows there are no issues with ProScan or the Broadcastify target for my feed.
Obviously, I don't have a solution yet (it seems out of my hands), but with this info, I believe I can engage Spectrum support IF I need to take it further. I hope it doesn't come to that point
Then again, I may be totally off base and not interpreting my findings utilizing PingPlotter correctly. I just wanted to post here as I know others have seen this issue.
Jim



I searched here on RR for any feedback/solutions. Despite getting a few hits, I have not found any resolution to the issue in any of the threads I was able to pull up. I've decided to do my own sleuthing. Bob @ProScan did provide some good details in a couple of the threads on potential sources of the errors. He mentioned more than once utilizing PingPlotter to help identify the source of the errors. Never heard of it, decided to download it. Turns out, the program is quite intuitive with a very helpful online tutorial.
My preliminary findings are captured in the snapshots below. Using Broadcastify as the target IP, it appears that there is a severe latency issue on hop #6, which is a Charter (Spectrum) IP (identified as COUDERSPORTBB-2 using WHOIS.com). Now, knowing that there have been Spectrum outage issues very recently, not to mention the Amazon Cloud outage, I am not sure if I am going to take it further at this point, rather a wait and see approach. So far my router (hop#1) connection shows no issues, nor do any of the other hops (why does it take 19 hops to get there??). More importantly, it shows there are no issues with ProScan or the Broadcastify target for my feed.
Obviously, I don't have a solution yet (it seems out of my hands), but with this info, I believe I can engage Spectrum support IF I need to take it further. I hope it doesn't come to that point
Jim


