Scenario

Block propagation and regional arrival lag.

Endpoint A subscribes with Yellowstone/Geyser Subscribe blocks over gRPC; endpoint B subscribes with Solana blockSubscribe over WebSocket. Datasets from all regions are merged by number + hash to detect the leader and followers for each block.

Of the possible 31 regions, 2 were selected for data collection: Ireland and Cape Town.

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.

AxB BLOCK-REGION LEADERSHIP
A. solana-mainnet.g.Alchemy.com
leading block * region
58
behind block * region
53
tied block * region
2
avg lag when behind (ms)
40.7
A. COMPLETENESS
unique a.blocks / hashes
87
observed in all a.probes
86
A. BLOCK NUMBER GAPS
count of unique gaps
0
count of probes w gaps
0
A. RPC RESPONSES
Success
173
Fail
0
429
0
AxB BLOCK-REGION LEADERSHIP
B. withered-dimensional-liquid.solana-mainnet.Quiknode.pro
leading block * region
53
behind block * region
58
tied block * region
2
avg lag when behind (ms)
50.9
B. COMPLETENESS
unique b.blocks / hashes
57
observed in all b.probes
56
B. BLOCK NUMBER GAPS
count of unique gaps
0
count of probes w gaps
0
B. RPC RESPONSES
Success
113
Fail
0
429
0

Summary by Dataset

Summary by Block

Includes only "complete" blocks (blocks seen by every probe). The p95 of the values in the column "p95" is: 207.1 ms.

Details

Per block, leading endpoint-region vs. every other arrival for the same block hash, incl. blocks not seen by every probe. Regional "wall clocks" are treated as globally synchronized.

No Errors In this Dataset