I have a stable total hashrate being a bit more than 4 GH/s and almost stable block payout about 0.10 BTC.But the 14206th block payout suddenly dropped to ~0.02Next one was normal so I left it to network problems.

But now I'm observing a zero-like estimated reward whilst all others pool and my rig parameters are stable and fits theirs default ranges.

Please see below the screenshot - split into 2 parts just for not wasting space and being easy to read.

The estimate reward

Workers' stats

I wonder if it can be an issue of scoring algorithm?

Edit: Ok, all are already aware of an issue.Hope it'll be resolved quickly and easily, as Slush always has logs of everything

There was lockup in database, I recalculated rewards and it should be fine now. Now I'm watching logs for some indices what happen.

I got a reward considerably lower than normal (roughly half) on block 202299 after 2 hours+ full steam hashing. It did not correct in your update, was it supposed to be that low or is possible there was another lockup or event that caused it?

I got a reward considerably lower than normal (roughly half) on block 202299 after 2 hours+ full steam hashing. It did not correct in your update, was it supposed to be that low or is possible there was another lockup or event that caused it?

Unfortunately there's no way how to recalculate already confirmed rounds, because these rewards has been already paid out. For now I cannot say if your lower reward for 202299 was the same issue like hour ago, but I'm optimizing some code to prevent current issue to happen next time.

I got a reward considerably lower than normal (roughly half) on block 202299 after 2 hours+ full steam hashing. It did not correct in your update, was it supposed to be that low or is possible there was another lockup or event that caused it?

Unfortunately there's no way how to recalculate already confirmed rounds, because these rewards has been already paid out. For now I cannot say if your lower reward for 202299 was the same issue like hour ago, but I'm optimizing some code to prevent current issue to happen next time.

I just finished database maintenance and some code optimizations. I had to restart pool application so I'm sorry for bunch of rejected shares. However problems in reward calculations should be fixed now.

If somebody is using latest stratum proxy (git sources/1.0.0) together with latest cgminer (2.8.1), please check your miners. They most likely crashed during recent pool restart. I'm working on bugfix right now, should be available on github in few minutes.