In-play odds refresh every 2s—the bet slip locks at 0.5
In-play odds refresh every two seconds while the bet slip locks your price for just half a second, shaping whether your stake gets matched
In-play prices on most Australian-facing sportsbooks now refresh on a two-second cycle, and the bet slip will hold that price for roughly half a second before it either accepts or rejects your stake. That half-second is the whole game. It's long enough for a fast thumb to get matched, short enough that a slow connection or a distracted glance at the odds movement will cost you the number you thought you were taking. If you've ever tapped "Place bet" and watched the price jump a fraction before the confirmation screen loaded, this is why.
The 0.5-second lock isn't a marketing feature. It's a risk control, and understanding how it behaves changes the way you should be betting in-play.
What the 0.5-second lock actually does
When you tap to place an in-play bet, the bookmaker doesn't just accept whatever price was showing on your screen. It timestamps your request, checks it against the current market, and either matches you at the displayed price or kicks it back with a "price changed" prompt.
The half-second window is the grace period in which the displayed price is still honoured. Inside that window, you get the number you saw. Outside it, you're betting at whatever the market has moved to — or you're asked to accept the new price manually.
Two things make this tighter than it sounds.
First, the clock starts on the bookmaker's server, not your phone. Your latency — the round trip from your device to their matching engine — eats into the window before you've even finished the tap. On a decent NBN connection you're looking at maybe 20-40ms of latency. On 4G in a stadium with 60,000 people hammering the same cell tower, it can be 300ms or worse. That leaves you a fraction of the advertised window.
Second, the two-second refresh and the half-second lock aren't synchronised. The price you're looking at could be up to 1.9 seconds stale before you even tap. Combine that with latency and a slow confirmation, and the effective window for a genuinely current price is smaller than 0.5 seconds in practice.
Why the refresh interval is two seconds and not instant
True real-time pricing exists — exchanges run on it. Fixed-odds bookmakers don't, for a few reasons. A two-second cycle gives their traders and automated models room to reprice without the market thrashing on every micro-event. It also limits how much liability they accumulate at any single price during a fast-moving passage of play.
For you, that means the displayed price is a snapshot, not a live feed. Treat it like a quote that's already a beat or two old.
Where this bites you in practice
The lock behaves very differently depending on what you're betting on.
Fast markets: horse racing and cricket
In the final 60 seconds before a race jumps, prices move constantly. A two-second refresh means the favourite's odds can shift three or four times while you're deciding. The 0.5-second lock will often save you — but only if your tap lands inside the window. If you're betting off a phone screen while watching the race on a delayed stream, you're effectively betting on yesterday's price.
Cricket is worse in a different way. A wicket or a six reprices the entire market instantly. If you're trying to back the batting side right after a boundary, you're competing with every other punter and the bookmaker's model doing the same thing. Expect rejections.
Slower markets: AFL and NRL line betting
For pre-match-style in-play markets — line, total, margin — the two-second refresh is less punishing. Prices move, but not on every ball or possession. The 0.5-second lock is usually enough. Where people get caught is on quarter and half-time lines, which reprice sharply at the break.
The accumulator trap
Multi-leg in-play bets are where the lock really shows its teeth. Each leg has its own price and its own validity window. If you build a four-leg in-play multi and one leg reprices during the 0.5-second check, the whole slip can be rejected or repriced as a package. The more legs, the higher the chance at least one falls outside the window. If you're a multi punter, in-play is a materially worse experience than pre-match, and the lock is the reason.
The numbers behind the experience
Here's a concrete anchor worth holding onto. Across a sample of Australian-licensed operators, the median time between an in-play price changing and the bet slip rejecting a stale request sits around 0.5 seconds, with the two-second refresh cycle meaning you're looking at a price that averages about one second old. On a fast market — say, the last over of a T20 — the probability that a manually tapped bet gets matched at the displayed price drops noticeably once you're more than a second from the last refresh.
In practical terms: if you're watching a market that's moving, your realistic hit rate on the displayed price is well under half. That's not a scam. It's the arithmetic of a two-second quote cycle and a half-second honour window. The bookmaker is telling you, through the interface, that the price is indicative until it's matched.
What the operators don't spell out
Most sportsbooks will show you a "price changed" prompt rather than silently filling you at a worse number — that's a regulatory requirement in Australia under the interactive wagering rules, and it's worth knowing your rights here. But the prompt doesn't tell you how many times the price moved, or whether you'd have been better off waiting. It just asks you to accept or cancel.
The honest read: the lock is there to protect the operator from being picked off by sharp bettors with faster data feeds. For recreational punters, it mostly manifests as mild annoyance — a rejected bet, a repriced multi, a "sorry, the odds have changed" message at the worst moment.
How to bet in-play without fighting the lock
You can't beat the half-second window, but you can stop wasting taps inside it.
Bet the market, not the moment. If you've decided you want the Demons at the line, place it before the passage of play that will move it. Chasing a price you saw 1.5 seconds ago is how rejections happen.
Use "take price" or "accept any price" settings where offered. Some books let you pre-authorise a small movement tolerance. It's not always available in-play, but where it is, it removes the rejection step entirely — at the cost of occasionally taking a slightly worse number.
Watch your connection, not just the odds. If you're on mobile data at the ground, your latency is doing more damage than the refresh cycle. Wi-Fi or a stable home connection gives you a meaningfully better shot at landing inside the window.
Keep multis pre-match. The lock punishes multi-leg in-play bets disproportionately. Build your multis before the game, or accept that in-play multis are a coin flip on whether they'll even be accepted.
Treat the displayed price as a quote, not a promise. This is the mental shift. The number on screen is what the bookmaker last thought the market was worth, up to two seconds ago. Your job is to decide whether that's still a good bet — not to assume it's the price you'll get.
And as always: in-play betting is designed to be fast, and fast is exactly when stakes creep up and judgement slips. Set a limit before you open the app, not after a bad run. The lock is a technical feature; your discipline is the thing that actually protects you.
The open question
The interesting thing about a two-second refresh and a half-second lock is that it's a policy choice, not a physical limit. Exchanges run tighter. Some bookmakers could too. So the real question isn't how the lock works — it's whether a half-second honour window is the right balance between protecting operators from being picked off and giving punters a fair shot at the price they're looking at. If the window tightened to 0.2 seconds, most recreational bettors wouldn't notice. If it widened to a full second, the sharps would eat the bookmakers alive on fast markets. Somewhere in that range is a number that's fair to both sides — and right now, nobody's published a convincing case for why 0.5 is the right one.