As far as I know there there was no network drop and nothing went down from what I can tell.
I have two separate connections coming that are bridged and then connected to the switch my miners connect to. Even if i lost one incoming line the other one would have still carried the load. I have been looking as far back as I can and didn't see anything off, no loss of connection no miners dropping, just seems like I got the shaft.
I did submit a ticket, but I do that for every problem and never hear anything back. There is always a slight variance to the number of shares my miner pulls compared to the pool since they can not seem to find a var diff they like they are always bouncing around, I just go with it since this is more of a hobby for me then anything, but it is just discouraging when I get hit with a problem like this.
crashoveride54902 - What pool did you move to? I am considering jumping ship, its just a tough choice since I have been here since 2011, and it has never given me this much trouble as it has in the past month.
You can try to divide your hashing power between a couple of pools (mining clients such as bfgminer and cgminer allow you to set up a 'load balance' among multiple pools). The division doesn't have to be equal, you can apportion some fraction to another pool (or pools) to act as a 'monitor'. Or you can divide your hashing resources equally between a few pools as a 'spread the risk' approach. The 'monitoring' would not give you the 'full picture' though, as Slush's short-term 'anti-hopping' thing is unique (some people claim that it can be exploited as well, as you'd get the full reward if you hopped back to Slush just a few minutes before the end of a block).
Cheers