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: 62 of 62 datasets were available from 31 selected regions x 2 endpoints.
Findings
| Endpoint | Lagging | Unique | Lowest | Arrival Tms | Arrival Region | Highest | Arrival Tms | Arrival Region |
|---|---|---|---|---|---|---|---|---|
| A. base-mainnet.Blockreq.com | 3 | 18 | 45,828,910 | 1,778,447,170,827 | Tel Aviv / AWS | 45,828,927 | 1,778,447,201,998 | Paris / AWS |
| B. base-mainnet.g.Alchemy.com | 0 | 15 | 45,828,911 | 1,778,447,169,597 | Singapore / AWS | 45,828,925 | 1,778,447,198,235 | Oregon / AWS |
We detected 3 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,778,447,187,271 in Mexico / AWS, we received number 45,828,920 from B. base-mainnet.g.Alchemy.com. Afterwards, on sendTms=1,778,447,187,370 we dispatched a request to A. base-mainnet.Blockreq.com, which returned lower number 45,828,919 at arrivalTms=1,778,447,188,755. Therefore, A. base-mainnet.Blockreq.com was lagging because it was returning lower number 45,828,919 well after B. base-mainnet.g.Alchemy.com advanced to 45,828,920.
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.