Mine was low to. But in my part my miners were redirected again right at the end of the round. So slushes antipool hopping code got me good. Is anyone elses bfgminer being redirected to the russian IP still. I was fine all week and got hit twice this weekend. My equipment is in a remote data room, running all BFL hardware. Good thing for API.


Things I wound helpful was checking that slush is the only pool in the pool list , deleting  bfgminer.conf and starting whole hing from BAT with SLush pool as only pool showing.
Seems to me that then work was done you will get bogus block from slush just to try and stop pool hooping.

What should happen is that once block is solved and no more new block are found all
your miners should start working on bogus block just to make sure you stay on slush
when it's dinner time

There is always Murphy's low , my computer went out yesterday and I only started mining this morning (there was an blackout with all the power in the house) so go
figure

When you want to use another pool do the same thing , single BAT that will show
your pool of choice as only pool (not active) buy only pool showing , when you want to go back to slush just use different bat and report results.

It's not that well done in BFGMiner I must say and you still have to monitor from time to time that no new pool found it's way in but it can only do that through bfgminer.conf file.My theory is that when your miner sees no more mork on slush it hops to pirate pool.

Anyway best of luck

My BAT EXample :

bfgminer -o http://stratum.bitcoin.cz:3333 -u Eagle92212.1 -p xxxxxxx -S antminer:all --set-device antminer:clock=x0981
 
Worked so far.

However high speed workers are probably better targets.