Suspension, latency and the bet that did not go on
Betting in running feels instantaneous and is not. Between the moment something happens on the pitch and the moment a price updates, several systems have to agree: a data feed has to record the event, a pricing model has to react, and a market has to be closed and reopened at a new number. During that interval the market suspends, and any bet arriving in the interval is rejected. This is the single most misunderstood behaviour in live betting, and it is a design requirement rather than a fault.
What the delay is protecting
If markets stayed open through a goal, anyone watching a faster feed than the operator could back an outcome that had already happened. Suspension closes that window. Because different viewers receive different delays — a stadium spectator, a streaming subscriber and a terrestrial broadcast are not in sync — no operator can safely assume the customer knows less than it does. Suspension is therefore automatic and frequent, triggered by dangerous attacks and reviews as well as by goals.
What triggers a suspension
Goals, penalties, red cards, video reviews, injuries and often anything the feed classifies as a dangerous attack. Some suspensions last a second and are barely visible; others hold until an official decision is confirmed. During any of them the market accepts nothing.
Why your bet was rejected
Either the market suspended between your tap and the server receiving the request, or the price moved and your slip was configured to reject changes. Both are ordinary. Neither indicates that anything has been done to you personally, and both happen to every customer at every operator.
Your stream is behind
Video delivered over the internet typically lags the live event, and the size of that lag varies by provider and connection. Betting on what you can see is therefore betting on the recent past. This matters most in the seconds after a chance, which is exactly when people most want to bet.
Acceptance is the only thing that counts
A bet exists when the server has accepted it at a recorded price, not when you pressed the button. Any dispute about a live bet turns on the acceptance record, which is why screenshots of a price you saw are rarely persuasive on their own.
Questions readers send us
Can I disable price-change rejection?
Most platforms offer a setting to accept better prices, or any price change, automatically. Turning it on reduces rejections and removes your control over the number you get. Which trade you prefer is a genuine choice rather than an obvious one.
Is the delay the same everywhere?
No. It depends on the data provider, the platform and your own connection, and it varies between sports and even between competitions within a sport. Assuming a fixed delay is unsafe, which is another argument against betting live on the basis of what a screen has just shown you.
