The bottom line, is less than 1% of the miners are having problems. That doesn't mean there aren't problems, but chances are it's not with the pool. That doesn't mean your doing anything wrong, but it could be a bad dns entry between you and slush, or some issue between your isp and the amazon servers, or any of thousands of other weird little things that can happen on the internet.
That's why your getting the response you are. If you report a problem, then slush checks everything on his end and finds everything is good. Then there is nothing he can do about it. And I now what your going to say next, slush hasn't reported back. Well I can assure you, he has seen your posts, and if there was anything he could do about it, it would have been done already.
A=B, and B=C, therefore A=C, maybe a little simplified, but the principal is sound.
I bet you 1BTC that he didn't read them... And how did you figure out 1%? do you have access to the pool? And seeing pool accepting shares and then not recording them is a pool problem for sure. Also recording them to the wrong worker is a pool problem. Seeing one worker connecting and other not with same configuration is a pool problem...
