Ganz offensichtlich sollte der King High Flush nicht gegen einen Ace High Flush gewinnen. Cake poker arbeitet zur Zeit auf hochtouren um den Fehler in der Software zu finden. Den orginal Thread bei two plus two mit den statements von Lee Jones, dem Cardroom Manager findet ihr hier.

Hero (UTG): $6.78
MP: $2.35
CO: $1.13
BTN: $2.71
SB: $1.81
BB: $3.94

Pre Flop: ($0.06) Hero is UTG with 2 T
2 folds, MP calls $0.04, BTN calls $0.04, 1 fold, BB raises to $0.28, MP calls $0.24, BTN raises to $2.71, BB raises to $3.92, 1 fold

Flop: ($5.72) 4 4 8

Turn: ($5.72) 6

River: ($5.72) 9

Final Pot: $5.72
BTN shows A Q
BB shows K K
BB wins $5.36
(Rake: $0.36)

POlkas Meinung dazu:

Scheisse passiert, was einen guten von einem schlechten Poker Anbieter unterscheidet ist wie er mit solchen Problemen umgeht. Es gab einen ähnlichen vorfall vor gar nicht so langer zeit bei ub.com. Hier wurde der Fehler versucht runterzuspielen und es gab keine richtigen öffentlichen Statements. Cake allerdings schickt ihren besten Mann den ehemaligen Pokerroom Manager von Pokerstar Lee “fucking” Jones, der die Community nonstop über die fortschritte und das vorgehen bei 2+2 auf dem laufenden hält.

Hier klicken und miit 33% Rakeback bei Cake Poker spielen

Update : Der Fehler in der Software ist mittlerweile gefunden hier die Erklärung wie es zu dem falschen Sieger kommen konnte.

Hi all -
Well, our software wonks, after a sleepless night, got the answer.

During the hand in question, there was a player who had missed the blinds and been asked to post a dead blind in the cutoff. He didn’t, but somehow there was a perfectly timed lag between the client and the server that caused him to have a “Fold” button presented (though he may or may not have seen it). Probably unknowingly, he clicked a non-existent “Fold” button, which went through to the server. The server has code built in to protect it from extraneous messages such as this (including malicious intent from hacked clients). But it turned out that it didn’t have that protection from a dead blind-posting player if the message was something that shouldn’t have been coming in anyway (e.g. a “Fold” from somebody who shouldn’t be allowed to fold in the first place).

The result of all this was for the system to believe that it had a side-pot between the sitting-out player and the small blind (the guy with the kings). It evaluated that pot, awarded that pot to the small blind, and then had no more pots to award, so it ended the hand.

We’ve fixed the code and are testing it. There’s a pretty good chance we could have gone another four years before we saw this again, but obviously we’re not going to wait and find out. The $500 offer I mentioned above stands; we think we’ve got this one beaten.

As regards the people who were involved in the meteor-strike pot, we’re going to treat it like a bad beat jackpot. We’re going to ship $500 to the guy who had the ace of trump and should have won the pot in the first place, $250 to the OP in this thread for reporting it, and spread $250 around the other players who were dealt in, including the mystery player who wasn’t dealt in but managed to fold anyway. Were it not for him, we’d have never found and removed this bug.

Thank you all for your understanding and patience with us; we appreciate that beyond words.

Best regards,
Lee Jones

Cake Poker Cardroom Manager