Regarding that block #17925 I suspect what's the problem .
From what I can see it appears that majority of the folks didn't submit any shares in the last X minutes while others did continue to submit shares.
The most reasonable explanation to this is that there was some network issue (routing or clogged traffic) and something happened to **some** of the pool's endpoints but not to **all** of them.
In other words - a few of the IPs listed below may have been DDoS-ed, and those that were connected to them suffered as they were unable to submit their shares, while the unaffected IPs worked just fine and those people connected to them did get their (at that point) fair share:
that's from a few days ago:
C:\Users\me>nslookup stratum.bitcoin.cz
Server: rdns-lb-01.orange.rr.com
Address: 66.75.160.63
Non-authoritative answer:
Name: stratum.bitcoin.cz
Addresses: 54.225.117.74
54.215.3.100
54.215.3.101
54.215.3.102
54.215.3.103
54.225.68.97
54.225.116.40
54.225.116.174
54.225.116.221
and looking at my currently connected worker - I am currently connected to one of those:
TCP 192.168.0.70:54312 54.215.3.103:3333 ESTABLISHED
Unfortunately I don't think slush would have any (easy) means to find out which IPs of the pool worked at that time and which didn't. If that's the case then I guess all I have to say to the winning folks - congrats for the bonus!
(that's unless slush wishes to manually recalculate the payout for that block, but the time for this is running out rather quickly too)