Benchmarking.

Benchmark: our consensus vs. an odds API provider

Benchmark results / updated 6 November 2026

After a score, our consensus repriced 1.5 to 3.4 seconds before the fastest venue price arrived through the odds provider we benchmarked against, depending on the league.

We subscribed to the enterprise tier of an odds provider, and benchmarked our stream against their stream side by side, as a customer receives them, on one clock-synchronized machine. For each scoring play we took the time each feed needed to move halfway to its new price, then compared the feeds on the same play. That difference does not depend on the accuracy of the play's timestamp.

Repricing after scoring plays

Median lead of our consensus over the first venue to reprice on each play, as delivered by the odds provider:

Venue by venue

We compared our consensus with three venues, shown here as Venue 1 to 3. Median lead over each venue's price, as delivered by the provider:

Which plays count

Isolated scoring plays only, with no other score within 20 seconds, starting between 5 and 95 cents, where a provider feed moved at least 3 cents. Periods around a reconnection of either feed are excluded.

How to read it

These are price arrivals through one provider, not the venues' own order books, and we make no claim to be ahead of order books or sportsbooks. Our recorder sits in the same region as our servers, and the provider's location is unknown. Network distance shifts the gap for a customer elsewhere, in either direction, typically by under 0.25 s even on another continent. That is small next to the leads above. Play timestamps come from public play-by-play data, to the second, matched after the game. The recordings run from 30 October to 6 November 2026 and span an update of our consensus on 1 November. We update these numbers as more games are recorded.