New: the Free plan. Check FirstLight's timing against your own feed

Robinhood Chain feed latency

FirstLight's lead per block over a typical provider and, until 2026-10-29, over the fastest private provider. One host receives every feed and one clock stamps every arrival. The record below shows the figures of every day.

The last hour, live

The lead of each block is the comparator's arrival minus FirstLight's arrival. A positive lead means that FirstLight delivered the block first. The figures cover the last hour of blocks.

ComparatorBlocks comparedFirstLight firstMedianMeanp90p99p99.9Max
A typical provider35,038100.00 %+47.6 ms+52.1 ms+63.4 ms+141.5 ms+363.5 ms+633.4 ms

A comparator with fewer than 20 compared blocks in the hour shows "measuring", not a figure.

The continuous record

What the record holds

The service records the lead of every block over the typical provider, and over the fastest private provider until its feed ended on 2026-10-29, on one host with one clock. It finalises each UTC day 10 minutes after the day ends. The tables below show the figures of each day. Coverage is the share of the day's sequence numbers that the record holds, from the first to the last recorded block.

The record starts on 2026-10-26. It holds 6,446,599 blocks: 8 finalised days and the days not yet finalised. Quantiles are per day; they cannot be combined across days.

Since 2026-10-26

ComparatorComparedFirstLight firstMeanMaxMissedDisagreed
The fastest private provider2,678,04699.98 %+2.7 ms+878.7 ms5520
A typical provider6,444,91099.97 %+50.5 ms+1.72 s1,6890

Today so far (UTC)

2026-11-03: 335,879 blocks, coverage 100.00 %.

ComparatorComparedFirstLight firstMeanMedianp90p99p99.9MaxMissedDisagreed
A typical provider335,87999.99 %+50.1 ms+46.7 ms+61.2 ms+104.0 ms+314.0 ms+633.4 ms00

The last 30 days

The fastest private provider

Day (UTC)ComparedFirstLight firstMeanMedianp90p99p99.9MaxMissedDisagreedCoverage
2026-10-29650,65499.98 %+2.4 ms+2.0 ms+4.1 ms+9.7 ms+15.8 ms+878.7 ms10099.99 %
2026-10-28831,52399.99 %+2.8 ms+2.5 ms+4.2 ms+9.5 ms+18.0 ms+824.6 ms53099.98 %
2026-10-27826,99099.97 %+2.8 ms+2.7 ms+3.9 ms+6.0 ms+16.6 ms+537.0 ms489099.99 %
2026-10-26368,87999.96 %+2.9 ms+2.9 ms+3.7 ms+4.6 ms+10.8 ms+30.3 ms00100.00 %

A typical provider

Day (UTC)ComparedFirstLight firstMeanMedianp90p99p99.9MaxMissedDisagreedCoverage
2026-11-02836,30199.99 %+51.4 ms+47.4 ms+63.1 ms+113.9 ms+396.7 ms+1.72 s892099.67 %
2026-11-01830,28799.99 %+48.6 ms+45.7 ms+59.1 ms+92.8 ms+276.1 ms+1.57 s0099.99 %
2026-10-31823,27899.98 %+48.0 ms+45.0 ms+58.2 ms+93.5 ms+271.6 ms+494.2 ms0099.99 %
2026-10-30765,84999.95 %+50.1 ms+45.8 ms+62.5 ms+135.0 ms+414.7 ms+1.03 s605093.57 %
2026-10-29825,22899.97 %+51.0 ms+45.2 ms+64.2 ms+155.6 ms+496.5 ms+1.14 s78099.99 %
2026-10-28831,49799.98 %+50.2 ms+44.9 ms+62.1 ms+149.3 ms+451.6 ms+1.66 s79099.98 %
2026-10-27827,46499.96 %+52.9 ms+48.5 ms+64.6 ms+140.1 ms+410.8 ms+816.4 ms15099.99 %
2026-10-26368,85999.98 %+54.4 ms+49.5 ms+66.0 ms+138.1 ms+494.5 ms+1.15 s200100.00 %

The method in short

The full method is in the docs, under How Robinhood Chain feed latency is measured.

Questions

Who are the two comparators?

The fastest private provider is the fastest private sequencer stream that we measured, until its feed ended on 2026-10-29. A typical provider is a node provider's newHeads subscription, which comes after the block has executed.

Why are some blocks missed or disagreed?

A block is missed when the comparator did not deliver it within 30 seconds. A block is disagreed when the two block hashes differ. Neither kind of block has a lead, and the record counts both.

Can I measure the lead myself?

Yes. Ask for a free key, connect to the /headers stream and to your feed from one host, and subtract the two stamps of each block. The steps are in the measurement docs.