Realtime feed: Ohio endpoint joins London, Frankfurt and Ashburn

Self-serve realtime access now has 4 delivery endpoints: London, Frankfurt, Ashburn and Ohio. The new Ohio endpoint sits in AWS us-east-2, next to Kalshi.

Trading Kalshi? Connect in Ohio

Kalshi's trading API runs in AWS us-east-2 — the region of the new endpoint. A Kalshi strategy hosted there can now get Binance data at 65.0 ms latency, roughly 4 ms faster compared to Internet/AWS peering. That matters most for Kalshi’s crypto markets — the BTC and ETH up/down and price-range contracts move with the crypto price.

Endpoints

• London (LD4 / AWS London) — Binance (Tokyo) → London over dedicated fiber, ~70.4 ms one-way
• Frankfurt (AWS eu-central-1) — Binance (Tokyo) → Frankfurt over dedicated fiber, ~69.3 ms one-way
• Ashburn (AWS us-east-1) — Binance (Tokyo) → Ashburn over dedicated fiber, ~68.5 ms one-way
• Ohio (AWS us-east-2) — Binance (Tokyo) → Ohio over dedicated fiber, ~65.0 ms one-way

Every latency figure is one-way, end to end from the venue to your client — including Binance exchange latency and the AWS on-ramp behind the endpoint; measured against the Binance transaction timestamp "T".

Buy realtime access · Connection guide · Spec for coding agents