Kalshi Perps over DoubleZero

How much sooner you get the data

Two ways to get the same Kalshi trade to your server, side by side: the DoubleZero edge feed vs Kalshi’s own public API — the perpetuals WebSocket (external-api-margin-ws.kalshi.com) that anyone can connect to directly. Both are received on one machine and timed on one clock, and each trade is matched across the two by exchange timestamp, price and size — so there is no cross-machine clock skew. Below: how often, and by how much, the DoubleZero copy of a trade arrives first.

—

arrives first

of trades reach you first over DoubleZero

Typical lead over the public feed

Median— ms

matched — trades · rolling window

Live, rolling window — one host, one monotonic clock, no cross-machine skew.

How long DoubleZero actually takes

The panel above says how much sooner DoubleZero is. This one says how long the trip takes. Every Kalshi trade carries the exchange’s own execution timestamp, so the clock starts at the venue rather than at our door.

One server in Europe, listening at DoubleZero’s Frankfurt edge. Kalshi sits in AWS us-east-2, an ocean away — 106 ms round trip from here, against 2.9 ms to the DoubleZero edge.

Measuring… the first matched trades are still coming in.

The feed, live right now

Every Kalshi crypto perpetual — full top-of-book & trades — streaming over the DoubleZero edge network and decoded here in real time. Live throughput below.

Perp	Bid	Ask	Last trade	Trades
connecting to the feed…

What it is

Coverage

All Kalshi crypto perpetuals — BTC, ETH, SOL, XRP, and more.

Data

Top-of-book (best bid/ask) plus every executed trade.

Transport

Binary multicast over the DoubleZero edge network.

Decoding

Fixed-size wire format, decoded deterministically to normalized events.

Benchmark baseline

Kalshi’s own public perps WebSocket (external-api-margin-ws.kalshi.com) — the same data, the standard public way to get it.

Method

One host, one monotonic clock; trades matched by exchange timestamp + price + size.