Skip to content

Measurements

Block propagation

Every provider is subscribed at the same moment from one process. When each announces the same block or slot, the arrival is stamped by the same clock before any parsing. What is published is how far behind the earliest announcement each provider was, for that specific height.

No propagation race has settled in this window.

A race needs at least two providers subscribed to the same chain over the same transport at the same time.

What this does not measure

Each of these was tried and rejected on evidence, not on principle.

  • Absolute time from subscribing to a first notification. It is dominated by where in the block interval the subscription landed — up to a full block of noise, measured at 10.2 seconds of spread on Ethereum between trials whose subscribe round trip differed by 13ms.
  • Counts of which provider won most often. Two consecutive runs over the same providers scored 5-1 and then 7-0, because one block on which everyone stalled flips the headline. Lead share is shown alongside the distribution, never instead of it.
  • Comparisons across transports. WebSocket slotSubscribe fires when a node's bank forks a slot; Yellowstone SLOT_PROCESSED fires once that slot has been executed, a median 575ms later. They are different events, so they are ranked separately.
  • The first heights after a subscription opens. A node replays recent slots to a new subscriber, and that backlog drain is not a race: on Solana the median delta over the first 25 slots was 2,205ms against 72ms over the last 25 of the same session. Those rows are recorded and excluded from every figure here.

7d window · generated 2026-08-24 15:45:33 UTC · 0 cohorts