How fast do fills reach subscribers?Measured on every block we ingest and every push we send, not on a synthetic probe. Block time is the Polygon block timestamp; detected is when our listener had the block’s logs; pushed is when the message left our edge.
Block → push · median—p95 — · n=0 pushes · 0 failed
Block → detected—p95 — · header seen p50 — · newHeads + getLogs(blockHash)
Detected → pushed—median difference · decode, entity match, fan-out
Block → stored—p95 — · p99 — · 0 blocks · 0 reorgs
How we measure
01t_block is the Polygon block timestamp of the fill. It is set by the block producer, not by us.
02t_detect is our server clock (NTP-synced) when the block’s logs were in hand on the RPC stream (newHeads, then getLogs by block hash).
03t_push is our server clock when the message was handed to your webhook or socket. Your own network hop is not included; your feed shows delivery separately.
04reorgs are counted when a block we stored is replaced. Replaced fills are re-pushed with the new transaction; the payload carries the block hash.
Ingest, this windowPolygon blocks are ~2s apart, so anything under 2s means the fill reached you before the next block was mined.
Blocks ingested0
Header seen, p50 / p95— / —
Logs in hand, p50 / p95— / —
Stored, p50 / p95 / p99— / — / —
Head—