{"slug":"ws-head-latency-base","title":"Fastest Base WebSocket newHeads push, live block-push lag across RPC providers","subtitle":"Per-block WebSocket push lag in milliseconds versus the earliest provider to deliver the same Base head, measured continuously from one eu-west vantage point.","category":"RPCs","metric":"Block push lag","unit":"ms","status":"live","higherIsBetter":false,"filters":null,"value":0.428852,"leader":{"name":"PublicNode","slug":"publicnode","value":0.428852},"rankings":[{"name":"PublicNode","slug":"publicnode","ms":{"p50":0.428852,"p90":12.1982,"p99":133.69,"mean":2.17457},"successRate":100,"sampleSize":135474,"sampleHealth":19.353428571428573,"dataConfidence":"healthy"},{"name":"dRPC","slug":"drpc","ms":{"p50":23.3031,"p90":155.067,"p99":10240,"mean":62.6466},"successRate":99.9167,"sampleSize":135474,"sampleHealth":19.353428571428573,"dataConfidence":"healthy"}],"sparkline":[3.89686,3.29676,0.768123,0.492889,0.748538,1.91841,0.77002,0.475529,0.467473,0.462404,0.458845,0.453849,0.447391,0.435858,0.435964,0.440789,0.420639,0.380252,0.355561,0.345235,0.346435,0.341689,0.346816,0.355365,0.367967,0.370706,0.363632,0.356101,0.362189,0.378192,0.39465,0.429427,0.466545,0.862508,0.499512,0.497434,0.494825,0.489288,0.482052,0.470909,0.472832],"sampleSize":270948,"expectedN":7000,"dataConfidence":"healthy","asOf":"2026-07-17T04:34:54.498Z","headline":"PublicNode leads block push lag at 0.4 ms (p50, 24h) on Fastest Base WebSocket newHeads push, live block-push lag across RPC providers.","quote":"PublicNode leads block push lag at 0.4 ms (p50, 24h) on Fastest Base WebSocket newHeads push, live block-push lag across RPC providers. Source: OpenChainBench (https://openchainbench.com/benchmarks/ws-head-latency-base).","cite":{"plain":"OpenChainBench. \"Fastest Base WebSocket newHeads push, live block-push lag across RPC providers\". Retrieved 2026-07-17. https://openchainbench.com/benchmarks/ws-head-latency-base","bibtex":"@misc{ocb_ws_head_latency_base,\n  author = {OpenChainBench},\n  title  = {Fastest Base WebSocket newHeads push, live block-push lag across RPC providers},\n  year   = {2026},\n  url    = {https://openchainbench.com/benchmarks/ws-head-latency-base},\n  note   = {Retrieved 2026-07-17}\n}","apa":"OpenChainBench. (2026). Fastest Base WebSocket newHeads push, live block-push lag across RPC providers. Retrieved July 17, 2026, from https://openchainbench.com/benchmarks/ws-head-latency-base","ris":"TY  - GEN\r\nAU  - OpenChainBench\r\nTI  - Fastest Base WebSocket newHeads push, live block-push lag across RPC providers\r\nPY  - 2026\r\nUR  - https://openchainbench.com/benchmarks/ws-head-latency-base\r\nY2  - 2026-07-17\r\nER  - \r\n"},"pageUrl":"https://openchainbench.com/benchmarks/ws-head-latency-base","ogImage":"https://openchainbench.com/api/og/ws-head-latency-base","source":"https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/ws-head-latency","methodology":["Providers measured (keyless WebSocket endpoints): PublicNode (wss://base-rpc.publicnode.com), dRPC (wss://base.drpc.org). Tenderly does not expose a keyless Base WebSocket path and is scoped out until a public gateway is announced. Keyed providers (Alchemy, Infura, Chainstack, QuickNode) join the cohort when contributor keys are wired via WS_URL_<PROVIDER>_BASE env vars.","Cohort saturation: Blast, LlamaRPC, BlockPI, 1RPC, mainnet.base.org and Ankr all reject a keyless WebSocket handshake at the time of ship (verified 2026-07), which is why the keyless tier stops at two.","Chain scope: every query on this page is pinned to chain=\"base\". Base block cadence is 2 seconds, so a 24h window carries roughly 43000 samples per provider (versus ~7200 on Ethereum), well above the 7000 sample floor used by the parent bench.","Race scoring: identical to the parent [ws-head-latency](https://openchainbench.com/benchmarks/ws-head-latency-ethereum) benchmark. First provider to deliver block N sets T0. Each provider's sample for block N is arrival(N) minus T0 in milliseconds. Cohort closes 5 seconds after the first arrival; late arrivals are scored as missed blocks via ws_block_gap_total rather than as huge latency samples.","Relative, not absolute: subtraction of two arrivals over the same path removes vantage-point network latency. Consequence: the fastest provider reads near zero by construction. The honest readings are win rate, trailers' lag distribution, and gap counts.","Aggregation: per-provider lag histogram with a sub-millisecond floor (0.5 ms bucket up through 10 s tail), p50/p90/p99 via histogram_quantile over the 24h rate. Coverage score = ws_head_blocks_seen_total divided by cohort maximum, clamped to 1. A provider that pushes fast but skips blocks loses on this column, not on the latency percentiles.","Connection discipline: one persistent WebSocket per (provider, chain), client ping every 30s, read deadline 60s, 90s head watchdog forcing reconnect when a socket keeps the heartbeat alive but silently drops the subscription. Exponential backoff 2s to 60s on reconnect.","Vantage point: a single eu-west host. Multi-region deployment is a follow-up on the parent bench roadmap; the same limitation and the reasoning behind it are documented there."],"license":"CC-BY-4.0"}