I have thought long and hard about how to reply to this, as the operator/provider of the audio feed(s) in question.
I'm going to start out with the feed uptime history for the last 30 days:
There are a few dimples in the graph, but for the last 30 days, the feed has been "up" and "operating" more than 95% of the time. I'm sure that if pressed, uptime statistics for far longer could be provided.
Today, I took the system down for some long overdue maintenance. (See the second attached image.) You know, installing the dreaded Windows Updates, running a full virus scan, performing a full backup of the disk, in order to be able to continue providing the service reliably. The quality of the feed degrades if I attempt to do all that with the feeds running, so I take them down so that I don't get complaints about the quality of the feed.
ALL of the RadioReference.com (and soon Broadcastify.com) live audio feeds are provided by volunteers who are free to put the feeds up and take them down as often, or for as long as they like (subject to a few restrictions). The feeds are not guaranteed -
anywhere to be available with any SLA: if they're down, they're down.
When the feeds go down, I am automatically notified twice: once by my own system and once by RadioReference.com for EACH FEED. I don't need facebook messages, "feed problem reports", emails, or any other notices. I work a day job. On a radio. 40+ hours a week. I don't sit in front of the feed computer 24/7/365 when I'm not working and wait for a problem so I can fix it. When a problem comes up, I will take care of it as soon as I can - getting bombarded with other messages isn't going to make the end of my shift come any sooner, or get me back home from the coast any faster, or anything else I might be doing (for example, I just got back from 4 days in the Nevada desert - if the feed(s) had gone down while I was gone, guess what? They would have stayed down until I had gotten back and settled in.)
I try to wait for a time period where there is nothing "big" happening so that I can take care of routine maintenance activities without disturbing people from being able to listen to a potential "big event". Usually this works just fine. Sometimes it doesn't.
I also
don't listen to the audio from my feeds frequently. I have separate monitoring facilities that I can include the things I want to listen to (as opposed to just my advertised feeds), and so if there is a problem with a feed (for example, when the Portland Fire scanner quit scanning and was stuck on Tapout a few weeks ago), that is when I
welcome Feed Problem Reports. But, as I stated above. If I am out of town, at work, or somewhere that I don't have the facilities to troubleshoot the problem being reported, IT WILL TAKE TIME to resolve.