Scenario
Round-trip latencies for chained requests getSlot and getBlock(slot) with start-to-start throttling of (at least) 1100 ms for every request.
Also, slot 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. lb.Drpc.live | 0 | 23 | 421,418,151 | 1,779,452,772,747 | Frankfurt / AWS | 421,418,225 | 1,779,452,801,410 | Columbus, OH / AWS |
| B. lb.Drpc.live | 2 | 24 | 421,418,152 | 1,779,452,772,749 | Frankfurt / AWS | 421,418,225 | 1,779,452,801,472 | 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,452,802,628 in Frankfurt / AWS, we received number 421,418,225 from A. lb.Drpc.live. Afterwards, on sendTms=1,779,452,802,665 we dispatched a request to B. lb.Drpc.live, which returned lower number 421,418,224 at arrivalTms=1,779,452,802,693. Therefore, B. lb.Drpc.live was lagging because it was returning lower number 421,418,224 well after A. lb.Drpc.live advanced to 421,418,225.
Details
Latencies exclude one warmup request per endpoint in each region. Additional columns are visible when you scroll to the right.