Claim
Bonus
Check
Risk
Back to guides
Player Protection Guide

System failure? Save the round, balance, and timestamp first

Did a platform crash, disconnect, or show a balance error during play? This guide helps you separate local connection issues from platform-side faults and save the records needed for a reviewable complaint.

13 min readReview scope: player-risk guidance
1
Stop the session

Do not keep playing until the round ID, timestamp, and balance state are saved.

2
Capture measurable impact

Record the bet, payout, balance before/after, error message, and support acknowledgement.

3
Check whether it is platform-side

Local connection drops without logs or screenshots are usually weak claims.

Open claim workspaceCheck evidence standard

Required before review

  • Round ID or transaction ID
  • Timestamp and error message
  • Balance before and after
  • Support reply or platform incident note
Stronger if available
  • Screen recording
  • Game provider round detail
  • Platform status announcement
  • Other player reports with matching time
Usually not enough
  • Only remembering a lost win
  • No round ID
  • No balance record
  • Only a local network drop without platform evidence

Next evidence paths for system failures

Use these paths when a platform-side fault appears to affect a balance, bet result, or payout.

Compare system casesReview crash, disconnection, malfunction, and balance-sync patterns.Check settlement overlapUse this when the failure changed a calculable bet or game payout.
More related paths
Evidence standardLocal connection drops without logs, IDs, or screenshots are usually weak.Check risk warningsRepeated unexplained failures should be compared with blacklist signals.Open review centerCheck whether the platform has a guaranteed or reference-only review path.
01

Types of Casino System Failures

Not all system failures are equal in terms of player impact or casino liability. Understanding the type of failure you experienced is the first step toward a successful claim. GOOD CASINO's audit team has categorised platform incidents into the following distinct types, based on frequency and financial impact:

Mid-Game Disconnection with Incomplete Round

The most common type. You are mid-spin on a slot, mid-hand in a live dealer game, or mid-round in a crash game when the platform goes offline — and the round never completes. Reputable platforms use server-side round completion, meaning the outcome is determined server-side and credited correctly when you return. If your balance is lower after reconnecting and no game result is recorded, this is a documentable failure.

Account Balance Discrepancy Post-Outage

You experience a platform outage, log back in after it resolves, and your balance is materially lower than it was before the disconnection. This can occur when a transaction is partially processed — a bet deducted but a win not credited — due to a race condition at the moment of disconnection. This type is directly covered by GOOD CASINO's guarantee at partner casinos.

Duplicate Transaction / Double Deduction

A deposit or bet triggers twice due to a payment processor timeout or network retry loop. You see two identical debit entries in your transaction history. The casino may acknowledge this but leave the correction pending for days or weeks.

02

Red Flags: When 'Technical Issues' Are Actually Negligence

Casinos often use the phrase 'technical issues' as a blanket deflection. These are the documented patterns that separate a genuine one-off failure from a systemic operational problem — or deliberate denial of liability:

No Official Incident Announcement

A genuine platform-wide outage is almost always announced on the casino's official social media, status page, or via email. If no outage was ever acknowledged, the casino may be disputing that the failure occurred at all — making your own timestamped evidence essential.

Support Claims No Record of the Incident

You report a balance discrepancy and support says 'our systems show no interruption during that period.' Reputable platforms maintain server logs of all round outcomes and can verify discrepancies internally — the claim that 'no record exists' is almost never technically accurate.

Selective Recovery for Some Players

Other players on public forums report a correction for the same outage, while your similar claim is denied. This suggests the incident may have been acknowledged internally but handled inconsistently.

03

What to Do Immediately After a System Failure

The first 15 minutes after a system failure are the most important for building your case. Every action you take — or delay — in this window affects how credible your claim will be.

1. Do Not Refresh or Close the Browser

Leave the browser window open. Some platforms display an error state that includes a session ID or round reference number in the URL or page source. Refreshing may clear this. Take a full screenshot of exactly what you see before doing anything else.

2. Screenshot Your Balance Before and After

Navigate to your wallet or account balance page immediately after reconnecting. Screenshot both the current balance and your full transaction history. If there is a discrepancy, this is your primary evidence.

3. Check the Casino's Status Page or Social Media

Many platforms publish real-time status updates at status.[casino].com or their official Telegram. Screenshot any incident report or outage acknowledgement immediately — these posts are sometimes deleted once the issue resolves.

4. Note the Exact Time and Game Details

Record the exact time the failure occurred, the game you were playing, the bet size, and the expected outcome if known. This timestamp will be cross-referenced against server logs if your case is escalated.

04

Building Your Evidence File

A system failure claim without documented evidence rarely succeeds. Casinos have access to their own server logs; you need independently verifiable evidence that supports your account of events. Here is what carries the most weight:

Step 1

Screenshot of your balance immediately before the failure (if available from a previous session or cached browser page)

Step 2

Screenshot of your balance immediately after reconnecting — timestamped

Step 3

Screenshot or recording of the game state at the moment of disconnection

Step 4

Screenshot of the transaction history showing any anomalous deductions

05

How GOOD CASINO Reviews Evidence

GOOD CASINO reviews platform-side failure claims by checking whether the player record, platform reply, and measurable balance or payout impact line up. Guaranteed-platform cases are assessed under the applicable guarantee rules.

