Scenario

Round-trip latencies for chained requests eth_getBlockByNumber(latest, false) and eth_getLogs(hash) with start-to-start throttling of (at least) 1100 ms for every request.

Also, block number 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: 60 of 62 datasets were available from 31 selected regions x 2 endpoints.

2 datasets were not available at the time of the report generation: A.aws-me-central-1, B.aws-me-central-1.

Additional info about RPC Inspector Pro technology is in the FAQ and documentation

GLOBAL LATENCY p95 ms
A. api.Uniblock.dev
eth_getBlockByNumber_latest_false
431.6
eth_getLogs_hash
645.9
Arbitrum One successes
900
A. P95 COMPARISON
winner region / method
2
worse region / method
58
additional region / method
0
A. RPC QUALITY
number consistency
100%
block availability
94.9%
A. RPC RESPONSES
Success
900
Fail
0
429
0
GLOBAL LATENCY p95 ms
B. arbitrum-mainnet.core.Chainstack.com
eth_getBlockByNumber_latest_false
194.1
eth_getLogs_hash
192.4
Arbitrum One successes
900
B. P95 COMPARISON
winner region / method
58
worse region / method
2
additional region / method
0
B. RPC QUALITY
number consistency
100%
block availability
99.3%
B. RPC RESPONSES
Success
900
Fail
0
429
0
BLOCK PROPAGATION
Endpoint Lagging Unique Lowest Arrival Tms Arrival Region Highest Arrival Tms Arrival Region
A. api.Uniblock.dev 0 46 462,883,584 1,778,797,730,869 London / AWS 462,883,702 1,778,797,760,844 Montreal / AWS
B. arbitrum-mainnet.core.Chainstack.com 0 24 462,883,584 1,778,797,730,824 Tokyo / AWS 462,883,699 1,778,797,759,531 Mexico / 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.

Errors

Info about errors incl. 429. Up to 4 retained error responses per endpoint, per region. Scenario-derived availability notes may also appear.