Using OddStorm
Reporting wrong odds
Sometimes the odds at your bookmaker do not match what OddStorm shows. Usually the explanation is timing or a clone domain; occasionally it is a real scanning issue we want to know about immediately. This is the two-minute check and the exact report that gets it fixed fastest.
intro1
Before reporting: the two-minute check #
Three quick questions resolve most mismatches on the spot:
- Timing: is the leg's 'seen' timestamp fresh? Odds move; a price seen 40 seconds ago on a live match may simply have moved on. That is the market, not a bug.
- Domain: are you on the EXACT site we scan? Mirror and clone domains of the same brand can shift or lag odds. 'Only I see different odds' is the classic clone symptom.
- Market: same market, same period, same line? AH -0.75 at the book vs AH -1.0 in the app is a different market, not different odds.
The report that gets fixed fast #
Still mismatched? Send support these four things; together they let us reproduce the case in minutes:
- Whether it is InPlay or PreMatch.
- The FULL web address of the bookmaker you use (the exact domain, copied from the browser).
- A screenshot of the arb calculator with the Odd History visible (the seen/change timestamps are the evidence).
- A screenshot of the odd at your bookmaker, timestamped as close as possible to the first one.
What happens on our side #
We check the feed for that bookmaker and market at your timestamps. Clone-domain cases get an answer explaining which domain we scan; real discrepancies go straight to the parser team, and bookmakers with a genuine outage show as temporarily down on the Supported Bookmakers page until fixed. Either way you get an answer, not silence.
Where to go next #
The clones guide explains the domain trap in depth, and why-surebets-exist covers the odds-history discipline that separates moved prices from wrong ones.
Related questions
See live surebets with the stakes already calculated.
Try OddStorm free