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.

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: 2 of 2 datasets were available from 2 selected regions x 1 endpoint.

Additional info about RPC Inspector Pro technology is in the FAQ and documentation

Findings

api.Zan.top
Solana Mainnet
RPC QUALITY
number consistency
100%
block availability
100%
RPC RESPONSES
Success
60
Fail
0
429
0

Details

Latencies exclude one warmup request per endpoint in each region. Additional columns are visible when you scroll to the right.

No Errors In this Dataset