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: N. California and Paris.
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. degen-mainnet.g.Alchemy.com | 0 | 3 | 26,803,441 | 1,778,850,515,104 | Paris / AWS | 26,803,443 | 1,778,850,541,536 | Paris / AWS |
| B. rpc.Degen.tips | 0 | 3 | 26,803,441 | 1,778,850,515,114 | Paris / AWS | 26,803,443 | 1,778,850,541,541 | Paris / 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.