NOTICE:
Im aware that some users actually permanently stayed on their backup pools, all I can think is that their backup pool configuration in their miners stuffed up or they didnt update to cgminer 2.4.1
CGMiner 2.4.1. did not resolve this issue, sometimes the pool stays on 'rejecting' state even though it is working fine again
Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares

It was resolved for everybody else and all other pools. I can testify to this.
It is just your sucky proxy pool that has very high rejects and it keeps getting disabled.
No need to ask ckolivas to change cgminer. 2.4.1 has no bugs AFAIK.
Tell your miners to use the
--no-pool-disable switch when at your pool and turn the switch off when at other normal non-proxying low reject pools

Good luck !
if it was specific to this pool, all my mining rigs would stay connected to my backup pool.... they don't.... sometimes 1 or 2 of them keep hashing away at the backup pool, while the others happily switch back to Clipse.... seems clear enough to me !
Seems you are right.
I was just reporting that cgminer 2.4.1 does not seem flawed to me.
The pool failover system does work for me while using a normal pool because it detects LP requests. Proxy pools do it differently probably as they don't have their own LP I think.
Carry on and don't let me distract you. I was just saying I believe cgminer is not at fault here. Maybe there is an incompatibility between cgminer and proxy pools due to how LP is handled ?
Not disappointed at all Clipse. On the contrary, I found using your pool much less rewarding compared to a normal pool simply because of the high reject % and that is why I stopped mining.
I gave you a "sorry, let me back in" PM so I could try again and see if the reject ratio went down but you don't like me ...