OddStorm
↑↓ navigate Enter open Esc close

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.

4 min read Updated

View as Markdown Open in ChatGPT Open in Claude

A vague 'your odds are wrong' email starts a round of questions; a report with the right four details lets us reproduce the case from your first message. The difference is knowing what support looks at first, so here's the checklist we wish every mismatch report followed.

Before reporting: the two-minute check #

Three quick questions resolve most mismatches on the spot:

  • Timing: is the price's 'Seen' time in Outcomes 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? A clone (another brand on the same platform) can shift or lag odds; a mirror of a bookmaker we cover shows that bookmaker's 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. Write to us through the form on our Contact page, which takes text only, and attach the two screenshots when you reply to our email. Live Chat in the sidebar of the PreMatch and InPlay pages (on a phone, in the bar at the bottom), with an active subscription, takes short text messages that every subscriber reads: fine for flagging a mismatch, not for the report. The four things:

  • 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 Outcomes and the Odd History visible (the Seen and Change times in Outcomes 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 a bookmaker with a genuine outage shows as temporarily down on the Supported Bookmakers page and in the web app's Bookmakers panel until it's 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.

See live surebets with the stakes already calculated.

Try OddStorm free
Guides