Slush is down. "502 Bad Gateway". Since they score based on uptime this is unacceptable (everybody should get scored equally for the round when it comes up which hurts the people who have been continuously mining and those who stopped, but they can take it out of their "profit" to payout to the miners who were no up full-time since it is a site error and clearly the server they are using is not robust (nginx/0.7.65 .... come on, 1.0 was released awhile ago!).
I would guess this is the same thing that happened before. Not really a big deal.
https://bitcointalksearch.org/topic/m.77673
In hind sight, it was just the web server and not the pool. There should be monitoring software in place to watch bitcoind among other services and daemons; it is open source and not expensive to implement. Also, the site should give a message other than 502 if something recurring like this goes down; simple matter. Without access to the website, I cannot tell if the miner is processing good shares or stale shares [no idea if the pool is working correctly]. These are simple matters for hosting [no, I don't host a website, but I am very familiar with administering Linux/FreeBSD even though I am a software engineer (Microsoft products primarily) by trade].
If you look at http://bitcoinwatch.com/ right now, you will note that slush has almost zero contribution at the moment. That suggests to me that something bigger is going on [are all shares processed today stale at this point?].
