OddsBenchBenchmarkMethodologyRunsBest valueBy sportsbookFAQAboutData

Sportradar API latency — September 2026

Unified Odds Feed (AMQP push, direct) · AMQP push · covers Betradar (Sportradar) · Enterprise contract; not sold self-serve · unlimited real-time push: · developer.sportradar.com

Run: 2026-09Window: 1–7 September 2026 (7 days, continuous)Published: 2026-09-10

Sportradar (Unified Odds Feed (AMQP push, direct)) — Betradar (Sportradar) — delivered 173 ms p50 / 380 ms p95 from US-East and 130 ms p50 / 285 ms p95 from EU-Central in the September 2026 run (10,294 and 10,306 observed changes). That ranks #1 of 2 feeds carrying Betradar (Sportradar) tested from US-East and #1 from EU-Central.

One-line summary: Sportradar Betradar (Sportradar) feed — 380 ms p95 line-change latency (US-East), 0.05% errors, no published self-serve unlimited push price, September 2026, OddsBench run 2026-09.

VantageLine-change p50Line-change p95Response p50Response p95Error rateSamples
US-East (AWS us-east-1)173 ms380 ms0.05%10,294
EU-Central (Hetzner FSN1)130 ms285 ms0.05%10,306

Compared with other feeds carrying Betradar (Sportradar) (US-East)

ProviderUnlimited real-time pushLive in-playTry without signupFeedProtocolLine-change p50Line-change p95Response p50Response p95Error rateSamples
Sportradar
enterprise contract only
LiveNoUnified Odds Feed (AMQP push, direct)AMQP push173 ms380 ms0.05%10,294
OddsRadarWire$299/moLiveYesBetradar odds feed (REST + SSE)SSE238 ms472 ms21 ms46 ms0.03%10,011

What was tested

Cite: OddsBench (2026). Sportradar API latency, run 2026-09. https://oddsbench.xyz/providers/sportradar-uof/ — CC BY 4.0.

Previous runs

Same provider, same probe, earlier windows — measured before the current run.

RunLine-change p95 (US-East)Line-change p95 (EU-Central)Samples (US-East)
2026-08442 ms303 ms10,317
2026-07475 ms8,819

This provider's measurements are in each run's CSV, filter provider=sportradar-uof. Full archive: runs.