Past-Posting in Live Betting: Why Sportsbooks Keep Taking Bets After a Goal
After a goal, this sportsbook keeps taking bets at the pre-goal price for seven seconds. The trading team suspended the market right away, but the suspension went out the way prices do, on the odds pipeline, queued behind the repricing of every other market on the match. Bots watching a feed faster than the broadcast bet Harbor City at +240, and bet acceptance checks a cache that still says open. By the time the suspension lands, the book has taken 326 bets and liability is $1.4M against a $300K limit. Then the same goal with the trading team writing the suspension as a hold that bet acceptance reads directly, so the bots' bets are turned away and every accepted bet is written back before the next one arrives.
Overview
A Decision Replay of in-play betting, on camera with Alex Kimball: why a correct suspend rule still let 326 bets through after a goal, and the same goal with current context.
Topics Covered
- •A live match, and how prices reach bet acceptance
- •The goal, and the rule to suspend every market
- •Bots betting on a feed faster than the broadcast
- •The odds pipeline at its busiest right after a goal
- •The same goal with the suspension written as a hold bet acceptance reads
Key Takeaways
- ✓The suspend rule was right; bet acceptance couldn't see it yet
- ✓A suspension that rides the price pipeline waits behind every repriced market
- ✓Seven seconds after a goal was enough for 326 bets and $1.4M of liability
- ✓When each accepted bet is written back, the next bet sees current liability
More Product Demos
Card Fraud: Six Purchases Approved on an Account Already on Hold
A 4-minute walkthrough of a fraud hold placed in time that reaches card authorization eight seconds late, and the same hold with current context.
Do You Actually Need a Separate Vector Database?
A 3-minute explainer on when a separate vector database earns its place, and what changes when similarity search has to agree with live filters and state.
Why ClickHouse JOINs Are Slow (and Why Denormalizing Isn't the Fix)
A 4-minute explainer on why ClickHouse JOINs are slow, what denormalizing costs, and what it looks like when joins stay first-class.
Ready to get started?
Book a demo to see how Tacnode can power your real-time data infrastructure.