New: real-time data over RF Binance USDT-M at our London endpoint, top of book over a microwave link — by the 24 h pass.New: real-time over RF

See it
Low-Latency Trading Solutions
Cart
Infrastructure & latency

How to Read a Microwave (RF) Top-of-Book Feed: Path Flag, RF Only and Gaps

How to read a microwave (RF) top-of-book feed: the path flag on each update, the RF-only subscribe option, why RF only is not gap-free and what an outage does.

7 min readPublished Nov 20, 2026
Message type
6 · top of book
Path element
true / false
Over RF
13 instruments
One pass
24 h

Our Binance market data over microwave (RF) endpoint delivers one market over two paths at once: top-of-book price changes of 13 instruments arrive over a microwave (RF) link from Tokyo, everything else over our fiber line — on one WebSocket, with one API key. This guide is for the person who writes the client: how to tell the two paths apart in the stream, what the RF-only subscribe option changes, why that option is not a gap-free top of book, what an interrupted link looks like from your side, and how the 24 h pass decides whether your key is let in.

One endpoint, two paths

The endpoint in London delivers the whole Binance USDT-M market like every other realtime endpoint — the same login, the same messages, the same API key. What differs is how the data gets there. The endpoint merges both paths: you see every update once, delivered by the path that brought it first, and never an older update after a newer one.

PathWhat it carriesOne-way line figure
Microwave (RF) linkTop-of-book price changes of the 13 listed instruments~66.0 ms
Our fiber lineEvery other top-of-book update and every other topic, for every instrument of the market~69.3 ms

Both figures: line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top.

The listed instruments are BTCUSDT, ETHUSDT, SOLUSDT, XRPUSDT, BNBUSDT, DOGEUSDT, ADAUSDT, NEARUSDT, HYPEUSDT, XMRUSDT, ZECUSDT, 1000PEPEUSDT, BTCUSDC. Only their price changes travel over the link. A change of the resting quantity at an unchanged best price arrives over fiber, and so does a price change whose fiber copy reached the endpoint first. An instrument on the list therefore receives both kinds of update, and the path is a property of each single update — never of an instrument.

The path element on every top-of-book message

Top of book is message type 6 on every realtime endpoint: the common header, then one row for the best bid and one for the best ask. At this endpoint the message carries one more element at its end: true when the update arrived over RF, false when it came over fiber. In SBE the same information is the field receivedViaRfUdp of the top-of-book event.

a top-of-book message with its path element
[6, 67824, …, [[0, "77979.1", "5.221", 1], [1, "77979.2", "1.481", 1]], true]
Parse by position

Parse the top-of-book message by position and ignore elements you do not know: the trailing path element is an addition to the message, and further elements may follow in later protocol versions.

Read the element per message and keep it next to the quote it came with. It tells you which path delivered that one update and says nothing about the next one.

Complete feed or RF only

There are two ways to receive the endpoint, and the choice is made in your subscribe request. The fiber part belongs to the pass: there is no fiber access to buy on top.

Complete feedRF only
How you ask for itSubscribe as on every endpoint — the default"topOfBookRfUdpOnly": true in the topic flags of the subscribe request
Top-of-book updates you receiveAll of them, each marked with its pathOnly those that arrived over RF
The other topicsOrder book, trades, mark and index price, funding and liquidations, over fiberLeft as they are — switch them off in the same request if you want nothing else
Top of book right after the subscribeSentSent, whatever its path
Who it is forA client that wants the whole market on one connectionFor clients that already receive this market from Tokyo over their own line.
complete feed · RF only, nothing else
[11, 67824]

[11, 67824, {"topOfBookTopic": true, "topOfBookRfUdpOnly": true,
             "depthTopic": false, "tradesTopic": false, "markPriceTopic": false,
             "indexPriceTopic": false, "fundingRateTopic": false}]

The option touches top of book alone. The second request above also switches off the topics that are on by default, so the connection carries nothing but the updates that arrived over RF.

Why RF only is not a gap-free top of book

It is not a gap-free top of book: a quantity-only change never travels over the link, and a price change whose fiber copy reached the endpoint first is not repeated. Both cases follow from how the endpoint works: the link carries price changes only, and the endpoint forwards every update once — from the path that brought it first. With the option set, the updates that fiber brought first are not sent to you.

What you can rely on: each message carries the whole top of book — the best bid and the best ask with their quantities — so the latest message stands on its own and no earlier one is needed to read it. What you cannot do is count on seeing every state the top of book went through, or read a quiet stream as an unchanged market.

Need every top-of-book state?

Take the complete feed — the default — and read the path element. The option is a filter on top of book; it is not a second, smaller copy of the market.

If you already receive Binance USDT-M over your own line

RF only exists for one kind of client: one that already receives this market from Tokyo over its own line and wants only what this endpoint adds. For that client the stream is one more source of top-of-book prices next to the feed it already has — never a replacement for it. The complete record of the market stays the feed you already run.

Two properties matter when you place it next to another feed. It is not gap-free (the section above), so nothing downstream may wait for it. And it goes quiet while the link is interrupted (the next section), so silence is a normal state of this stream, not a sign of a dead connection — the keep-alive tells you that.

