By Milena Petrovska · Fact-checked by Nikita Jones · Updated 30 July 2026Your screen goes dark mid-drop, your router drops, loadshedding has hit stage 2 again — and you're left staring at a dead phone wondering whether that bet is safe. Here's the honest, technical answer, plus how to protect yourself before the next stage hits.
Your bet is safe. Once you tap Bet, the round is processed and settled on the casino's server, not on your phone or router — that happens in a fraction of a second, before the ball animation even finishes playing out. Losing power or your connection a moment later doesn't cancel the round or change the result; it just means you missed watching it live. Reconnect and check your round history — the outcome will be sitting there, win or lose.
South Africans don't need loadshedding explained — Eskom's stage system is daily life, and it can hit at any moment regardless of what schedule an app promised you. The honest answer to "is my bet safe" depends entirely on when in the sequence the power actually cut, and it splits into two very different cases.
If the lights went out before you tapped Bet, nothing happened — no wager was sent to the server, no balance was touched. There's nothing to protect here, because there was never a live round to interrupt. When power's back, you just start again.
This is the case that actually worries people, and it's also the one where the mechanics work in your favour. The instant you tap Bet, the request goes to the casino's server, the stake is deducted, and the round is generated and recorded there — not on your device. The ball-drop animation you watch afterwards is just a visual replay of a result the server has already computed. A disconnect at that point doesn't roll anything back, doesn't change the multiplier your ball lands on, and doesn't touch your balance beyond what the round itself determined. This matches how casino platforms generally treat disconnections industry-wide: bets not yet locked in are voided, bets already accepted are settled exactly as if you'd stayed connected, and the result is always retrievable from your round history once you're back online.
The one thing loadshedding takes from you in that moment isn't your stake — it's the animation. You'll reconnect to a settled result, not a live drop you can still watch unfold.
Only crypto-native studios run true Provably Fair Plinko. Here the server seed is generated and cryptographically hashed before your drop even starts — the result is mathematically fixed the moment your bet is accepted, using that seed plus your client seed and the round's nonce. A power cut a second later changes nothing, because the outcome was never computed on your side to begin with. Once you're back online, you can open the casino's verifier and re-check the exact seed math for that specific round — not just trust that it settled correctly, but prove it.
Most Plinko titles — from providers without a Provably Fair engine — use an independently certified Random Number Generator instead. The result is still generated and stored server-side the instant your bet is accepted, so a disconnect still doesn't change the outcome. The difference is verification: you can't personally re-run the seed math for that one round the way you can on a Provably Fair title. You're trusting the lab certificate (eCOGRA, iTech Labs, GLI) behind the algorithm rather than checking a single spin yourself. Your round history still shows the result either way.
Once your data or Wi-Fi is back, don't just trust that it worked out — check. It takes under a minute.
Every operator has one, usually under Account, Transactions or Bet History. It shows the exact multiplier and whether your balance moved up or down for that round — regardless of whether the game was Provably Fair or RNG.
Confirm the stake deduction and any payout line up with what the round history says. If a bet you're certain you placed doesn't appear at all, that's worth a support ticket — not because the disconnect broke anything, but so there's a paper trail.
If you were playing BGaming, Spribe or Stake Originals, open the built-in fairness/verifier tool, grab the revealed server seed, your client seed and the round's nonce, and re-hash it yourself (or let the tool do it). A match proves nothing was altered — see our full Provably Fair guide for the worked example.
If you're about to place a large stake and you know a loadshedding stage is due, a quick screenshot of your balance beforehand gives you your own record to compare against — cheap insurance that costs nothing and takes two seconds.
None of this is about the casino letting you down — it's about not letting an Eskom stage catch you mid-session with a dead phone. A few habits make the whole thing painless.
Your home router almost always loses power the second loadshedding hits, unless it's sitting on a UPS or inverter. Your phone's mobile data usually keeps working through a stage, since the nearest cell tower typically runs on its own backup power (though not always for a full stage on the worst days). Switching to a data bundle before you play removes the one point of failure that's actually in your control.
Obvious, but it's the thing people forget until stage 4 hits at the worst time. A power bank in your bag means a stage cut doesn't also cost you the ability to check your round history afterwards.
Make it a habit, not a panic response — open your bet history any time you've been offline mid-session, win or lose. It takes seconds and removes any doubt.
If a loadshedding stage is scheduled and you're about to place a bet you'd want a record of, screenshot your balance first. It's not required — the server record is authoritative either way — but it's your own reference point if you ever want to double-check something later.
iGaming writer with 8 years across live casino, slots and crypto-casino coverage. Leads our crypto-Plinko, provably-fair and crypto-payments analysis.