Scenario
Round-trip latencies for chained requests getblockchaininfo and getblock(bestblockhash, 1) with start-to-start throttling of (at least) 1100 ms for every request.
Also, block-height consistency with block availability and block age. The block propagation comparison is conservative and latency-agnostic.
Of the possible 31 regions, 31 were selected for data collection: Oregon, N. California, Mexico, Columbus, OH, N. Virginia, Montreal, São Paulo, Ireland, Zaragoza, London, Paris, Frankfurt, Zurich, Milan, Stockholm, Cape Town, Tel Aviv, Dubai, Mumbai, Hyderabad, Bangkok, Kuala Lumpur, Singapore, Jakarta, Hong Kong, Taipei, Seoul, Osaka, Tokyo, Melbourne, and Sydney.
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: 62 of 62 datasets were available from 31 selected regions x 2 endpoints.
Additional info about RPC Inspector Pro technology is in the FAQ and documentation
Findings
| Endpoint | Lagging | Unique | Lowest | Arrival Tms | Arrival Region | Highest | Arrival Tms | Arrival Region |
|---|---|---|---|---|---|---|---|---|
| A. bitcoin-mainnet.g.Alchemy.com | 0 | 1 | 949,636 | 1,778,925,391,741 | Montreal / AWS | 949,636 | 1,778,925,391,741 | Montreal / AWS |
| B. api.Zan.top | 0 | 1 | 949,636 | 1,778,925,391,804 | Osaka / AWS | 949,636 | 1,778,925,391,804 | Osaka / AWS |
No conclusive proof of block lag was found in this dataset / interval.
Summary
Global and continental aggregations by endpoint and method(s) depend on completeness of data in the details.
Details
Latencies exclude one warmup request per endpoint in each region. Additional columns are visible when you scroll to the right.