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.
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
Inconclusive data. Our processing requires at least one success for each row region / endpoint / method.
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 examples per problem category, per endpoint, per region. Scenario-derived availability notes may also appear.