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, 2 were selected for data collection: Columbus, OH and Frankfurt.

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: 4 of 4 datasets were available from 2 selected regions x 2 endpoints.

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

Findings

A. rpc.Sentio.xyz
Arbitrum One
A. P95 COMPARISON
winner region / method
2
worse region / method
2
additional region / method
0
A. RPC QUALITY
number consistency
100%
block availability
93.3%
A. RPC RESPONSES
Success
60
Fail
0
429
0
B. arb-one.api.Pocket.network
Arbitrum One
B. P95 COMPARISON
winner region / method
2
worse region / method
2
additional region / method
0
B. RPC QUALITY
number consistency
100%
block availability
100%
B. RPC RESPONSES
Success
59
Fail
1
429
0
BLOCK PROPAGATION
Endpoint Lagging Unique Lowest Arrival Tms Arrival Region Highest Arrival Tms Arrival Region
A. rpc.Sentio.xyz 24 13 467,826,366 1,780,040,124,871 Columbus, OH / AWS 467,826,473 1,780,040,153,657 Columbus, OH / AWS
B. arb-one.api.Pocket.network 0 22 467,826,371 1,780,040,124,805 Frankfurt / AWS 467,826,486 1,780,040,153,504 Frankfurt / AWS

We detected 24 lagging block-number responses whose sendTms, arrivalTms and number prove the endpoint was behind in the respective region.

E.g. on arrivalTms=1,780,040,124,912 in Columbus, OH / AWS, we received number 467,826,371 from B. arb-one.api.Pocket.network. Afterwards, on sendTms=1,780,040,127,125 we dispatched a request to A. rpc.Sentio.xyz, which returned lower number 467,826,368 at arrivalTms=1,780,040,127,242. Therefore, A. rpc.Sentio.xyz was lagging because it was returning lower number 467,826,368 well after B. arb-one.api.Pocket.network advanced to 467,826,371.

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 examples per problem category, per endpoint, per region. Scenario-derived availability notes may also appear.