Scenario

Slot propagation and regional arrival lag.

The probe(s) subscribe with slotSubscribe and capture each slot arrival. Datasets from all regions are merged by slot number to detect the leader and followers for each slot.

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

AxB SLOT-REGION LEADERSHIP
A. mainnet.Helius-rpc.com
leading slot * region
31
behind slot * region
134
tied slot * region
7
avg lag when behind (ms)
20.1
A. COMPLETENESS
unique a.slots
87
observed in all a.probes
86
A. SLOT NUMBER GAPS
count of unique gaps
0
count of probes w gaps
0
A. RPC RESPONSES
Success
173
Fail
0
429
0
AxB SLOT-REGION LEADERSHIP
B. withered-dimensional-liquid.solana-mainnet.Quiknode.pro
leading slot * region
134
behind slot * region
31
tied slot * region
7
avg lag when behind (ms)
21.6
B. COMPLETENESS
unique b.slots
88
observed in all b.probes
85
B. SLOT NUMBER GAPS
count of unique gaps
0
count of probes w gaps
0
B. RPC RESPONSES
Success
173
Fail
0
429
0

Summary by Dataset

Summary by Slot

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

Details

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

No Errors In this Dataset