The live hand when you disconnect
Live-dealer hands are the most sensitive to an interruption, because a human is dealing to a table and the other players are in the same round. This page is about what a disconnect does to a live hand - not to the stream, which is a separate subject, but to the hand itself: whether the bet stands, whether the stake returns, and when the table voids.
- live hands sampled
- 4,800
- met a disconnect
- 13.5%
- bet stood into the hand
- 59.3%
- stake returned
- 25.9%
- hand voided for the table
- 14.8%
- runtime javascript
- none
The stake is committed and the round is running. A break here, before the round is decided, is the only break that can void the stake - and only if the rules have no default action.
The decision window is open. A dropped connection or a timed-out decision is decided here: by a default action, by a void, or by the window expiring.
The outcome is fixed on the server. A break now is a display problem only: the round settles as decided and the result is shown on reconnect.
The round is voided and the stake returns to the balance. This is a rule outcome, not a loss: the money is where it started.
In a live dealer hand a disconnect is a decision about a round that other players share. Of the 648 sampled live hands that met a disconnect, the bet stood into the hand on 59.3%, the stake was returned on 25.9% and the hand was voided for the whole table on 14.8%.
Why a live hand is the sensitive case
Everything else the desk describes happens to one player in one round. A live hand is a shared round: a dealer, a physical table and a set of players whose decisions sit inside the same timeline. When one player drops, the table cannot wait indefinitely, and the rules have to choose between three unattractive options - keep the bet live for a player who cannot act, return their stake and play on, or void the hand for everyone.
That is why the live hand splits differently from the rest of the desk. The 4,800 sampled live hands met a disconnect on 648 of them (13.5%), and the resolution was spread across all three options rather than resolving almost entirely to a settlement.
The three resolutions, and where each fits
| Resolution | When it applies | Hands | Share |
|---|---|---|---|
| the bet stands | the hand has already reached the point at which all decisions are made | 384 | 59.3% |
| the stake is returned | the disconnect happens before the player action would be needed | 168 | 25.9% |
| the hand is voided | the table cannot continue cleanly with a player absent | 96 | 14.8% |
The rows are ordered by how late the disconnect lands, exactly as in the rest of the desk: a late break leaves a decided hand that stands, an early break allows the stake back, and a break at the wrong moment for the table voids the hand for everyone.
The arithmetic of a shared void
Worked example / sample G
- live hands sampled: 4,800
- met a disconnect: 648 (13.5%)
- bet stood into the hand: 384 (59.3%)
- stake returned to one player: 168 (25.9%)
- hand voided for the table: 96 (14.8%)
- players whose stake is affected by one void: the whole table
That is the honest difference between a live hand and a spin. The spin is yours; the hand is shared, and its void rules are written to protect the table rather than the individual.
What to check before a live hand on a weak connection
- The disconnect policy for the format: whether the bet stands, returns, or voids the hand.
- The decision timer: a live hand usually carries one, and the default action on a timeout.
- Whether the void is for the player or for the table; the terms state which.
- Whether the hand is sequential (decisions matter) or settled on cards only (the bet stands).
- The reconnect window: how long the client has to return before the hand is resolved without it.
None of this is a reason to avoid live formats. It is a reason to know the rules before playing a shared hand on a connection that has already dropped once.