Eligibility 1

The casino must be on the GOOD CASINO guaranteed partners list

Eligibility 2

The balance discrepancy must be at least $10 USD equivalent

Process 1

Email help@good.casino with subject: 'System Failure Claim – [Casino Name] – [Date of Incident]'

Process 2

Attach all evidence: balance screenshots, support chat transcript, incident timestamp

07

How to Prepare a System-Failure Complaint

Players searching for a casino disconnect, server crash, or missing balance need a clear file first. Use this order before escalating:

Step 1

Step 1: Save the round ID, timestamp, balance before and after, error message, and support reply

Step 2

Step 2: Check whether the issue overlaps with a calculable settlement error or missing transaction

Step 3

Step 3: If the platform is guaranteed, prepare the file for GOOD CASINO review

Step 4

Step 4: If the platform is not guaranteed, compare blacklist signals and similar case records before taking further action

08

Prevention: Minimising Your Risk Exposure

You cannot remove every technical risk, but you can reduce exposure by choosing platforms with clearer records and by keeping your own transaction trail. GOOD CASINO considers technical reliability as part of platform review.

Choose Casinos with Published Uptime Commitments

Top-tier platforms publish their uptime history or explicitly commit to service level standards. Any casino that makes no mention of technical reliability in its player protection documentation should be treated with additional caution.

Use Provably Fair Games Where Possible

Provably fair games generate outcomes using cryptographic hashes that can be verified by the player after each round. This makes balance discrepancies from technical failures objectively verifiable — the hash proves what the outcome was, independent of the casino's server logs.

Play in Shorter Sessions and Withdraw Frequently

The longer and larger your balance sitting on a platform, the greater your exposure to any single technical incident. Withdrawing winnings regularly — rather than letting large balances accumulate — is the single most effective risk management behaviour for active players.

Lost Balance Due to a Platform Failure?

If the casino is on our partner list and support has not explained the issue, prepare the records for GOOD CASINO review.

File a ClaimView guaranteed casino list
Evidence and claim path

Use this when the dispute depends on proof quality

Evidence-led cases need a clear timeline, platform records, player-side screenshots, and a specific claim amount. Weak or incomplete proof usually leads to rejection.

Player task: build a clean evidence file before asking GOOD CASINO or a platform to act.

Evidence to save first

  • Timeline with exact dates, amounts, bet IDs, order IDs, and affected balances
  • Screenshots or exported records from the platform, not rewritten summaries
  • Support messages that confirm the platform's explanation or refusal

Recommended next checks

Study evidence casesSee what strong and weak case files look like.Check platform riskMatch your evidence against platform status.Submit evidenceSend a structured file when facts are complete.Open resource centerChoose more safety tools and guides.
Guide to evidence file

Turn the guide into an evidence package

After reading the guide, collect the required records before asking GOOD CASINO to intervene.

Required evidence

  • Platform name, account ID, and registered email or phone
  • Transaction, withdrawal, deposit, bet slip, or order ID
  • Amount, currency, payment network, and exact submission time
  • Screenshots of account status, cashier status, and platform response

Helpful supporting records

  • Full support chat or email thread, not cropped single messages
  • KYC approval or rejection notice if identity review is involved

Review flow

24h acknowledgement

GOOD CASINO checks whether the file is complete enough to review.

48h platform inquiry

For eligible cases, the platform is asked to confirm records or resolve the issue.

Evidence outcome

Cases are marked paid, resolved, rejected, or pending evidence based on records.

Usually not accepted
  • Memory-only claims without records
  • Edited screenshots or screenshots with hidden order details
  • Claims involving forged identity, exploit abuse, or account sharing
help@good.casino@goodcasino_help
Email evidenceView case standards
Generate email template

Generate an email template

Fill the key fields, then open a prefilled email. Attach screenshots and exported records in your mail client before sending.

Evidence completeness

0 of 6

Not enough yet

Missing required fields. Submit after filling the key records so the claim can be reviewed.

Required before review
  • Add the platform name exactly as shown on the site.
  • Add account ID, registered email, phone, or username.
  • Add withdrawal ID, deposit order, bet slip ID, case ID, or ticket number.
  • Add the disputed amount and currency, such as 1200 USDT.
  • Add key dates: request time, support reply, and current status.
Recommended to strengthen the file
  • List screenshots, support chat, wallet hash, KYC notice, or exported records.

Complete the required evidence first

The draft is useful, but key records are still missing. Fill the required fields before sending it for review.

View evidence guide

This tool only creates text in your browser. GOOD CASINO receives information only after you send the email yourself.

Email preview
GOOD CASINO evidence review - Settlement or balance error - Not provided
Issue type: Settlement or balance error
Platform name: Not provided
Account ID / registered contact: Not provided
Transaction / order / bet ID: Not provided
Amount and currency: Not provided
Timeline: Not provided
Evidence attached: Not provided

Apply this guide

Primary actionCheck platform riskSearch safety signals before depositing.
Evidence pathView real casesCompare outcomes, evidence, and payouts.
Evidence pathFix withdrawal issuesUse the checklist for delayed or rejected payouts.
Evidence pathSubmit evidenceSend records before escalating a dispute.