Scenario
Round-trip latencies for chained requests /status and /block?height= with start-to-start throttling of (at least) 1100 ms for every request.
Also, latest block-height 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. gateway.Liquify.com | 364 | 1 | 3,371,450 | 1,779,799,143,494 | Frankfurt / AWS | 3,371,450 | 1,779,799,143,494 | Frankfurt / AWS |
| B. babylon.Nodes.guru | 0 | 4 | 3,549,096 | 1,779,799,143,641 | Frankfurt / AWS | 3,549,099 | 1,779,799,165,911 | Columbus, OH / AWS |
We detected 364 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,799,145,600 in Columbus, OH / AWS, we received number 3,549,096 from B. babylon.Nodes.guru. Afterwards, on sendTms=1,779,799,146,918 we dispatched a request to A. gateway.Liquify.com, which returned lower number 3,371,450 at arrivalTms=1,779,799,147,253. Therefore, A. gateway.Liquify.com was lagging because it was returning lower number 3,371,450 well after B. babylon.Nodes.guru advanced to 3,549,096.
Details
Latencies exclude one warmup request per endpoint in each region. Additional columns are visible when you scroll to the right.