> ## Documentation Index
> Fetch the complete documentation index at: https://docs.radion.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Limitations

> What the Radion WebSocket streams do and do not guarantee.

## Public onchain data only

Radion streams decoded onchain events and public mempool transactions. There are no account-only order or fill streams. Radion cannot see private orderbooks or your account state. To track your own confirmed fills, subscribe to the [`trading`](/websockets/channels/trading) and [`wallets`](/websockets/channels/overview) channels, filtered to your addresses.

## Mempool is speculative

Pending transactions on the [pending feed](/websockets/mempool) — any channel you subscribe to with `confirmed: false` — can be dropped, replaced, reordered, or reverted before they confirm. Treat them as hints, not facts, and check them against the confirmed feed by transaction hash. Mempool filters can only match fields that show up as calldata arguments — see [Filter reach](/websockets/mempool#filter-reach).

## Backpressure

Radion keeps a fixed window of recent events for each stream. If your client reads slower than events arrive and falls behind that window, the oldest events are dropped and you get a [`lagged` error frame](/websockets/frames#error-frames) with a `skipped` count. The connection stays open, but the gap is not sent again.

To recover, reconnect and resubscribe. To avoid lag, read fast, narrow your subscriptions with [filters](/websockets/filters), and do not block the socket read loop with heavy work for each message.

## No event replay

Streams are live only. There is no backfill and no historical replay over the WebSocket. You get events from the moment you subscribe. For historical data, use the [REST API](/api/overview).