Scenario
Block propagation and regional arrival lag.
The probe(s) subscribe with eth_subscribe(newHeads) and capture each block header arrival. Datasets from all regions are merged by number + hash to detect the leader and followers for each block.
Of the possible 31 regions, 1 were selected for data collection: N. Virginia.
Each location probe breaks its processing loop if / when the endpoint response is too-many-requests, a.k.a. HTTP code 429 etc. Also, codes 401 and 403.
At the time of the report generation: 2 of 2 datasets were available from 1 selected region x 2 endpoints.
Additional info about RPC Inspector Pro technology is in the FAQ and documentation
Launch our global propagation visualizer in your browser:
Findings
Summary by Dataset
Summary by Block
Includes only "complete" blocks (blocks seen by every probe). The p95 of the values in the column "p95" is: 189.1 ms.
Details
Per block, leading endpoint-region vs. every other arrival for the same block hash, incl. blocks not seen by every probe. Regional "wall clocks" are treated as globally synchronized.