Scenario

Block propagation and regional arrival lag.

The probe(s) subscribe with eth_subscribe(newHeads) and capture each block header arrival. Datasets from all regions are merged by number + hash to detect the leader and followers for each block.

Of the possible 31 regions, 3 were selected for data collection: Columbus, OH, Frankfurt, and Singapore.

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

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

Launch our global propagation visualizer in your browser:

Findings

eth-rpc.Polkadot.io
Polkadot
RPC RESPONSES
Success
0
Fail
3
429
0

Details

3 datasets do not have rows in this table. Review Errors below for more info.

Errors

Info about errors incl. 429. Up to 4 examples per problem category, per endpoint, per region. Scenario-derived availability notes may also appear.