If your Audio Player starts up, tries to connect and then fails, there could be a couple of issues.
It’s possible that your Player doesn’t support MPEG streams (though that’s unlikely in this day & age). If so, there are plenty of other Player options described here.
There could easily be a problem with the data route between your device and my transmitter out there in the Cloud.
Any web service can briefly get ‘eclipsed’ – disappear, becoming inaccessible from the outside world for a time, and then come back again as if nothing ever happened.
TCP-IP be like; “Hey, what’s up. Did you miss me? Aww, you look sad. Were you listening to something?”
Even when you have a successful connection, sometimes it might just drop out for about 5 seconds, then come back again. Or you could hear brief audio ‘hiccups’. This is likely due to network congestion – hooray for [buffering]
You make wake in the morning to find that you’d been disconnected at some point in the night. Sometimes during a ‘hiccup’, your player may lose the connection and not be able to re-establish it.
And this, kids, is what happens when you overload a system designed by DARPA in the 70s.
My stream might actually be offline. S E B does experience an outage on - ahem - rare occasion.
You can easily check that option by search for my SHOUTcast listing. If that doesn’t return any results, then … yeah, something’s probably up on my end.
There was a time, way back in the day, when the stream might even max-out – it wouldn’t have any more available connections. Fortunately, that is not an issue anymore.