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, 3 were selected for data collection: N. Virginia, 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: 6 of 6 datasets were available from 3 selected regions x 2 endpoints.

AxB BLOCK-REGION LEADERSHIP
A. solana-mainnet.g.Alchemy.com
leading block * region
245
behind block * region
0
tied block * region
0
avg lag when behind (ms)
A. COMPLETENESS
unique a.blocks / hashes
83
observed in all a.probes
81
A. BLOCK NUMBER GAPS
count of unique gaps
0
count of probes w gaps
0
A. RPC RESPONSES
Success
246
Fail
0
429
0
AxB BLOCK-REGION LEADERSHIP
B. solana-mainnet.core.Chainstack.com
leading block * region
0
behind block * region
245
tied block * region
0
avg lag when behind (ms)
420.1
B. COMPLETENESS
unique b.blocks / hashes
84
observed in all b.probes
82
B. BLOCK NUMBER GAPS
count of unique gaps
0
count of probes w gaps
0
B. RPC RESPONSES
Success
249
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: 571.3 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