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
| Endpoint | Lagging | Unique | Lowest | Arrival Tms | Arrival Region | Highest | Arrival Tms | Arrival Region |
|---|---|---|---|---|---|---|---|---|
| A. jsonrpc-mezo.Boar.network | 0 | 9 | 9,251,704 | 1,779,884,074,326 | Columbus, OH / AWS | 9,251,712 | 1,779,884,103,056 | Frankfurt / AWS |
| B. mainnet.mezo.public.ValidationCloud.io | 0 | 9 | 9,251,704 | 1,779,884,074,317 | Columbus, OH / AWS | 9,251,712 | 1,779,884,102,956 | Frankfurt / AWS |
No conclusive proof of block lag was found in this dataset / interval.
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.