If the RF link is interrupted, every update arrives over fiber and your pass keeps running. In the complete feed nothing stops: the same updates keep coming, and the path element reads false on the updates of the listed instruments until the link is back.

With RF only, no top-of-book updates arrive until the link is back. The connection itself stays up, and the topics you left switched on keep arriving. Reconnecting does not bring the updates back.

Access is a 24 h pass

Access is a pass, not a calendar day. A pass starts when your payment is confirmed and runs 24 hours for each pass you buy, plus 2 hours to get set up. Buying again while a pass is running adds the new time to its end — nothing overlaps. No subscription. Nothing renews.

A key without a running pass is refused at the handshake with the reason no active realtime pass for this market; when a pass ends, the endpoint closes the connection at its next periodic check, with the notice api key expired or revoked. Handle both as the normal end of access, not as an error to retry in a loop.

€399 per market and €299 per instrument per 24 h pass; from 14 passes €360 / €270, from 30 €320 / €240, from 180 €280 / €210, from 365 €240 / €180 (market / instrument). Single instruments are the 13 whose top of book travels over RF. The whole market includes the same 13 over RF and adds every other instrument over our fiber line. Passes are bought in the RF tab of the shop, paid by card or in USDC.

Implementation checklist

  1. Connect to ws://lon-rf.cryptostruct.com:14010/api/v6 with ?apiKey= appended — read the key from the environment variable CRYPTOSTRUCT_REALTIME_API_KEY, never from source code. It is the same key as on every realtime endpoint.
  2. Subscribe per instrument, or add "topOfBookRfUdpOnly": true to the topic flags for RF only.
  3. Parse message type 6 by position; read its last element as the path and ignore elements you do not know.
  4. Store the path with each quote. Never derive it from the instrument.
  5. With RF only: treat every message as a complete top of book, expect gaps, and expect silence while the link is interrupted.
  6. Treat the refusal no active realtime pass for this market and the close notice api key expired or revoked as the end of the pass.
  7. Everything else — the login, the other message types, keep-alive and reconnects — is in the connection guide; a coding agent reads the same guide as markdown.

Limitations

The two line figures are our measurements on the stated basis, quoted as approximate values — they are not an SLA, and what your process observes also depends on the path from your host to the endpoint and on your own stack. The link can be interrupted; the complete feed then continues over fiber. RF only is not a gap-free top of book. The list of instruments whose top of book travels over the link can change over time — the shop shows the current one. Market data only: there is no order entry on this product, and nothing here is investment advice.

Why CryptoStruct

Why buy the data in this guide here

Four things every page on this site is built on — and the reason the numbers above exist at all.

We record everything

The complete public feed of each venue as it was published: every Level-2 snapshot and update, every trade with its aggressor side, every quote, funding, mark-price and liquidation event — for every instrument the venue lists, every UTC day since we added the venue. Where a venue offers more than one order-book feed, we take the one with the lowest latency, at the depth that feed carries. Nothing sampled, no on-demand capture.

Institutional grade

Captured co-located at the venue with the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain that makes any gap visible, and one normalized schema across 35+ venues — the same capture our own high-frequency trading engine and enterprise feeds run on.

€1 per instrument-day

Any instrument-day is €1, series-day bundles start at €1 — no subscription, no minimum order, no tiers to unlock. Credit packs lower the effective price and never expire, and free full-day samples from the major venues let you test first.

Self-service for everyone

Pick the days in the Data Shop, pay by card or in USDC as a guest and download immediately — no sales call, no enterprise contract, no KYC. Coding agents buy the same files through the MCP server, and the free Agent Skill teaches them the format.

Agents: /llms.txt · MCP server /mcp · every page as markdown via Accept: text/markdown

FAQ

Frequently asked questions

How do I tell whether a top-of-book update arrived over RF?

Every top-of-book message (type 6) carries one more element at its end: true when the update arrived over RF, false when it came over fiber. In SBE it is the field receivedViaRfUdp of the top-of-book event.

What does the topOfBookRfUdpOnly subscribe option change?

The endpoint then sends only the top-of-book updates that arrived over RF — considerably fewer messages. The top of book sent right after the subscribe still comes, whatever its path, and the other topics stay as they are unless you switch them off in the same request.

Is the RF-only stream a complete top of book?

No. It is not a gap-free top of book: a quantity-only change never travels over the link, and a price change whose fiber copy reached the endpoint first is not repeated. Each message carries the whole top of book, so the latest one stands on its own.

How do I notice an interrupted link in the stream?

If the RF link is interrupted, every update arrives over fiber and your pass keeps running. In the complete feed the path element then reads false on the updates of the listed instruments. With RF only, no top-of-book updates arrive until the link is back.

Do I need fiber access on top of an RF pass?

No. The fiber part belongs to the pass: there is no fiber access to buy on top.

CryptoStruct Research Team · Market data & trading infrastructure

The team that records tick data co-located at 36+ venues and runs the low-latency trading stack behind it, as part of the SSW Group.