Yes, the 128k feed, as I said above, is on its own separate server. So, when you say it's related to a lot of listeners, you mean 5 or so for the 128k stream. I'm listening now with no problems (4 listeners, 60 56k listeners even though the number of 56k listeners has no relation to anything). Again, the 56k server can have 10,000 listeners, and it doesn't matter - the 128k stream always have between zero and 7 users or so. And that's nothing for a colocated connection (around 800 k/sec).
The fact that Jim chimed in and said he's isn't having any problems with the 128k at home or work, and at the same time you guys were having problems, still makes me suspicious.
Plus, I think I would get a TON of emails from the other subscribers if it was a server problem - but I haven't (you should see the number of emails I got when the subscriber stream went down because of tech reasons a few weeks ago). I also checked the logs for the subscriber stream, and there were no buffer underruns for any of the listeners when you guys were having problems.
Again, I'm not discounting that there might be a problem - just laying out the evidence and thinking it through.
To see how many listeners there are at any time, enter the stream address into your web browser (don't post the subscriber address in the forums).
Please post here if you are having problems today. Post the time and the number of 128k listeners (not 56k listeners).
Have you guys tried other 128k streams to test? Go to
http://www.shoutcast.com and click on a few 128k streams (search for prog if you want - there are a few prog 128k streams out there), and see how they do for you.
Also: try to ping and traceroute the subscriber server. Go to a command line and type ping <server address> and tracert <server address> and see what numbers it comes up with. Post them here.