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. orbital-falling-gadget.ethereum-sepolia.Quiknode.pro
Ethereum Testnet Sepolia
A. P95 COMPARISON
winner region / method
2
worse region / method
2
additional region / method
0
A. RPC QUALITY
number consistency
100%
block availability
100%
A. RPC RESPONSES
Success
60
Fail
0
429
0
B. ethereum-sepolia.core.Chainstack.com
Ethereum Testnet Sepolia
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
60
Fail
0
429
0
BLOCK PROPAGATION
Endpoint Lagging Unique Lowest Arrival Tms Arrival Region Highest Arrival Tms Arrival Region
A. orbital-falling-gadget.ethereum-sepolia.Quiknode.pro 0 4 10,918,395 1,779,704,734,883 Frankfurt / AWS 10,918,398 1,779,704,763,518 Frankfurt / AWS
B. ethereum-sepolia.core.Chainstack.com 2 4 10,918,395 1,779,704,734,913 Columbus, OH / AWS 10,918,398 1,779,704,763,547 Columbus, OH / AWS

We detected 2 responses whose sendTms, arrivalTms and number were such that we can state the endpoint was lagging in the respective region.

E.g. on arrivalTms=1,779,704,737,085 in Frankfurt / AWS, we received number 10,918,396 from A. orbital-falling-gadget.ethereum-sepolia.Quiknode.pro. Afterwards, on sendTms=1,779,704,737,087 we dispatched a request to B. ethereum-sepolia.core.Chainstack.com, which returned lower number 10,918,395 at arrivalTms=1,779,704,737,118. Therefore, B. ethereum-sepolia.core.Chainstack.com was lagging because it was returning lower number 10,918,395 well after A. orbital-falling-gadget.ethereum-sepolia.Quiknode.pro advanced to 10,918,396.

Details

Latencies exclude one warmup request per endpoint in each region. Additional columns are visible when you scroll to the right.

No Errors In this Dataset